Event Booking

5.0 out of 59 sold

Events with sessions and real capacity, sold from your own app. A ticketing platform charges per ticket on an audience you already had.

From$749

Open the preview Request a quote

Function: 23
User types: 2
Platform: iOS & Android

React Native
TypeScript
PostgreSQL
Expo

Inside the app

What it does out of the box

23 connected functions on one schema across 2 user types. Everything below is in the template before a line of customisation.

Events
Dates, remaining capacity and the tier currently on sale. No countdown theatre, just what is actually left.
Sessions
Capacity per session rather than per event, with clashes prevented at selection. The room holding 40 does not care that the event sold 300.
Requirements
Dietary and access needs taken at booking and carried through to the day, rather than collected in a separate form nobody reconciles.
Tiers
Early bird, standard, concession, with windows that close on their own. A tier still selling after it should have closed is money left behind.
Waitlist
When a session fills, with automatic promotion. A full session with no waitlist is a refund you did not have to give.
Sales pace
Against target, so a slow week is a problem you can still fix rather than one you read about afterwards.

User types

Two apps, one event.

The attendee is choosing how to spend a day and the organiser is selling a finite number of seats. Session-level capacity is where most simple ticketing tools give up.

User
3 of 5 screens
The attendee
Finds the event, picks sessions, books and holds it on their phone. Availability is accurate at the moment of purchase rather than a minute afterwards.
Preview as the user
- Availability accurate at purchase
- Pick sessions, not just a day
- Dietary and access needs at booking
- Change or cancel inside your rules
- Everything held on the phone
Event owner
2 of 5 screens
The organiser
Sets up events, sessions and capacity, watches the book fill, and knows on Monday whether Friday needs work.
Preview as the event owner
- Events with sessions and capacity
- Pricing tiers and early bird windows
- Sales pace against target
- Waitlist when a session fills
- Every attendee record stays yours

The limits

What this is not.

The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.

It carries no audience
A ticketing platform’s fee partly buys discovery. This sells to people you can already reach.
We do not process payments
Ticket money runs through your own payment provider account, which is what removes the per-ticket cut.
It is not a venue or AV system
Room layouts, streaming and production are separate concerns. We integrate where it matters rather than pretending to replace them.
Refund policy is yours
The app enforces the rule you set and shows it before purchase. What the rule should be, and what consumer law requires, is yours.

Questions

Questions, answered plainly.

If yours is not here, ask it on the call rather than guessing from a pricing page.

Not covered here?

Ask a consultant directly. No form to fill in first, and no follow-up sequence.

Book a consultant All questions

Can it handle sessions with separate capacity?

Yes, and it is the main reason to choose this over a simple ticket link. Session capacity is where most tools fall over, because the workshop room holds 40 regardless of what the event sold.

Can we run free and paid events together?

Yes. Free registration, paid tiers, early bird and comps are the same object with different rules.

What happens when a session sells out?

A waitlist opens and promotes automatically when somebody drops. Doing this by hand is where organisers lose evenings.

How does this relate to Ticketing?

Event Booking sells the place; Ticketing issues, transfers and refunds the ticket itself. Small events need only this one; anything with resale or transfer wants both.

Do I get the source code?

Yes. Both apps, API, schema, migrations and deployment configuration transfer on delivery.