Platform
Venues are master data, not per-event chores.
Define a venue once, its chart, seat categories, geo, and timezone, then let every event pin it. Sister workspaces can share it read-only; nobody can double-book it.
Sound familiar?
Re-entering the venue per event
Address, timezone, map, categories, copied from the last event and quietly drifting. Master data exists so you type it once.
The double-booked hall
Two events, one room, one awkward phone call. Venue allocation is enforced by a database constraint, not by remembering to check.
Go-live surprises
A venue that isn't ready discovers it on on-sale day. The ready preview walks the chart, categories, and entrances before that.
One source for every space you run
01Charts where they belongThe venue owns its seat map, authored in the embedded Studio. Events pin revisions instead of copying files.
02Seat categories per venueZones and sections are venue-level data with full CRUD, ready for pricing to reference.
03Geo & timezone built inLocation and IANA timezone travel with the venue, so schedules and storefronts localize themselves.
04Allocation without collisionsExclusive venue windows are enforced in Postgres. Overlapping bookings can't be saved, let alone sold.
05Shareable, safelyWithin a tenant, a venue can be read-only shared to sister workspaces. When it isn't shared, it doesn't exist to them.
06Ready previewA pre-flight check of chart, zones, and entrances before the venue serves its first event.
From empty hall to bookable venue
- 01Create the venueType, geo, and timezone, the master record every event will reference.
- 02Chart & categorizeDraw the map in Studio and define seat categories once.
- 03Pass the ready previewVerify chart, zones, and entrances, then start scheduling against it.
Model your first venue
Chart, categories, and allocation, all in the demo workspace.