---
title: "Pricing"
description: "Understand SeatLayer usage pricing, free monthly credits, prepaid packs, and account-level add-ons."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.seatlayer.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Pricing

SeatLayer uses a prepaid credit wallet. One credit is consumed when one guest
place is first booked; rendering, holds, releases, and organizer blocking do not
consume credits.

## Monthly free credits

Each organization receives 100 free credits per UTC calendar month. The grant
is applied automatically and does not roll over as a separate allowance:
credits are added to the organization wallet once each month.

No card is required to create charts and test the integration.

## Prepaid packs

| Pack | Price | Effective price |
|---:|---:|---:|
| 500 credits | $40 | 8.0¢ per credit |
| 1,000 credits | $75 | 7.5¢ per credit |
| 5,000 credits | $350 | 7.0¢ per credit |
| 25,000 credits | $1,500 | 6.0¢ per credit |
| 50,000 credits | $2,500 | 5.0¢ per credit |
| 100,000 credits | $5,000 | 5.0¢ per credit |

Pack prices are in USD. The server catalog—not a browser-submitted amount—is
authoritative for checkout.

> **Organization wallet**
>
> Workspaces isolate charts and events, but credits and purchases belong to the
> organization. There is no separate wallet per tenant workspace.

## What consumes a credit

| Operation | Credits |
|---|---:|
| Render a chart or picker | 0 |
| Create, replace, extend, release, or expire a hold | 0 |
| Best-available hold | 0 |
| Block or unblock inventory | 0 |
| First successful booking of guest capacity | 1 per newly sold place |
| Idempotent booking replay | 0 additional |
| Cancellation | No refund of the original credit |
| Resale of already-metered inventory | 0 additional |
| Test-mode booking | 0 |

Grouped objects and variable occupancy are guest-weighted. A five-person table
booked for five guests consumes five credits, not one object credit.

## Features and add-ons

Core Designer, buyer SDK, Server API, webhooks, workspaces, and embed surfaces
use the same usage wallet. Some account capabilities can still require an
entitlement—for example, removing “Powered by SeatLayer” is enforced as a
white-label add-on at buyer-serve time. Do not treat a theme flag as proof of
entitlement.

For committed volume, SSO/SAML, an SLA, a DPA, integration support, or custom
venue design, contact
[hello@seatlayer.io](mailto:hello@seatlayer.io).

## Buy and retrieve invoices

Admins purchase packs in the dashboard. SeatLayer creates a hosted Stripe
checkout from a server-authoritative `packId`, credits the wallet exactly once
after a verified completion, and sends a purchase confirmation.

New purchases can expose a Stripe-hosted invoice or PDF. A just-completed
purchase can briefly return `invoice_not_ready`; retry the invoice action
rather than starting a second checkout.

## Plan for production

- Estimate peak sold guest capacity, not chart renders or holds.
- Keep a buffer before a high-volume on-sale.
- Monitor the organization balance, not individual workspace balances.
- Use test-mode events for integration and load validation.
- Treat public pack values as product pricing that can change; read the
  dashboard/server catalog before building an internal purchase UI.
- Confirm white-label and enterprise entitlements separately.

See the [credit model](/billing/credits) and
[test-mode authentication](/start/authentication).

Source: https://docs.seatlayer.io/billing/pricing/index.mdx