# Everything SeatLayer does with a seat.

Design the room, sell the seats, run the door — and put it all in your own product. This is the full list, grouped, with links to go deeper.

_The Designer: geometry, categories and labels against live validation._

## The full list.

Six groups, every named capability in each, and the state it is in today. Each heading drops to the section that explains it; each item links out where a page goes deeper.

Released Released beta — controlled release preview — early access

### Design the venue

Go to Design the venue &darr;

Straight, curved and fanned rowsReleased Sections, shapes and labelsReleased Round and rectangular tables, and boothsReleased General admission areasReleased Accessibility seats and wheelchair baysReleased Multi-floor venuesReleased Categories, ticket tiers and price zonesReleased Validation before you publishReleased Trace a plan page or reference imageReleased Import a chart that is already publicReleased

### Buyers pick seats

Go to Buyers pick seats &darr;

Interactive 2D seat mapReleased Optional 3D view from a seatReleased Ticket types priced on the chartReleased Best-available groupsReleased Temporary holds with a timerReleased Exact seats handed to your checkoutReleased Responsive on a phone and a laptopReleased 37 buyer languagesReleased Buyer-facing accessibility filters and labelsReleased Fixed multi-performance seat selection: the same assigned seats, or a matching allocation, across listed dates.Released

### Run the event

Go to Run the event &darr;

Sales channels for sponsor, partner, presale, and box-office allocationsReleased Live availability boardReleased House blocks and guarded releasesReleased Box office counter salesReleased Door check-in and ticket scanningReleased Per-seat tickets and QR credentialsReleased Authorised performance totals and exportsReleased

### Put it in your product

Go to Put it in your product &darr;

JavaScript and TypeScript SDKReleased React wrapperReleased Vue 3 and Angular 17+Released 7 server SDKs: Node.js, Python, PHP, Java, Go, Ruby, .NETReleased REST API with an OpenAPI referenceReleased Signed webhooks with retries and a replay ledgerReleased Embedded Designer sessionReleased SeatManager embed for operatorsReleased Test mode, free and with no time limitReleased PerformanceGroupPicker for fixed, included performance runs; it is not a season or subscription product.Released

### AI and agents

Go to AI and agents &darr;

Copilot answers questions about the open chartBeta Copilot changes the open chart when you askBeta Multi-step chart creationBeta A plan or reference image as Copilot inputBeta Designer MCP for Claude and other MCP clientsPreview LLM-readable docs for coding agentsReleased

### Or let us host it

Go to Or let us host it &darr;

Hosted seated event pageReleased Checkout on a connected Stripe or Razorpay accountReleased Per-seat tickets issued for the orderReleased Box Office and Control Room on the same inventoryReleased

Reserved seating only — a published chart and exact-seat booking are required.

## Two ways in.

Most teams embed SeatLayer and keep their own commerce. Venues that do not want to build anything can run seated events on it directly.

### Building a ticketing product or platform

Embed the buyer seat picker, keep your accounts, checkout, payments, orders and tickets, and let SeatLayer run the seat map, holds, live inventory and booking.

Read these sections first: Buyers pick seats, Put it in your product, Where the line is.

### Running a venue or selling your own seated events

Publish a seated event page with hosted checkout, per-seat tickets, box office and check-in, and charge through your own connected payment account. No code.

Read these sections first: Design the venue, Run the event, Hosted seated events.

## Where the line is.

Before the detail, the split. This is what SeatLayer takes responsibility for, what stays yours, and what changes if you ask us to host the event instead.

Published chart geometry, current seat state, buyer selection, temporary holds, atomic booking, live inventory, and signed webhooks.

In an SDK integration, your application keeps buyer identity, checkout, payment, tax, refunds, orders, and ticket delivery. Pricing authority stays with you.

For hosted reserved-seating events, SeatLayer can provide the event page and checkout while payment runs through the organizer's connected Stripe or Razorpay account.

Review the platform boundary

## Draw the venue once.

A chart is authored in the Designer and frozen as a reviewed revision. Publishing is a separate, deliberate step, and every surface downstream reads the revision you published.

- Rows, sections and labels — straight, curved or fanned rows with true arc geometry, named the way the house names them.
- Tables, booths and general admission — round and rectangular tables, booths, and capacity zones beside reserved seats on the same chart.
- Accessibility and multiple floors — accessible seat types that become buyer-facing filters, wheelchair bays kept distinct from seats, and stalls, circles and balconies as one venue.
- Categories and validation — price zones painted onto the chart with per-seat overrides, and warnings raised while you work rather than after you publish.
- Start from what exists — trace a plan page privately, or point the importer at a chart that is already public and it lands as an editable draft. See a migration run.

Open the Designer Browse the templates

## Buyers pick exact seats.

The picker renders the published chart, prices it by ticket type, finds the best available group, and hands your checkout the exact seats plus a temporary hold. A seating event is handled by one server-side state authority: competing hold requests are ordered there, so one can succeed while a conflicting request receives a conflict response.

- Ticket types — each seat priced by the category it belongs to.
- Best available — ask for four seats together and get them held together.
- Temporary holds — a timer the buyer can see, released automatically if checkout is abandoned.
- Responsive, in 37 buyer languages — the same picker manages map, selection, cart, tiers and hold timer on a phone and on a laptop.
- Optional 3D — a view from the seat, loaded only when a buyer asks for it. See the 3D seat map.

### Try it here.

Nothing on this page is a mock-up. Load the released SDK against the fixed Grand Theatre v2 fixture; the complete 2D picker mounts first, and optional 3D appears only when this browser supports it.

#### Try the released picker — 2D map, then 3D from the seat.

