Sell the seat, show the view.
Buyers pick their seats in a 3D model of the venue, look at the stage from the seat before they pay, and check out on your site.
Live seat mapOne iframe and a few messages: your payments, your customers, your inventory.
26,644seats in the stadium concert template, every one with a ticket id
Buyers pick their seats in a 3D model of the venue, look at the stage from the seat before they pay, and check out on your site. The map never takes money; your checkout runs as it does today.
What it does for you.
Every chair in the stands, on the floor and at banquet tables is a ticket.
(01)Pick in 3D
Every chair in the stands, on the floor and at banquet tables is a ticket, coloured by price tier and availability. Buyers pick seats themselves or ask for the best block of N together.
(02)See it before paying
One tap puts the buyer in the seat, looking at the stage and screens. They know what they are buying, so there are fewer surprises at the gate and fewer "I could not see" complaints to handle.
(03)Sell the better seat
Comparing the view from Regular and from VIP makes the difference obvious. Tiers, prices and section assignments are set per event by the organiser.
(04)Standing, access and the door
Standing tickets by tier with a quota, wheelchair spaces sold with a companion seat, QR e-tickets checked in on phones at the gate, and a live event-day view of who is inside.
Try the seat map.
Click seats or use Best available, then the eye icon for the view from the seat.
Embed
How the integration works: embed, listen, confirm.
-
Step 01Embed the seat map
An iframe on your event page. Nothing to install.
-
Step 02Sync availability
Send what is already sold or held in your system; the map colours those seats.
-
Step 03Take the payment
When the buyer reserves seats you get a hold message with seat ids and total. Your checkout runs as usual.
-
Step 04Confirm
Tell the map the payment went through; it issues e-tickets with QR codes and sends you the order.
Integration in three messages
- map → you
previz:holdthe buyer reserved these seats (ids, total, expiry): start your checkout- you → map
previz:paidthe payment went through (buyer, your reference)- map → you
previz:purchasedthe order with ticket codes, to store on your side
Plus previz:status to sync sold and held seats from your system, and previz:inventory for the full seat list.
For your developers
The embed URL, seat ids, every message and its payload, a typical flow and the share-link format are on the developers page.
Your checkout stays yours.
- You keep
Your side of the sale
Payments and payouts, customer accounts and data, the master inventory, fees and refunds, your brand around the map.
- We provide
The venue and the map
The 3D venue and layout for each event (traced from site plans and maps), seat ids and tiers, the view from the seat, e-ticket rendering, and updates when the organiser changes the plan.
Security & data.
What the seat map does and does not hold.
- 01.EmbedOrigin allow-list
For a live on-sale the seat map talks only to the sites you register: messages from any other origin are ignored and its own messages go only to your origin. Registered per partner before the first on-sale.
- 02.PaymentsMoney never touches the map
The map never sees card or mobile-money details. It reports the held seats and waits for your
previz:paid; your payment provider, fees and receipts stay as they are. - 03.InventoryYour system is the source of truth
Sold and held seats come from you with
previz:status. The map colours them; it does not overrule your inventory. - 04.DataWhat the seat map stores
Seat ids, tiers and prices for the layout, the buyer's selection and hold, and for a completed order the name, phone and email you pass with
previz:paidand the ticket codes. Nothing else about the buyer. - 05.Demo limitsToday's version, honestly
The seat map only talks to the sites on the event's allow-list, and opens view only anywhere else. Holds and sales are still kept in the buyer's browser until the server version, so a sale must be confirmed by your own system; server-checked holds are on the roadmap.
- 06.PaperworkPolicies
A data processing addendum (you are the controller for buyer data), a ticket terms template and our security overview. Drafts for legal review.
Partner plans.
See all plansPer event
Example- One venue layout modelled for the event
- Embedded seat map and the view from the seat
- Price tiers and sections set with the organiser
Partner
Example- A library of your regular venues, kept up to date
- Availability sync with your system
- Your branding around the map
Enterprise
Example- Server-side holds and sales against your API
- Organiser tools for your promoters
- Support terms to suit your on-sales
Questions ticketing teams ask.
01.Do we have to change our checkout?

No. The map never takes money. It tells you which seats the buyer reserved and waits for your confirmation (previz:paid). Your payment page, fees and receipts stay as they are.
02.Where is the seat inventory kept?
You stay the source of truth: send sold and held seats with previz:status and ask for the full seat list with previz:inventory to load into your system. In the current version the map also keeps holds and demo sales in the buyer's browser; a shared server store plugs into one adapter, and then holds are checked on the server.
03.Which venues are available?
Stadiums, halls and ballrooms, and open-ground sites. New venues are traced from the site plan and street maps. See the templates for the ones already modelled.
04.Does it work on phones?
Yes. The map runs in the browser with WebGL and drops to a lighter quality on small touch devices. No app to install.
05.What happens when the organiser changes the layout?
Floor seat ids follow the published layout, so publish the layout before the on-sale. Stand seats keep their ids. Changes after the on-sale should be agreed with you so sold seats are not moved.
06.Can buyers see the stage in AR?
Not in the current version. An AR preview is on the roadmap.
07.Can we try it first?
Yes: the partner demo is a mock ticketing checkout driving the real seat map through the messages above. Pick seats, reserve them, pay with the fake form and see the order and e-tickets come back.

One model for the organiser.
The same model is the organiser's production plan: stage and kit, sightlines, sound, crowd and exits, a capacity & safety sheet, an equipment list and CAD export. Your seat map is always the layout they planned and approved.
For planners & productionPut 3D seat maps on your next on-sale.
Tell us the venue and the date. We will model the layout, set it up with the organiser and send you the embed link to test.
