Gomry gives a paid community separate products for its recurring classes and public events. Experiences manage scheduled sessions; Bundles provide prepaid credit for selected Experiences; Events sell admission to dinners, conferences and workshops. Luma centers its offer on events, calendars and community memberships. Both publish APIs, with different access and purchase workflows.
Why choose Gomry for events and repeat attendance
- Scheduled Experiences and prepaid credits. Define recurring sessions and sell Bundles across selected Experiences, giving regular customers a way to buy future visits.
- Ticketed Events alongside the timetable. Sell a conference, showcase or public workshop separately from class credit.
- Access for staff and consumer agents. Use a compatible assistant for supported organizer operations, and connect eligible event listings to applications that support discovery and commerce.
Feature comparison: from community calendar to repeat booking
A ticket to a meetup, membership of its community and credit for a future class are separate products. They can have the same customer without sharing the same entitlement.
| Workflow | Gomry | Luma | What changes for the organizer |
|---|---|---|---|
| Event registration | Events with ticket classes and attendee records | Ticket types, group purchases and coupons | Compare the information collected for each attendee, including group orders |
| Community communication | Contacts and lists alongside event and booking records | Calendar subscribers, newsletters and event reminders | Decide whether communication starts from calendar membership or the customer relationship |
| Paid community access | Subscriptions for recurring billing; Memberships in private beta | Free, one-time and recurring membership tiers | A live billing product is not a substitute for every member-access rule |
| Repeat class attendance | Scheduled Experiences and prepaid Bundles | Evaluate calendar events against the intended pass rules | Gomry lets the seller choose the Experiences a credit can book |
| Door operations | Ticket scanning and attendee lookup | Guest check-in and event management roles | Check which staff members need access before doors open |
| Developer access | REST APIs and authenticated organizer MCP (Model Context Protocol) | Plus subscription; calendar-scoped API keys and public OpenAPI | Compare the supported action, not just the presence of an API |
| Consumer-agent journey | Documented event discovery and commerce flow | OpenAPI can support custom agent integrations | Gomry provides a defined route from an event selection into ticket commerce |
A paid community that also sells classes
Consider a founder community running a monthly dinner, weekly training sessions and a public conference. Membership may grant access to the dinners, while classes are sold individually or through a prepaid pack. A conference ticket may remain a separate purchase. Combining those offers into a single generic “membership” hides the rules customers need to understand.
In Luma, the calendar and its membership tiers are central to this model. In Gomry, the dinner or conference can use Events, while the scheduled sessions use Experiences. A Bundle can cover the selected Experiences. It does not become a conference pass.
If the business primarily sells access to a private community, Luma's membership controls deserve particular weight. If customers increasingly buy individual sessions and prepaid visits, examine the Experience and Bundle flow in Gomry.
How Luma compares
Luma’s calendar memberships can use free, one-time or recurring payment tiers. Its documentation describes member-only tickets, calendar visibility and newsletters. The API supports event and guest management, and the developer getting-started guide requires a Luma Plus subscription. Its public OpenAPI specification can be used to build integrations, including integrations with AI agents.
What an external assistant changes for customers and staff
A customer asking for an event near their hotel needs a current date, venue and purchasable ticket option. Gomry's event catalog gives a connected application structured records to use in that conversation. The selected event can continue into Gomry commerce. This gives the organizer a way to support discovery inside a consumer application while keeping the purchase tied to event and order data.
Staff have a different need. An organizer may ask a compatible assistant to find an attendee, create a ticket tier or review event sales. Gomry MCP exposes supported account operations using the organizer's permissions. That allows the team to work through an assistant without treating the assistant as a separate customer database.
The purchase can use an enabled checkout integration or a link that opens Gomry checkout with the ticket type already selected. Direct checkout access is configured for the connected application.
Costs and existing community purchases
Separate the cost of accepting a paid registration from the cost of reaching the community. Count ticketing charges, payment processing, the subscription needed for integrations and any additional communication allowance. Then use the same annual sales volume for both providers. A monthly equivalent quoted with annual billing should be evaluated as an annual commitment.
Before a move, retain the current renewal dates, active membership terms, future registrations and unused credits. Reconcile those obligations separately. A guest imported into a contact list has not automatically received a paid membership or a remaining balance. Start the new booking flow with a clearly defined offer and tell customers where existing purchases will be honored.
Paid-event pricing and practical differences
Official sources checked September 18, 2026. Luma's displayed Plus price is in USD, billed annually; it is not the monthly-billing quote.
| Item | Gomry | Luma |
|---|---|---|
| Paid-event platform charge | Introductory Pro month: 2.49% + $0.79; then 3.99% + $0.79 per paid ticket | Free plan: 5%; Plus: 0% |
| Platform subscription | No monthly platform fee | Plus: $59/month billed annually |
| Processing | Processing remains additional | Stripe fee remains additional on Plus |
| Existing event operations | Events for ticketed formats; Experiences for scheduled bookings | Ticket types, group purchases, check-in and CSV import/export are listed |
See Luma pricing and Gomry pricing for current terms. Compare the total cost at your expected volume, including any paid-plan commitment.
Agent-readiness assessment
Gomry scored 100/100 on Is Agentic and 91/100 on Ora in the assessments of gomry.com recorded on September 17, 2026. Is Agentic is powered by Ora and uses a different scoring model. The assessment details explain the scores and dated platform comparison.
Choose Gomry for a community that also sells experiences
For a community adding paid classes, start with one Experience and its prepaid offer. Keep community membership benefits distinct from class credits, then connect a public Event to consumer-agent commerce if that purchase route is part of the launch.