Independent ticketing platform

Ticketing that fits the event, not the other way around.

Multi-day programmes, workshop add-ons, voucher-locked tickets, and attendees who aren't the buyer — sold through a hosted shop that charges on your own Stripe account.

No application fee, no revenue share, no per-ticket cut.

Payments

Bring your own Stripe. You keep the money, the customer relationship, and the paperwork.

Charges land on your account

Payments are created directly on your connected Stripe account and settle with you, on your payout schedule.

You are the merchant of record

Your name on the statement, your invoices, your refunds — and no application fee on anything you sell.

One account per event

Each event maps to its own connected account, so takings never mix across events.

What it does

Built for the events generic ticketing gives up on. Conferences with tracks, workshops with capacity, tickets that change hands.

Events with sub-events

Days, tracks, and workshops under one parent event — ticket types bundle whichever sub-events you choose.

Open and locked tickets

Sell to anyone, or lock a ticket type behind a voucher code — minted by hand or through the API.

Capacity that actually holds

Adding to a cart reserves capacity with a visible countdown. Abandoned carts release themselves.

Waitlists on sold-out types

Sold-out quotas take a waitlist. Release seats by hand, or automatically as cancellations free capacity.

The buyer isn't the attendee

One order, many tickets. Each holder claims theirs, fills in their own details, and picks their sessions.

Invoices and check-in

Gapless invoice numbering per event, and a QR pass per ticket with its own secret for the door.

Automation

Every surface is an interface. Run it by hand, by API, or by agent.

  • An MCP server for organizers

    An agent can create events, mint vouchers, and pull order data — no clicking through a back office.

    MCP documentation
  • A versioned REST API

    The public API ships an OpenAPI document, so you can generate a typed client in your own stack.

    API reference
  • Webhooks on the real events

    Order paid, order cancelled, ticket claimed — point them at your CRM or mailing tool.

    Webhook catalog