Platform

Every event type, one way to run it.

Concerts, matches, classes, and sailings are configuration, not new schemas. Create events with their sessions, move from draft to published with a guided checklist, and reuse everything.

Explore highlights

Sound familiar?

Event setup lives in spreadsheets

Dates in one file, prices in another, the truth in someone's head. Events, sessions, venues, and pricing belong in one model with one lifecycle.

Every event type needs its own system

Ticketing for shows, booking for classes, something else for cruises. A generic event model runs them all. Types are data, not code.

Launch-day unknowns

Did anyone set the timezone? The hold timer? Publishing with a preview and a checklist turns go-live from a leap into a step.

The event operations spine

01A real lifecycleDraft, published, archived, with publish and unpublish previews that show exactly what buyers will see before anyone does.
02Sessions built inAn event's instances, performances, sailings, time slots, carry their own schedule, chart pin, pricing, and overrides.
03Event types as dataA DB-backed registry defines each type's session labels, cardinality, and schedule modes. Workspaces enable only what they run.
04Hot-event modeOne toggle routes a high-demand event's hold traffic to dedicated capacity, per session, inheriting or overriding.
05Sensible defaults, per eventVenue, geo, timezone, seat map theme, and hold settings default per event and override per session.
06Everything linksOrders, pricing, seat map, studio, and previews hang off the event, no hunting across modules.

From idea to on-sale

  1. 01Create from a typePick the event type; its session labels and schedule modes come with it.
  2. 02Add sessionsFixed dates, publish-now-confirm-later, or bookable slots, each pinned to its chart.
  3. 03Walk the checklistVenue, pricing, theme, holds. The guided checklist catches what's missing.
  4. 04Publish with previewSee the storefront exactly as buyers will, then flip the status.

Run your next event on it

Create an event and take it to published in the demo workspace.