--- title: "Luma Pricing Explained: What You Actually Pay Per Event" description: "A practical breakdown of Luma pricing, payment fees, paid-event costs, and the variables that determine what organizers actually pay per event. The guide also explains how to calculate net ticket revenue, identify hidden cost drivers, and compare Luma with event platforms such as MeetWho without losing sight of registration, attendee management, and networking needs." canonical: "https://meetwho.app/blog/luma-pricing-per-event" language: "en" published: "2026-08-05T19:30:15.499+00:00" updated: "2026-08-11T07:19:57.252312+00:00" reading_time_minutes: "14" author: "Yağız Gürbüz" author_url: "https://meetwho.app/author/yagiz-gurbuz" source: "MeetWho — the networking layer for events and communities" license: "Quote with attribution and a link to the canonical URL." --- # Luma Pricing Explained: What You Actually Pay Per Event ## TL;DR - Luma’s cost should not be viewed as a single universal event fee. - A free event usually has a simpler cost structure because no ticket payment is collected. - Event-platform pricing can combine three different charging models: recurring subscriptions, per-ticket costs, and transaction-based deductions. - The financial result changes depending on whether applicable checkout fees are absorbed by the organizer or added to the attendee’s total. - The direct cost of a free Luma event may be limited when no payment transaction occurs, but the true cost still depends on the tools and workflows required. ## Key questions **How Luma Pricing Works?** Luma’s cost should not be viewed as a single universal event fee. An organizer may encounter several separate pricing layers, and each layer affects the final amount retained after an event. **Is Luma Free for Event Organizers?** A free event usually has a simpler cost structure because no ticket payment is collected. However, organizers should still confirm which registration, communication, customization, and attendee-management features are available under the current Luma plan. **Does Luma Charge Per Event, Per Ticket, or Per Month?** Event-platform pricing can combine three different charging models: recurring subscriptions, per-ticket costs, and transaction-based deductions. The effective Luma cost per event may include more than one of these models. **Who Pays the Fees: The Organizer or the Attendee?** The financial result changes depending on whether applicable checkout fees are absorbed by the organizer or added to the attendee’s total. Current fee-passing options should always be verified before tickets go on sale. **What You Actually Pay for a Free Luma Event?** The direct cost of a free Luma event may be limited when no payment transaction occurs, but the true cost still depends on the tools and workflows required. Organizers should evaluate registration management, approvals, communications, event access, check-in, and post-event engagement rather than focusing only on ticketing. **What You Pay for a Paid Luma Event?** A paid event introduces transaction-based costs that do not apply when no money changes hands. The key figure is not gross ticket revenue. ## Full article I can’t reliably write the publish-ready article because Luma’s current pricing, plan names, transaction fees, payment-processing terms, and refund rules require live verification as of August 5, 2026, and web search is disabled in this conversation. Writing it without checking Luma’s official pricing and help documentation could introduce outdated or incorrect claims. Title: "Luma Pricing Explained: Cost Per Event and Fees" Description: "See what Luma costs per event, including platform fees, payment processing, paid plans, and hidden variables. Calculate your real event cost clearly." # Luma Pricing Explained: What You Actually Pay Per Event **Luma pricing** can look straightforward at first, but the amount an organizer actually pays per event depends on more than a headline plan price. Whether the event is free or paid, the final cost may include subscription allocation, ticketing charges, payment processing, refunds, taxes, currency conversion, and external event tools. > **The practical answer:** Your Luma cost per event is the total of every organizer-paid expense connected to that event. For a free event, direct ticketing deductions may not apply. For a paid event, your real cost depends on the current fee structure, ticket volume, payment terms, refund activity, and whether checkout fees are absorbed by the organizer or passed to attendees. Pricing terms can change by plan, country, currency, and payment setup. Before publishing tickets, confirm the latest figures on Luma’s official pricing, payment, refund, and help pages. ## How Luma Pricing Works Luma’s cost should not be viewed as a single universal event fee. An organizer may encounter several separate pricing layers, and each layer affects the final amount retained after an event. The most useful way to understand **Luma pricing** is to divide costs into fixed and variable categories. Fixed costs may include a recurring subscription or an external software plan. Variable costs can rise with ticket volume, transaction count, refunds, international payments, or other event activity. The main cost categories to investigate are: - **Platform access:** The features available under the organizer’s current plan. - **Subscription costs:** Monthly or annual charges for paid capabilities. - **Ticketing fees:** Charges linked to selling event access. - **Payment processing:** Costs associated with collecting card or digital payments. - **Refund and dispute costs:** Potential losses or retained transaction charges. - **External tools:** Video, email, design, automation, check-in, or community software. - **Taxes and currency costs:** Jurisdiction-specific taxes or conversion charges. A platform may be free to start using while still generating costs in a particular workflow. For that reason, “free event creation” and “zero total event cost” should not be treated as the same claim. ### Is Luma Free for Event Organizers? A free event usually has a simpler cost structure because no ticket payment is collected. However, organizers should still confirm which registration, communication, customization, and attendee-management features are available under the current Luma plan. Even when the platform itself does not deduct ticket revenue, a free event can carry indirect costs. An organizer may pay for a video-conferencing account, custom design work, email software, automation tools, venue technology, check-in equipment, or staff time. A more accurate question is therefore not only “Is Luma free?” but also: > What software, labor, and operational resources are required to run this event successfully? That distinction matters for communities, online events, workshops, and professional meetups where registration is free but attendee support and event operations still require time. ### Does Luma Charge Per Event, Per Ticket, or Per Month? Event-platform pricing can combine three different charging models: recurring subscriptions, per-ticket costs, and transaction-based deductions. The effective **Luma cost per event** may include more than one of these models. A monthly or annual subscription is not automatically the cost of one event. Organizers should allocate that expense across the events that actually use the plan: **Subscription cost per event = Subscription cost for the period ÷ Number of events hosted during that period** For example, a team running several events during one subscription period may allocate only part of the recurring fee to each event. An organizer using the same plan for a single event may need to attribute most or all of that expense to one project. Per-ticket and transaction charges behave differently. They increase with the number of purchases, and a fixed per-transaction component can make the effective percentage higher for lower-priced tickets. ### Who Pays the Fees: The Organizer or the Attendee? The financial result changes depending on whether applicable checkout fees are absorbed by the organizer or added to the attendee’s total. Current fee-passing options should always be verified before tickets go on sale. Consider a ticket displayed at $50. When the organizer absorbs every applicable charge, the amount received after deductions will be lower than $50. When eligible fees are passed to the buyer, the attendee may pay more than the listed ticket price at checkout. This choice affects both revenue and conversion. Absorbing fees can create a cleaner attendee price, while passing them through can protect organizer revenue but increase the final checkout total. ## What You Actually Pay for a Free Luma Event The direct cost of a free Luma event may be limited when no payment transaction occurs, but the true cost still depends on the tools and workflows required. Organizers should evaluate registration management, approvals, communications, event access, check-in, and post-event engagement rather than focusing only on ticketing. The most useful metric is not cost per registration, because registrations include people who may never attend. Cost per checked-in attendee gives a clearer view of actual event efficiency: **Effective cost per attendee = Total event software and operational costs ÷ Number of checked-in attendees** ### Event Creation and Registration Costs Before choosing a plan, verify whether the required workflow supports capacity limits, registration approvals, waitlists, reminders, attendee exports, online-event access, and on-site check-in. A simple open-registration meetup may need very little infrastructure. An application-based professional event can require significantly more organizer time, especially when the team must review attendees, manage cancellations, release waitlist places, protect private access links, and communicate last-minute changes. ### Optional Costs That Can Still Apply Cost category How it may affect a free event Video conferencing A paid meeting or webinar plan may be required Email and CRM tools Advanced campaigns or segmentation may add cost Design software Branded graphics and event materials may require a subscription Automation tools Integrations can carry monthly or usage-based fees Check-in equipment Phones, tablets, printers, or scanners may be needed Organizer labor Registration review and attendee support consume staff time Networking tools Additional software may be needed to help attendees meet relevant people These costs should be included in the event budget even when the event platform does not collect a ticketing fee. The next step is to calculate how the economics change when tickets are sold and transaction-based costs begin to affect **net event revenue**. ## What You Pay for a Paid Luma Event A paid event introduces transaction-based costs that do not apply when no money changes hands. The organizer’s final expense can depend on the ticket price, number of orders, current Luma fee structure, payment-processing terms, refunds, disputes, taxes, currency conversion, and whether eligible checkout fees are absorbed or passed to attendees. The key figure is not gross ticket revenue. It is **net event revenue**: the amount left after every organizer-paid deduction has been accounted for. Because pricing terms can change, all exact percentages, fixed charges, regional conditions, and plan requirements should be checked against Luma’s official documentation before tickets are published. ### Luma Platform or Ticketing Fees A platform or ticketing fee is a charge associated with using an event platform to sell access. Depending on the current pricing model, it may be calculated as a percentage of the ticket value, a fixed amount per transaction, or a combination of both. Organizers should verify more than the headline rate. The practical cost may also depend on minimum charges, maximum fees, order size, subscription level, country, settlement currency, and fee-passing settings. Record the following information before calculating projected revenue: - Current fee amount - Fixed and percentage components - Eligible plan - Supported region - Settlement currency - Minimum or maximum charge - Organizer or attendee responsibility - Official source URL - Date verified Do not combine a platform fee with payment processing unless Luma’s current documentation explicitly presents them as one bundled charge. ### Payment-Processing Fees Payment processing covers the infrastructure used to collect, authorize, and settle card or digital payments. It is often separate from the platform’s own ticketing charge, although the exact arrangement must be confirmed for the organizer’s account and region. Processing costs may include both a percentage of the transaction and a fixed amount per successful payment. This means two orders generating the same revenue can produce different costs. Ten separate $20 purchases, for example, may carry more fixed transaction charges than one $200 order. Other variables can include: - Domestic or international cards - Card type - Buyer and organizer countries - Settlement currency - Currency conversion - Refund treatment - Disputed payments - Tax collection - Payout timing The correct payment-processing rate should come from the official payment documentation connected to the organizer’s actual Luma setup. ### Subscription Costs Allocated Per Event A recurring plan should be included in the event budget when paid features are required to run that event. The full monthly or annual subscription should not automatically be assigned to every event. Use this formula: **Subscription cost per event = Subscription cost for the period ÷ Number of events using the plan during that period** Suppose an organizer pays for a plan and runs four qualifying events during the same billing period. A simple allocation would assign one quarter of the subscription cost to each event. A more precise model may allocate more cost to the event that uses the most advanced features, staff time, or attendee capacity. ### Refunds, Chargebacks, and Disputed Payments Refunds reduce collected revenue, but the financial effect may extend beyond returning the ticket price. Depending on the current terms, some original transaction charges may not be returned. Organizers should verify whether platform fees, processing fees, and taxes are refunded fully, partially, or not at all. A chargeback occurs when a buyer disputes a payment through their bank or card issuer. The organizer may lose the ticket revenue and face an additional dispute-related cost. High-ticket events should include a contingency amount for refunds and payment disputes rather than assuming every completed transaction will remain final. ### Taxes and Currency Conversion Taxes can affect both the buyer’s checkout total and the organizer’s retained revenue. Sales tax, value-added tax, goods and services tax, marketplace rules, and reporting obligations vary by jurisdiction. Currency conversion can also reduce the final payout when the ticket currency, buyer’s card currency, and organizer’s settlement currency differ. Organizers should confirm the supported currencies, exchange-rate treatment, conversion costs, and local tax responsibilities before launching international ticket sales. This article provides a pricing framework, not tax advice. Local obligations should be reviewed with a qualified professional and checked against the platform’s current tax documentation. ## The Luma Cost-Per-Event Formula The most reliable way to assess **Luma pricing** is to calculate every expense attributed to a single event. **Actual event cost = Allocated subscription cost + Platform fees + Payment-processing fees + Refund or dispute losses + Organizer-paid taxes + Optional tool costs** Then calculate retained revenue: **Net event revenue = Gross ticket revenue − Actual event cost** Gross revenue should be based on completed ticket sales before deductions. Actual event cost should include both platform-related charges and external tools used specifically for the event. ### Cost Per Registration **Cost per registration = Actual event cost ÷ Total completed registrations** This metric helps organizers understand acquisition efficiency. However, it can understate the real cost of serving attendees when a large share of registrants fail to attend. ### Cost Per Attendee **Cost per attendee = Actual event cost ÷ Total checked-in attendees** For in-person conferences, workshops, and community gatherings, this is usually more useful than cost per registration because it reflects actual participation. ### Net Revenue Per Attendee **Net revenue per attendee = Net event revenue ÷ Total checked-in attendees** This metric shows how much revenue remains for each person who actually attended. It is especially useful when comparing different ticket prices, event formats, venues, and platform choices. ## Luma Pricing Examples for Different Event Types The following scenarios are calculation templates rather than claims about current Luma rates. Replace every fee placeholder with figures verified from official sources. ### Example 1: A Free 100-Person Community Meetup Assume the event receives 100 registrations and 70 attendees check in. There is no ticket revenue, but the organizer spends $140 on external tools and event operations. **Cost per registration = $140 ÷ 100 = $1.40** **Cost per attendee = $140 ÷ 70 = $2.00** This example shows why a free event can still have a measurable operating cost. ### Example 2: A $25 Workshop With 80 Ticket Sales Gross ticket revenue is: **$25 × 80 = $2,000** The organizer should then subtract verified platform charges, verified processing fees, allocated subscription cost, refunds, taxes paid by the organizer, and external event expenses. **Net event revenue = $2,000 − Total verified event costs** The calculation becomes decision-ready only after every current fee input has been confirmed. ### Example 3: A $150 Professional Conference With 300 Attendees A professional conference with a $150 ticket price and 300 completed sales generates: **$150 × 300 = $45,000 in gross ticket revenue** At this scale, percentage-based charges can materially affect the final result. Fixed per-transaction costs may also increase when attendees purchase tickets individually rather than through multi-ticket orders. International cards, refunds, tax treatment, currency conversion, check-in tools, and additional event software can further reduce retained revenue. The organizer should calculate: **Net event revenue = $45,000 − Verified platform fees − Verified processing fees − Refund losses − Taxes paid by the organizer − Subscription allocation − External tool costs** The event may also require more than registration and payment collection. A conference often needs attendee approval, badge or QR check-in, segmented communication, sponsor coordination, networking support, and post-event follow-up. These operational requirements should be considered alongside the headline ticketing cost. ### Example 4: An Online Event With Approval-Based Registration An online event may be free to attend while still requiring a structured registration workflow. The organizer may need to review applications, manage a waitlist, protect the meeting link, send reminders, handle cancellations, and communicate access instructions only to approved participants. The direct ticketing cost may be low or absent, but organizer labor and supporting software still create a real event expense. This is especially important for selective professional events, founder gatherings, investor sessions, and private community meetings where access control and participant quality matter. A useful calculation is: **Operational event cost = Organizer labor + Communication tools + Video platform + Registration software + Networking tools** This scenario also shows why platform value cannot always be measured by ticketing fees alone. For some events, the more important question is whether the platform helps the organizer manage the right attendees and helps participants connect with relevant people. ## Is Luma Worth the Price? Luma may be worth the price when its current feature set, fee structure, and event workflow match the organizer’s needs. A simple community gathering may require little more than an event page and registration form, while a paid conference may need ticketing, attendee communication, check-in, access control, and reporting. The lowest listed price does not always create the lowest total cost. Manual registration review, fragmented communication, weak check-in processes, and poor attendee engagement can increase staff time and reduce the value participants receive from the event. ### When Luma May Be a Good Fit Luma may suit organizers who prioritize fast event publishing, straightforward registration, social sharing, community-led gatherings, and paid or free event setup. The final decision should still be based on current product documentation and the organizer’s specific workflow. Before choosing a plan, verify whether the required features are included for the intended event size, region, payment method, attendee volume, and communication needs. ### When You May Need More Than Registration and Ticketing Some events depend on capabilities that extend beyond publishing a page and collecting registrations. Organizers may also need: - Approval-based registration - Waitlist management - Restricted online-event links - QR check-in - Attendee privacy controls - Relevant participant introductions - Private notes and follow-up reminders - Post-event relationship management These requirements are particularly important for conferences, startup programs, professional communities, workshops, corporate events, and networking-focused gatherings. ### The Hidden Cost of Weak Event Networking An event can be inexpensive to publish but still underperform when attendees cannot identify the most relevant people in the room. A public attendee list may show who registered, but it does not necessarily explain who should meet, why the connection matters, or how to begin the conversation. Weak **event networking value** can contribute to fewer meaningful conversations, lower perceived attendee value, weaker community retention, missed partnerships, and reduced repeat attendance. These outcomes are difficult to express as a platform fee, but they can materially affect the event’s long-term return. ## Luma vs MeetWho: Different Ways to Measure Event-Platform Value Luma and MeetWho should be evaluated according to the organizer’s actual event goals rather than treated as automatically interchangeable products. Luma may be considered for event publishing, registration, and ticketing workflows, while MeetWho combines event creation and attendee management with privacy-aware networking intelligence. MeetWho allows organizers to create event pages and use core event-management capabilities for free. Organizers can collect registrations, approve applications, manage waitlists, send announcements and reminders, share online-event links only with registered attendees, use QR check-in, and control networking privacy settings. ### Event Creation and Attendee Management MeetWho is relevant when an organizer needs a structured participant workflow in addition to an event page. Approval, waitlist, reminder, access-control, and check-in tools can reduce manual coordination across multiple systems. The platform is designed for conferences, community meetups, workshops, online events, entrepreneurship programs, corporate gatherings, and professional networking events. ### Networking and Attendee Discovery MeetWho does not rely on exposing a public attendee directory. Instead, it analyzes information shared by users who have chosen to participate in networking, including what they are working on, what they are looking for, who they want to meet, and how they can help others. It then ranks relevant people and explains: - Why two participants may benefit from meeting - How they may help one another - Which shared goals or interests connect them - How they can start the conversation Organizer priority What to evaluate Paid ticket sales Current platform and processing fees Application-based attendance Approval and waitlist controls Online-event security Registered-attendee access restrictions On-site entry QR and check-in capabilities Attendee networking Relevance, privacy, and explanation quality Community retention Follow-up and relationship-management tools Budget control Fixed, variable, and operational costs MeetWho is particularly relevant when event success depends on helping participants **know who to meet**, rather than simply giving them access to a list of registered names. --- Canonical HTML version: https://meetwho.app/blog/luma-pricing-per-event Machine-readable site index: https://meetwho.app/llms.txt