Luma - Event Technology Platform Review

Event and community registration with free and paid plans, Stripe-linked paid events and plan-gated API access.

Luma provides event pages and registration for hosts running gatherings and communities. Its pricing page offers a free plan for events and guests and describes a platform fee on paid events, plus a paid Plus plan with a different platform-fee arrangement. Stripe's card-processing charges are separate. “Free to create an event” should not be mistaken for cost-free paid admissions: compare the host's net proceeds with the full amount a guest pays.

Paid-event workflow

The paid-event help article says hosts link a Stripe account before configuring ticket prices. It describes flexible pricing, approval before charging an applicant and waitlists for paid tickets. These options can suit a professional meetup or a small conference where registration approval is important, but test the specific capacity and approval rules with a real sample event. Check whether Stripe can onboard your legal entity in its jurisdiction and what payout currency and payment methods are available to it; an event page can exist without guaranteeing a particular merchant setup.

Luma's refund instructions explain host-initiated full and partial refunds, ticket invalidation options and guest notification. The page also says an organizer's displayed refund policy does not automatically cause Luma to issue refunds. Ask what happens to card and platform fees, which staff can refund, and how a cancelled registration appears in the calendar and finance report. Bring a partial-refund and postponed-event scenario from the refunds and chargebacks guide to a demonstration.

Data and permissions

Luma's API reference explicitly requires a Luma Plus subscription for API access; keys are scoped to a calendar. The pricing page also lists Zapier automation on the paid tier. Neither statement proves that your specific CRM fields or workflow can be synchronized without custom work. Identify the calendar owner, key rotation process, attendee consent and failure recovery using the integrations and webhooks guide. Avoid sharing a broad-access key in a spreadsheet or volunteer chat.

During evaluation, have a guest register, join a waitlist, receive approval, request a refund and check whether all changes appear in an export. Test keyboard access, checkout messages and the privacy notice with your audience; the privacy, accessibility and security checklist provides procurement questions. Published documentation establishes the described features, not service quality or accessibility outcomes for your configured event.

Key Features

Pros

Cons

Best For

Community and professional-event hosts needing registrations with optional approval and paid tickets.

Pricing

Stripe processing is separate; confirm current plan, paid-ticket economics, Stripe eligibility and refund-fee treatment.