Demo inventory is local to this tab, and the fixture panorama is a clearly labelled AI-generated stand-in rather than a certified sightline. Read the full provenance note on the home page.

See the 3D seat map Read the SDK quickstart

## Run the event on the same inventory.

Watch availability move in real time, block or release seats, sell at the counter and check people in at the door. Box Office, Control Room, blocks, releases, and door activity share event inventory.

- Live board — open, held, sold and blocked seats for authorised operators, without handing over admin authority.
- Blocks and releases — hold back house seats and put them back through guarded actions.
- Box office — serve the walk-up audience, record the external tender, and create the real order with per-seat tickets.
- Door — scan the ticket credential and keep check-in state separate from sale state.
- Tickets and reporting — per-seat tickets with QR credentials, plus authorised performance totals and exports.

_The event workspace: live board, availability tools and reports._

See Box Office See venue operations

## It drops into your product. Your checkout doesn't move.

A short-lived, origin-bound session mints the embed. Selection and holds happen in the browser, booking is confirmed from your server, and signed webhooks tell you when inventory moves. Transactional embedded buyer flows use the JavaScript SDK or React wrapper. The group picker supports a fixed multi-performance run.

```
$ npm install @seatlayer/js
import { SeatPicker } from '@seatlayer/js';
const picker = new SeatPicker({
  container: '#seat-picker',
  event: 'ev_9f3a',
  onCheckout: (_, __, handoff) =>
    yourCheckout(handoff.holdId),
});
picker.render();
```

- Client SDKs — JavaScript and TypeScript, React, Vue 3, and Angular 17+.
- Server SDKs — Node.js, Python, PHP, Java, Go, Ruby and .NET.
- Any other backend — every route stays available through REST and the OpenAPI reference.
- Signed webhooks — HMAC-signed delivery with retries and a replayable attempt ledger.
- Embedded surfaces and test mode — an origin-scoped Designer session for organisers, an event-scoped SeatManager embed for operators, and a free test mode with no time limit.

_Session minting and the origin-bound embed boundary._

_Signed delivery, with retries and a replayable ledger._

Read the integration guide Read the OpenAPI reference

## Ask the chart. Then tell it what to change.

Copilot works inside the Designer on the chart you already have open, and a compatible MCP client can work through one chart scope you authorise. Every change lands as a revision a person reviews and publishes.

### In the Designer

Copilot beta can change the open chart when you ask it to, and every change is a reviewable revision you publish. It can also answer questions about the chart without touching it.

### From Claude or another MCP client

Designer MCP Preview lets a compatible MCP client work through one authorised chart scope. Publishing stays a human action.

### For your coding agent

The docs are published as LLM-readable Markdown, so the agent integrating the SDK reads the same source humans do.

## Or let SeatLayer run the seated event.

SeatLayer provides the event page and checkout, charges through the organiser's connected Stripe or Razorpay account, issues per-seat tickets, and keeps Box Office and Control Room on the same live inventory.

Reserved seating only — a published chart and exact-seat booking are required.

1. Publish the seated event page.
2. Connect the organiser's payment account.
3. Sell exact seats and issue tickets.
4. Keep online and counter inventory together.

## Product boundaries, without the fine-print hunt.

The questions that decide whether this fits, answered in one place.

### Does SeatLayer replace my checkout system?

You choose. In an SDK integration, your application keeps buyer identity, checkout, payment, tax, refunds, orders, and ticket delivery. For hosted reserved-seating events, SeatLayer can provide the event page and checkout while payment runs through the organizer's connected Stripe or Razorpay account.

### Does optional 3D replace the 2D seat map?

No. The complete 2D Map remains available. Optional 3D uses the same published chart and selection state, loads only after a visitor asks for it, and is offered when WebGL2 and the evaluated browser context support it.

### How does SeatLayer handle two buyers asking for the same seat?

A seating event is handled by one server-side state authority. Competing hold requests are ordered there, so one can succeed while a conflicting request receives a conflict response. A trusted server confirms the commercial sale after checkout succeeds.

### Which integration paths does SeatLayer support?

Transactional embedded buyer flows use the JavaScript SDK or React wrapper. The Designer uses a short-lived, origin-scoped session inside an organizer CMS. Hosted reserved-seating event pages are a separate path for organisers who want SeatLayer to provide the buyer site and checkout.

### Which SDKs and languages are published?

Client-side: JavaScript and TypeScript, React, Vue 3, and Angular 17+. Server-side: Node.js, Python, PHP, Java, Go, Ruby, and .NET. Any other backend can use the REST API and its OpenAPI reference directly.

### Can an agent or MCP client work on my chart?

Designer MCP Preview lets a compatible MCP client work through one authorised chart scope. The agent can read the chart and prepare changes as a revision; publishing stays a human action. The docs are also published as LLM-readable Markdown for the coding agent integrating the SDK.

### Can a venue reuse one chart for multiple events?

Yes. A venue chart can be published as a reusable version, while each event adds its own pricing and seat inventory. That separates stable venue geometry from the open, held, sold, and blocked state of a particular event.

### Can I try it before paying?

Yes. Test mode is free, with no time limit and no card. Live accounts also receive 100 free credits each month, and a credit is used only when a seat is newly confirmed as sold.

## Start with the part you need.

Open the demos and click through the released picker, or read the quickstart and put it in your product this afternoon.

Just need a chart? The free seating chart maker needs no account.

---

_Machine-readable site index: [/llms.txt](https://seatlayer.io/llms.txt) · full corpus: [/llms-full.txt](https://seatlayer.io/llms-full.txt)_
_Source page: [https://seatlayer.io/features/](https://seatlayer.io/features/) · Questions: [Contact SeatLayer](https://seatlayer.io/contact/) · hello@seatlayer.io_
