Event Registration & Ticketing
Luma
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Luma Labs, Inc. · luma.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Luma at a glance
- Vendor
- Luma Labs, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 29 Oct 2026
- Data hosting
- Default not stated; pages mention United States source, captured 29 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 29 Oct 2026
- Panel verdict
- The AI panel rates Luma 2.5/5, the mean of 6 judges. Luma is an event registration and ticketing platform from Luma Labs, Inc., a Delaware C corporation in San Francisco. how scores are made
- As of
- Vendor pages captured 29 Oct 2026; evaluated by the panel 30 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Luma is an event registration and ticketing platform from Luma Labs, Inc., a Delaware C corporation in San Francisco. Weighted totals span 4.2 to 5.1, strongest on payments and fees at 4 to 6 and check-in and on-site at 5 to 6: ticket money runs through the organiser's own Stripe account on a rolling payout schedule typically the next business day, and iOS, Android and web scanners cover the door. Weakest are sovereignty and shop and registration, both flat at 4 — the captured pages state that data is hosted on AWS in the United States and that data residency in other countries or regions is not offered, and we found no public information on capacity limits, waiting lists or seating. The 4-to-6 spreads in payments and fees and attendee data ownership trace to emphasis: lower payments scores weighed missing refund and transfer information, while higher ones credited the own-Stripe payout and itemised fee exports. Pricing transparency scores 4 to 5: a 5% platform fee on the free plan, 0% on the paid plan at $59 per month billed annually.
Speaks for it
- Ticket payments run through the organiser's own Stripe account, with funds typically sent on the next business day or shortly after.
- The sales history export itemises each transaction into the Luma fee, the Stripe fee and the net amount.
- iOS, Android and web scanners read a per-guest QR code, with Express Mode, lockable staff modes and hardware scanners for high-volume events.
- Guests can download receipts and invoices carrying the organiser's name, address and VAT number, numbered automatically where the Stripe country requires it.
- A data processing addendum covering GDPR, UK GDPR and CCPA, a published subprocessor list, and SOC 2 Type II and SOC 3 reports are public.
Held against it
- We found no public information on refund handling, ticket transfer, resale or chargebacks.
- Stripe's processing fee rate is not stated on the captured pages, so a paid event's full cost cannot be computed publicly.
- Tax collection and remittance stay with the organiser, with no European VAT numbers provided.
- We found no public information on capacity limits, waiting lists, seating, badge printing or box-office sales.
Best for
- You sell tickets online and want payouts landing in your own Stripe account, typically the next business day or shortly after.
- You reconcile event revenue line by line and need every fee broken out per transaction in a CSV export.
- You check guests in at a physical venue using phone scanners and restricted staff roles.
- You message attendees over email, SMS, push notification and WhatsApp from the platform itself.
Avoid if
- You need your attendee data hosted outside the United States, or data residency in your own region.
- You need per-event tax rates or law-specific DPA terms without entering an Enterprise conversation.
- You need check-in staff accounts on the free plan.
- You expect the platform to remit your taxes or supply a European VAT number.
The scores
| Criterion | Panel median |
|---|---|
| Ticket shop, checkout & registration | 2 of 5 |
| Payments, payouts, fees & refunds | 3 of 5 |
| VAT, invoices & accounting handoff | 2.5 of 5 |
| Check-in, badges & on-site sales | 2.5 of 5 |
| Attendee data & the customer relationship | 2.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2.5 of 5 |
Ticket shop, checkout & registration
Show reasoningHide reasoning
How this is scored
How a ticket or a registration is sold: ticket types and categories, member and early-bird prices, discount codes, bundles and add-ons, a shop embeddable on the organiser's own website or under its own domain, custom questions per ticket and per attendee, group and company bookings, capacity limits and waiting lists, reserved seating with a seating plan, recurring dates and course series, several languages, and an accessible mobile checkout.
0 — Not a ticketing or registration tool; tickets cannot be sold and registrations cannot be taken in the product.
3 — An event page on the platform with a few ticket types and a fixed sign-up form; embedding, custom questions, capacity rules or seating are basic or not described.
5 — Several ticket types with prices, quotas and sale periods, discount codes, custom questions per attendee, a shop embeddable on the organiser's website as a widget or link, capacity limits with a waiting list, and a checkout that works on a phone.
8 — A white-label shop under the organiser's own domain and design, reserved seating with a seating-plan editor, add-ons and bundles, group and company bookings with several attendees per order, conditional questions, member prices by code or login, recurring dates and course series, several languages, and the checkout's accessibility stated.
10 — A shop that fits any event: multi-event and season tickets, timed entry and seat holds, a checkout that the organiser can extend (API, custom fields synced to a CRM), an accessibility conformance statement (WCAG level named), and the conversion and drop-off of the checkout reported to the organiser.
The Conference Organiser
Ticket types, coupons and group purchasing are documented, guests' answers to registration questions are captured and visible to check-in staff, and approval or token gating handles selective admission; a custom URL for event pages comes with the paid plan. For my congress the open questions are the ones no page answers: we found no public information on capacity limits with waiting lists for twenty-seat workshops, member versus non-member pricing, reserved seating, or running the shop under our own domain and design. We also found no public information on the checkout's accessibility. 3 6
The Venue Promoter
The pricing page shows ticket types, group purchasing and coupons, registration can require approval or token gating, and the check-in help confirms guests answer registration questions — enough structure to sell a night of tiered tickets. We found no public information on quotas or sale windows, waiting lists, a seating plan, or a shop under the club's own domain beyond a 'Custom URL for event pages' on the paid plan; a help page about embedding Luma on a website was captured but adds no detail we could confirm. Fine for standing room, unproven for anything reserved. 6 3
The Course Provider
Ticket types, group purchasing and coupons are on the public pricing page, registration questions are confirmed indirectly through check-in staff being able to see guests' answers to them, and a help article covers embedding Luma on a website. What my eight-week courses need beyond that — capacity limits with a waiting list that refills a cancelled seat, quotas, sale periods, seating or several languages — has no public information I could find. For a school selling recurring course dates, that silence decides the level. 2 3 6
The Revenue Accountant
The captured pages describe ticket types with prices, coupons and group purchasing, registration questions whose answers travel all the way to the door, and a custom event-page URL on the paid plan, with events living on Luma-hosted pages. We found no public information on sale quotas and periods, capacity limits or waiting lists, reserved seating, or a shop embeddable on my own website, so this reads as a platform page with a standard form rather than my box office. 1 3 6
The Data Protection Officer
Ticket types, group purchasing, coupons and approval or token gating are documented, registration questions are evidenced by the answers check-in staff can see, and a help article on embedding events on an organiser's website exists alongside custom URLs for event pages. We found no public information on capacity limits, waiting lists, seating plans, per-ticket quotas, or checkout languages and accessibility. 6 3 2
The Skeptic
Ticket types, group purchasing, coupons and approval or token gating are documented, registration questions exist because check-in staff can see guests' answers to them, and a custom URL for event pages comes with the paid plan. We found no public information on capacity limits and waiting lists, sale periods, seating, shop languages or the checkout's accessibility, and the captured facts do not describe how embedding works. The shop's centre of gravity is Luma's own calendar and community pages, so the event lives on the platform first. 1 6 3 10
Payments, payouts, fees & refunds
Show reasoningHide reasoning
How this is scored
How the money moves: payment methods offered to buyers (cards, PayPal, SEPA direct debit, invoice, local methods), whether the organiser connects its own payment account or the platform collects as merchant of record, when the revenue is paid out (continuously, before the event, or after it), the per-ticket and payment fees and whether they can be passed on to the buyer, refunds of single tickets and of a cancelled event, ticket transfer and resale, and chargebacks.
0 — No payment of any kind; the product only collects free registrations.
3 — Online card payment through the platform; payout timing, fee model, refunds or buyer-paid fees are basic or not described.
5 — Several payment methods including cards and PayPal or SEPA, the fee per ticket stated with the option to pass it to the buyer, the payout schedule stated, and refunds of single orders and of a cancelled event issued from the product.
8 — A choice between the organiser's own payment account (Stripe, PayPal, Mollie or similar) and platform collection, payouts before the event stated with their conditions, invoice and bank transfer for business buyers, partial refunds and refund policies set per event, ticket transfer or resale by buyers, and chargeback handling explained.
10 — Full control of the money: the merchant of record named for each set-up, payout timing and any reserve held published, every fee itemised per order, refunds, transfers and resale with the organiser's rules enforced, and the cancellation process for an event documented end to end.
The Conference Organiser
The money moves through the organiser's own Stripe account with rolling payouts typically on the next business day, and Luma's platform fee plus Stripe's processing fee are deducted from each transaction; cards, Apple Pay, Google Pay and regional methods such as iDEAL are accepted. The platform fee is public — 5% on the free tier, 0% on the paid plan — and the price I set is exactly what guests see, so the fees sit with the organiser. We found no public information on invoice or bank-transfer payment for business buyers, partial refunds and per-event refund policies, ticket transfer or resale, or chargeback handling. 4 5 6
The Venue Promoter
The money side reads well for a club that pays guarantees before doors: cards, Apple Pay and Google Pay plus regional methods like iDEAL, a '5% platform fee' on the free plan or '0%' on the paid one, fees 'automatically deducted from each transaction as it occurs', and a rolling payout schedule 'typically sent on the next business day or shortly after' that is 'managed in Stripe, not Luma' — cash arriving around the show, not three weeks after. But the captured pages state 'the price you set is exactly what guests see and pay', so the fee stays on my side of a twelve-euro ticket and no buyer-pays option is described. We found no public information on refunding single orders or a cancelled night, ticket transfer, resale or chargebacks. 5 6 4
The Course Provider
The money model is readable: cards, Apple Pay, Google Pay and regional methods such as iDEAL; a 5% platform fee for paid events on the free plan or a 0% platform fee on the paid plan, with Stripe's processing fee, both deducted per transaction, and payouts through the organiser's own Stripe account on a rolling schedule typically the next business day. The price I set is exactly what guests see and pay, so fees stay with me rather than the buyer. We found no public information on refunds of single orders or a cancelled event, ticket transfer, resale or chargebacks, which my cancellation terms would have to point to. 4 5 6
The Revenue Accountant
Money lands in my own Stripe account, payouts run on a rolling schedule typically the next business day and are managed in Stripe, and buyers pay by card, Apple Pay, Google Pay or regional methods such as iDEAL. The platform fee and Stripe's processing fee are deducted per transaction and the sales history itemises each order into the Luma fee, the Stripe fee and the net amount — exactly what I need for reconciliation. We found no public information on issuing refunds or cancelling a whole event's sales in the product, on buyer transfers or resale, on chargebacks, or on passing fees to the buyer. 4 5 6
The Data Protection Officer
Cards, Apple Pay, Google Pay and regional methods such as iDEAL are offered, Luma's platform fee and Stripe's processing fee are deducted from each transaction and itemised per transaction in the sales export, and the organiser's own Stripe account manages a rolling payout schedule typically on the next business day. We found no public information on refunds being issued from the product beyond refunded amounts in exports, ticket transfer or resale, chargebacks, or invoice and bank transfer for business buyers. 5 6 4
The Skeptic
Cards, Apple Pay, Google Pay and regional methods such as iDEAL, Konbini and PayNow are offered, and the money runs through the organiser's own Stripe account — the payout schedule is managed in Stripe, rolling by default with funds typically sent the next business day, which answers my two oldest fears about held payouts and surprise buyer-facing fees. The platform fee — 5% platform fee for paid events on the free plan, 0% on the paid plan — plus Stripe's processing fee is deducted from each transaction, and every transaction is itemised down to each fee in the sales export. We found no public information on refund handling, chargebacks, or passing fees to the buyer; the stated model is that the price you set is exactly what guests see and pay. 5 6 4
VAT, invoices & accounting handoff
Show reasoningHide reasoning
How this is scored
How ticket revenue reaches the books correctly: the VAT rate set per ticket or product (reduced rates for concerts and culture, exemptions for education and seminars), gross and net prices shown, invoices to buyers in the organiser's name with consecutive numbers, business buyers with company name and VAT ID, reverse charge for cross-border events, cancellation invoices and credit notes, the platform's own fee invoice, e-invoicing, and exports to DATEV or named accounting systems.
0 — No receipts or invoices; the organiser has to produce every invoice outside the product.
3 — An order confirmation or simple receipt per booking; VAT rates, invoices in the organiser's name, business buyers or accounting exports are basic or not described.
5 — VAT rate configurable per ticket, invoices generated in the organiser's name with its tax details and consecutive numbers, company name and address captured for business buyers, cancellation invoices on refund, and a sales export as CSV or to at least one named accounting system.
8 — Several VAT rates in one order, net prices for business buyers, VAT IDs validated and reverse charge applied, e-invoices (XRechnung or ZUGFeRD) for public and business buyers, a DATEV export with booking data, the platform's fee invoice separated from ticket revenue, and whether the platform sells as agent or in its own name stated.
10 — Tax handled per country: VAT rules for events in several EU countries documented with the place of supply, invoices and credit notes stated as compliant with national invoice law, a reconciliation of payouts, fees and ticket revenue per event, and a GoBD-compliant archive or audit export.
The Conference Organiser
Tax configuration comes with the paid plan and per-event rates with Enterprise, tax is shown inside the ticket price, and guests can download a receipt or invoice carrying our name, address and VAT number, with automatic sequential numbering where the Stripe country requires it; Luma also issues a monthly fee invoice and the sales CSVs carry tax name, rate and amount. We found no public information on reverse charge and VAT-ID validation, net prices for business buyers, credit notes after cancellation, or an export to a named accounting system such as DATEV. 4 5
The Venue Promoter
Guests can download a receipt or invoice carrying my business name, address and VAT number, numbered automatically from an unbroken series where the Stripe country requires it, and I can generate a monthly invoice for platform fees 'for example, for bookkeeping or VAT purposes', alongside CSV exports that itemise tax per transaction. Tax configuration sits on the paid plan and a different rate per event sits behind Luma Enterprise, the pages put tax collection and payment on the host, and they state plainly 'We do not provide European VAT numbers'. We found no public information on reverse charge, e-invoicing, or an export to a named accounting system such as DATEV. 4 5 6
The Course Provider
Guests can download a receipt or invoice carrying my business details including a VAT number, invoices are numbered automatically from an unbroken series where the Stripe country requires it, tax configuration comes with the paid plan with the tax shown included in the guest's price, and Luma states it does not remit tax, so I settle with the tax office myself; a monthly platform-fee invoice can be generated and sales exports carry tax columns. Running exempt teaching and taxable workshops in one shop, though, would push me to per-event tax rates that sit behind an Enterprise contact email. We found no public information on capturing employer company details and VAT IDs, reverse charge, credit notes on cancellation, e-invoicing or an export to a named accounting system beyond CSV. 4 5
The Revenue Accountant
Tax configuration comes with the paid plan, tax is included in the displayed price (a $10 ticket with 20% tax shows guests $12), guests download receipts or invoices bearing my name, address and VAT number with automatic sequential numbering where the Stripe country requires it, and Luma issues a separate monthly fee invoice — the one thing I insist on. We found no public information on credit notes for refunds, reverse charge, e-invoices, or an export to DATEV or any other named accounting system — the sales export is CSV. 4 5 6
The Data Protection Officer
Tax collection requires the paid tier and per-event tax rates the Enterprise tier, guests can download receipts and invoices carrying the organiser's name, address and VAT number with automatic sequential numbering where the Stripe country requires it, and Luma issues monthly invoices for platform fees for bookkeeping or VAT purposes. The tax is included in the displayed price and the organiser remains responsible for remitting it, and we found no public information on credit notes, reverse charge, e-invoices, reduced rates, or exports to named accounting systems. 4 5 6
The Skeptic
Tax collection comes with the paid plan, per-event tax rates with the enterprise plan, and the tax is included in the price guests see; guests can download a receipt or invoice carrying the organiser's name, address and VAT number, with automatic sequential numbering where the Stripe country requires it. We found no public information on reverse charge, VAT ID validation, e-invoices or exports to a named accounting system. 4 5
Check-in, badges & on-site sales
Show reasoningHide reasoning
How this is scored
What happens at the door: a check-in app that scans tickets on phones or scanners, offline scanning and several devices at once, entrances and time slots, check-in lists by name, badge printing with attendee data and QR code, box office and on-site sales with card terminals, walk-in registration, session and room check-in at conferences, attendance certificates, and live attendance figures.
0 — No check-in; tickets cannot be validated at the event.
3 — Tickets with a QR code and a guest list to tick off by hand or in a simple app; offline use, several devices, badges or on-site sales are basic or not described.
5 — A free check-in app for iOS and Android that scans tickets on several devices at once, works offline and syncs, a searchable guest list, and live check-in numbers in the dashboard.
8 — Badge printing with attendee data and QR codes, access rules per entrance, session or day, box office sales on site with a named card terminal, walk-in registration, dedicated scanner hardware supported or rented, and attendance certificates for courses.
10 — On-site operations at scale: self-service kiosks or turnstile integration, session check-in feeding continuing-education credits, cashless or on-site payments reconciled with online sales, and the hardware, offline limits and failover documented.
The Conference Organiser
iOS and Android apps plus a web scanner read per-guest QR codes in express or standard mode, staff can be restricted to specific ticket types, hardware scanners are supported for high-volume events, and third-party check-in systems can build on the same QR codes; guest tickets also work offline in Apple and Google Wallet. For the door itself we found no public information on badge printing, box-office sales with a card terminal, walk-in registration, session-level check-in feeding continuing-education points, or attendance certificates — and check-in staff requires the paid plan. 3 6
The Venue Promoter
This is the page I care about most and it mostly holds up: check-in apps on iOS and Android, Express Mode that checks a guest in the instant their QR code scans, a searchable guest list for manual check-ins, 'Not Valid' feedback with multi-ticket selection, hardware scanners for high-volume events, and a limited check-in staff role I could hand my two door volunteers that shows name, ticket type, amount paid and question answers without event-management powers — though that role 'requires Luma Plus'. The offline claim covers the guest's wallet pass, not the scanner; we found no public information on the scanning app itself running without signal in a basement and syncing later. Badges, a box office with a card terminal and walk-up registration go unmentioned in everything we captured. 3
The Course Provider
Every guest gets a QR code, scanner apps exist for iOS, Android and the web with express and standard modes, invalid-ticket feedback, manual check-in by searching the guest list, and hardware scanners are supported for high-volume events; check-in staff work as a limited role, restricted to chosen ticket types and unable to touch the guest list or messaging, which suits a colleague at the seminar door. For my courses the gaps matter: we found no public information on badge printing, walk-in registration, box-office sales with a card terminal, attendance certificates, or whether scanning works offline. 3
The Revenue Accountant
iOS and Android apps plus a web scanner read QR codes delivered by email, in the app or as Apple/Google Wallet passes, with express and standard scan modes, a lockable mode, invalid-ticket feedback, a searchable guest list, a checked-in count, restricted check-in staff roles and hardware scanners for high-volume events. We found no public information on badge printing, box-office or walk-up sales, or entrance and session access rules, and the multi-staff check-in role requires the paid plan. 3
The Data Protection Officer
Every guest receives a QR code with Apple Wallet and Google Wallet passes that work without an app or internet, scanning runs on iOS, Android and the web with express and standard modes, mode locking, invalid-ticket feedback and multi-ticket selection, and there is name search, a checked-in count, a restricted check-in staff role (requiring the paid tier), hardware scanner support for high-volume events and integration for external check-in systems. We found no public information on badge printing, box office or on-site sales, walk-in registration, session-level check-in or attendance certificates. 3 6
The Skeptic
iOS, Android and web scanners read a QR code that lives in the confirmation email, the Luma app and Apple or Google Wallet passes, with an Express mode that checks guests in on scan, a mode lock for staff, search-based manual check-in and clear invalid-ticket feedback. Check-in staff are a limited role that can be restricted by ticket type, though that role requires the paid plan, and hardware scanners and external check-in systems are supported. We found no public information on offline scanning limits, live attendance figures, badge printing, box office or on-site sales. 3 6
Attendee data & the customer relationship
Show reasoningHide reasoning
How this is scored
Who the ticket buyer belongs to: whether the organiser is the controller of attendee data and the platform its processor, or the platform a controller in its own right; whether buyers must create an account on the platform; whether the platform markets other events to the organiser's buyers or lists the event on its own marketplace; consent for the organiser's newsletter collected in the checkout; messages to attendees; attendee data exportable at any time; and deletion and anonymisation after the event.
0 — The organiser receives no attendee data at all; the platform keeps the buyer relationship entirely.
3 — A guest list visible to the organiser; who is controller, the platform's own marketing to buyers, export or deletion are basic or not described.
5 — Attendee data exportable by the organiser at any time, the organiser named as controller with a data processing agreement offered, buyers able to book without a platform account, newsletter consent for the organiser collectable in the checkout, and messages to attendees from the product.
8 — A white-label set-up in which buyers see only the organiser, the platform stated not to market other events to the organiser's buyers (or the opt-out explained), the platform's marketplace listing optional, deletion and anonymisation of attendee data after the event configurable, and attendee data synced to a named CRM or via API and webhooks.
10 — The organiser owns the relationship and can prove it: the controller and processor roles documented for every data flow, no platform account or platform marketing by default, retention set per event and enforced, and a complete export of orders, attendees and answers that a successor tool can import.
The Conference Organiser
Attendee data exports to CSV, deletion is self-serve, blasts and reminders run through email, SMS, push and WhatsApp, and Zapier automation plus a GDPR-scoped data processing addendum are available. However, guests see their ticket on the event page only when signed in, and the platform itself runs discovery features — public calendars with followers and event submission — while we found no public information on whether the platform markets other events to my buyers, whether guests can book without a Luma account, or the controller and processor roles for each data flow. 3 6 7 8 10
The Venue Promoter
The privacy policy says attendee data is shared with the event host, export and deletion are self-serve on standard plans, CSV export is a listed feature, and I can blast and remind guests by email, SMS, push notification and WhatsApp — so last month's buyer list is mine to mail. But Luma is also built as a social site where visitors follow calendars and submit events, and we found no public information on who is named controller, whether a buyer can book without a Luma account, newsletter consent at checkout, or whether the platform markets other events to my crowd. A GDPR data processing addendum is published, which is a real start. 7 8 6 10
The Course Provider
Guests' personal data is shared with me as the host, I can export and delete it myself through self-serve tools and CSV, a data processing addendum is published, and blasts and automated reminders go to attendees through the product itself. The open questions for a school like mine are who is formally named as controller, whether buyers can register without a Luma account, and whether I can collect my own newsletter consent in the checkout — we found no public information on any of these. 6 7 8
The Revenue Accountant
Attendee details are shared with me as host, I can export and delete them self-serve, a GDPR data processing addendum is published, and I can message guests over email, SMS, push and WhatsApp. We found no public information on whether buyers can book without a Luma account, on collecting my own newsletter consent at checkout, or on the platform refraining from marketing other events to my buyers — the follow, event-submission and community pages show the platform keeps its own audience alongside mine. 3 6 7 8
The Data Protection Officer
Attendee data is exportable and deletable by the organiser on standard plans, CSV export and detailed per-transaction sales lists are available, a data processing addendum covering GDPR and UK GDPR is published, and messages go out to attendees via email, SMS, push and WhatsApp. The captured pages state that a registrant's personal data is shared with the event host, but we found no public information naming the organiser as controller, booking without a platform account, checkout newsletter consent, retention set per event, or a named CRM sync — and Luma itself runs discovery features such as following calendars and community pages. 8 7 6 5
The Skeptic
Guest lists and sales export as CSV, self-serve data export and deletion exist without an enterprise plan, a GDPR-scoped data processing addendum is published, and blasts and reminders go to attendees via email, SMS, push and WhatsApp. But the captured pages do not say who is controller and who is processor, guests sign in and carry profile photos on Luma, and we found no public information on collecting newsletter consent in the checkout or on the platform not marketing other events to your buyers — Luma's own calendars, follows and event submission form the discovery layer your audience sits in. 7 8 3 6 10
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where attendee, order and payment data are hosted, and who the subprocessors are (hosting, payment providers, email delivery, analytics, support). Independently sourced by the sovereignty pipeline; attendee lists show who goes where and when, and a conference list holds names, employers and dietary or accessibility answers, so the whole chain counts, not only the database.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (payments, email, analytics, support) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, a self-hosted or on-premises option or data export and deletion documented, and certifications published with their scope rather than implied.
The Conference Organiser
The contracting entity is Luma Labs, Inc., a Delaware C corporation in San Francisco, and all data is hosted on AWS in the United States with no data residency in other regions, accessed primarily from the US; Stripe and Google services appear in the chain. A subprocessor list is published, the data processing addendum covers GDPR and UK GDPR, and SOC 2 Type II and SOC 3 reports are available. We found no public information on an EU entity, EU hosting or an EU representative anywhere in the chain. 4 7 8
The Venue Promoter
To its credit, a subprocessor list, a GDPR-scoped data processing addendum and SOC 2 Type II and SOC 3 reports are published, with Stripe and Google services named in the chain. Even so, my door list — who came to my club on which night — has no European home on these pages, and no EU entity or representative appears in anything we captured. 8 4 7
The Course Provider
The vendor is transparent but firmly American: Luma Labs, Inc., a Delaware corporation in San Francisco, hosts everything on AWS in the United States and states it offers no data residency in other countries or regions, with a published subprocessor list, a data processing addendum and SOC 2 Type II and SOC 3 reports. For my attendee lists that means the whole chain — payments through Stripe, visit analytics through Google — runs to the United States, with no European entity or hosting anywhere in the captured pages. 4 7 8
The Revenue Accountant
The contracting entity is Luma Labs, Inc., a Delaware C corporation, everything sits on AWS in the United States with no data residency in other regions offered, and team members plus subprocessors access the data primarily from the US. A subprocessor list, a GDPR data processing addendum and SOC 2 Type II and SOC 3 reports are published, which is more transparency than I usually get. We found no public information on a European entity, EU hosting or an EU representative, so my attendee lists and dietary answers would live outside the EU. 4 7 8
The Data Protection Officer
The contracting entity is Luma Labs, Inc., a Delaware C corporation in San Francisco, all data is hosted on AWS in the United States with no data residency offered elsewhere, and team members and subprocessor providers access account, event and attendee data primarily from the United States. A data processing addendum, a published subprocessor list (Stripe for payments, Google Analytics for visit analytics, Google and YouTube APIs are named) and SOC 2 Type II and SOC 3 reports exist, but country-specific transfer clauses and law-specific terms are reserved for the Enterprise plan and no European VAT number is provided — a material consideration when attendee lists carry dietary and accessibility answers. 8 7 4
The Skeptic
The contracting entity is Luma Labs, Inc., a Delaware C corporation in San Francisco, attendee and order data is hosted on AWS in the United States with no data residency offered in other countries or regions, and team members and subprocessors access that data from outside your country, primarily from the United States. A subprocessor list is published, a data processing addendum covering GDPR is offered, and SOC 2 Type II and SOC 3 reports are listed — but we found no public information on any EU entity, EU hosting option or EU safeguard for the payments, email or analytics chain. For a European organiser, the whole attendee trail sits under US jurisdiction. 7 8 4
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether an organiser can compute the real cost of an event from public pages alone: the fee per ticket or per registration (fixed, percentage or both), payment processing fees, whether fees are charged to the organiser or added to the buyer's price, free events, subscriptions or credit packs, payout and refund fees, add-ons (seating, white label, badges, box office), hardware rental, minimums and term, and VAT on the fees.
0 — No public prices at all; every organiser is a sales call.
3 — A starting price or "free for free events" exists, but the fee for paid tickets, payment fees or who pays them is unclear.
5 — The fee per ticket and the payment processing fees are public with the main inclusions, but at least one commonly needed piece (refund fees, white label, seating, box office, hardware) is unpriced or "on request".
8 — Every fee published with its rule (per ticket, percentage, cap), the share paid by buyer and organiser stated, add-ons and hardware priced, payout and refund fees listed, and VAT treatment of the fees stated.
10 — Complete price computability: the cost of an event derivable for a given ticket price, ticket count and payment mix, with every add-on, hardware, support and payout fee and the cancellation and data-return terms published.
The Conference Organiser
The public pages give the fee rule: a 5% platform fee on the free tier, or the paid plan at $59 per month billed annually with "Save 14%" stated and 0% platform fee, plus stated admin and invite limits; fees are deducted per transaction and the price set is what guests see. The Stripe processing fee is named but never quantified, and we found no public information on refund and payout fees, hardware rental, or the VAT treatment of the fees. Per-event tax rates, law-specific DPA terms and security questionnaires sit behind a contact-sales Enterprise offering. 4 5 6
The Venue Promoter
I can budget a season from public pages alone: free with 'unlimited events and guests' but a '5% platform fee for paid events', or '$59' per month billed annually with '0%' platform fee, admin seats and weekly invite limits stated per plan, and fees deducted per transaction. The tax page pins 'the price you set is exactly what guests see and pay', so the fee stays on my side and no buyer surcharge is described, while the Stripe processing rate, refund or payout fees, and per-event tax rates (Enterprise, by email) go unstated or behind a contact address. Enough to plan from, not enough to price a night to the cent. 6 5 4
The Course Provider
I can read the costs off the public pages: free use with unlimited events and guests carrying a 5% platform fee for paid events, or the paid plan at $59 per month billed annually saving 14% with a 0% platform fee, admin seats and weekly invite limits stated, and the price I set being exactly what guests see and pay, so fees sit with me. The gaps: Stripe's processing fee figure is not stated on these pages, and we found no public information on refund fees, cancellation terms, hardware rental pricing or the cost of the Enterprise tier. 4 5 6
The Revenue Accountant
Public pages state the free tier with unlimited events and guests, a 5% platform fee for paid events (0% on the paid plan at $59 per month, billed annually), and that the price I set is exactly what guests see and pay. We found no public information on the Stripe processing fee rate, refund or payout fees, hardware pricing, or the Enterprise plan's price, so I can state my platform fee but cannot compute a ticket's full cost from public pages alone. 4 5 6
The Data Protection Officer
The free tier with a 5% platform fee for paid events (unlimited events and guests, up to 500 invites per week, up to 3 admins) and Luma Plus at $59 per month billed annually with a 0% platform fee are published, fees are deducted per transaction and itemised in the sales export, and the price the organiser sets is exactly what guests see and pay. We found no public information on the Stripe processing fee figure, Enterprise pricing, refund or payout fees, hardware rental, or the VAT treatment of the fees beyond monthly fee invoices generated for bookkeeping. 6 5 4
The Skeptic
The free plan is documented in full — unlimited events and guests, up to 3 admins, 500 invites or newsletters per week and a 5% platform fee for paid events — and the paid plan is $59 per month, billed annualy with 14% savings, carrying a 0% platform fee, 5 admin seats and 5,000 invites per week, with who pays made clear: fees are deducted per transaction and the price you set is what guests pay. But we found no public information on the Stripe processing fee rate, refund or payout fees, hardware scanner pricing, or enterprise pricing beyond a contact address, so the real cost of a paid event is not computable from the public pages alone. 6 5 3 8
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Luma
Is Luma European?
No. whats-best.ai classifies Luma as Rest of world.
Where does Luma store data?
The default storage location for customer data is not stated on the vendor’s pages as of 29 Oct 2026. The vendor’s pages mention United States as hosting location, per the vendor’s page captured 29 Oct 2026.
Does Luma have a free plan?
Not stated on the vendor’s pages as of 29 Oct 2026.
What are the best alternatives to Luma?
As of 3 Nov 2026, the panel rates pretix (3/5), Converia (3/5) and doo (3/5) highest among the other 13 Event Registration & Ticketing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is pretix (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Luma alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Hosting location. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 10 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage luma.com Checked 29 Oct 2026 Details →
- 2 Help article (embedding) help.luma.com Checked 29 Oct 2026 Details →
- 3 Help article (check-in) help.luma.com Checked 29 Oct 2026 Details →
- 4 Help article (taxes and VAT) help.luma.com Checked 29 Oct 2026 Details →
- 5 Help article (payouts) help.luma.com Checked 29 Oct 2026 Details →
- 6 Pricing page luma.com Checked 29 Oct 2026 Details →
- 7 Privacy policy luma.com Checked 29 Oct 2026 Details →
- 8 Data protection / gdpr page help.luma.com Checked 29 Oct 2026 Details →
- 9 Ticket shop, checkout & registration — found from sitemap luma.com Checked 29 Oct 2026 Details →
- 10 Ticket shop, checkout & registration — found from sitemap luma.com Checked 29 Oct 2026 Details →
- 11 Attendee data & the customer relationship — found from sitemap luma.com Checked 29 Oct 2026 Details →
- 12 Attendee data & the customer relationship — found from sitemap luma.com Checked 29 Oct 2026 Details →