2D Map
Floor navigation, availability, accessible inventory, and exact seat selection.
ARENA & STADIUM SEATING SOFTWARE
Stadium-scale seating. Every seat connected.
Explore a 53,018-seat stadium and a 13,784-seat arena. Reuse venue geometry, offer immersive 3D, and connect web, mobile and partner sales to the same event inventory.
Discuss a large venue →Go live for $0 in standard Platform/SDK mode. Every organization receives 100 free sold-seat credits monthly; buy non-expiring credits when needed. Your platform keeps commerce. Managed Ticketing is available for eligible events after staff enablement, with separate Hosted Ticket pricing.
MULTI-FLOOR AUTHORING
ZONE → SECTION → SEAT
COMPLETE 2D BASELINE
FOOTBALL STADIUM · 3D VENUE VIEW
RELEASED PRODUCT
53,018 seatspublic stadium fixture
13,784 seatspublic arena fixture
17.6 ms p9553K zoom / selection · 27 Aug
Renderer performance methodhardware · loading · frame rates
READABLE AT EVERY SCALE
Show the right detail for the decision in front of the buyer.
Progressive rendering makes venue sections usable before every seat is drawn. Viewport detail keeps the current seating block readable; instanced 3D seats and bounded near-camera detail support large bowls without duplicating the inventory model.
-
01 · ZONES
Choose a part of the venue.
Use buyer-readable venue regions—lower bowl, upper deck, a named stand, or your own zone model—to establish direction first.
WHOLE-VENUE CONTEXT -
02 · SECTIONS
Enter the right seating block.
Keep the section name, availability, and category context readable before the buyer enters the individual rows.
BLOCK-LEVEL CHOICE -
03 · SEATS
Finish on exact inventory.
Labels, accessibility, category, and live free, held, sold, or blocked state become actionable at selection scale.
EXACT LIVE SEAT
Optional 3D adds orientation, not a second seat map. A known seat can be opened with a direct 3D flight, while the same selection and live status remain available in 2D.
The 27 August desktop run measured 17.6 ms p95 for zoom and selection at 53,018 seats. A separate 4 August M3 Pro / Metal run recorded sustained 60 FPS during scripted 3D orbit and fly-to-seat. These are dated buyer-rendering measurements, not a device-wide promise or concurrent checkout test. Inspect both methods and their limits.
Evaluate the 3D buyer journey →Compare stadium and cricket virtual seat views →
ONE PUBLISHED CHART
Floors · zones · sections · seats
3D venue
Relief, level, and orientation added on request when the browser supports it.
Both views read the same event inventory and return the same selected seats.
ONE CHART · TWO VIEWS
The spatial view and the sellable map stay connected.
Author the physical venue once. Named floors, sections, zones, seats, categories, focal points, and live status serve the flat map and optional 3D experience.
- 2D remains complete. Floor switching and seat selection do not depend on WebGL2.
- 3D loads on request. Unsupported browsers continue on the standard map.
- Live state is shared. Changing view does not fork availability or selection.
AUTHOR THE PHYSICAL VENUE
Build by floor and section. Publish as one seating source.
Large charts stay manageable when the editing model follows the venue’s real structure.
Separate authoring without splitting inventory.
Each named floor keeps its own geometry, focal point, buyer background, and optional physical base height. Every floor publishes together.
Plan rows inside real boundaries.
Draw the sellable region, set target capacity and spacing, preview containment-safe rows, then apply them as editable chart objects.
Protect the labels the live event depends on.
Seat and grouped-object labels remain unique across the chart. Published safe mode protects destructive identity changes.
OPERATE CAPACITY AS ONE EVENT
Hold back a deck without maintaining a second chart.
Whole-section availability rules and exact-seat blocking update mounted buyer and operator surfaces through the live event stream. No account secret key belongs in the browser.
Open, close, or hide
Change a section or zone immediately. Hidden inventory leaves the buyer map; closed inventory stays visible but unavailable.
Release at a set time
Keep capacity hidden until a UTC release time, then reveal it without republishing the venue chart.
Reveal at a sold threshold
Open the next section when visible on-sale inventory reaches the configured sold percentage.
Block production inventory
Take specific seats off sale for operational reasons while keeping section-level rules distinct.
Running the house? Give operators short-lived, event-scoped access for only the live controls their role requires.
See the box-office workflow →CHOOSE HOW YOU RUN IT
Keep spatial inventory in SeatLayer. Keep the commercial relationship in your stack.
CONTINUE ON THE CANONICAL PATH
Stay here for large-venue depth. Follow the specialist question when it changes.
ARENA & STADIUM QUESTIONS
Decisions to settle before the first large event goes on sale.
Is SeatLayer suitable for a 50,000-seat stadium?
SeatLayer publishes a 53,018-seat stadium fixture and a 13,784-seat arena fixture, alongside dated buyer-renderer measurements. Progressive presentation, viewport detail and instanced 3D seating support the large-venue experience. Evaluate your own chart, devices, on-sale workload and service requirements; a renderer demo is not a simultaneous-buyer capacity guarantee.
Can SeatLayer handle multi-floor arenas and stadiums?
Yes. One chart can contain multiple named floors with independent geometry, focal points, and physical elevation. The floors publish together and share one event inventory.
How do buyers navigate a very large seating chart?
The buyer map changes detail as the view moves closer: zones establish the part of the venue, sections establish the seating block, and exact seats appear when they can be read and selected clearly.
Is 3D required to select a seat?
No. The complete 2D map and floor controls remain available. Optional 3D is lazy-loaded only when requested and only appears on browsers that support WebGL2.
Can operators hold back or release whole sections?
Yes. Operators can open, close, or hide sections immediately, or configure timed and sold-threshold release rules. Individual production holds use seat blocking.
Does SeatLayer replace our ticketing or venue-management system?
In SDK mode, no. SeatLayer owns the seating chart and live event inventory layer while your host system keeps payment, orders, ticket delivery, refunds, patron records, scheduling, and customer service. Teams using SeatLayer hosted reserved seating can instead run an event page, organizer-connected Stripe or Razorpay, Box Office, Control Room, and door tools. The organizer's connected provider controls processing fees, applicable taxes, and payout timing; SeatLayer bills Hosted Ticket usage separately and is not the venue CRM.
OPEN THE WHOLE VENUE
Start with the bowl. Finish with one clear seat.
Try the public 53,018-seat buyer journey, then discuss your venue, peak on-sale workload and support requirements.