Platform
Hold timers that match how you sell.
Per-seat countdowns for hot onsales, a shared cart timer for leisurely bookings. Set the policy per workspace, override per event, and watch the lifecycle over signed webhooks.
Sound familiar?
Holds that never die
A browser tab left open shouldn't park your best seats forever. Every hold carries a TTL. Expiry releases it automatically.
Seat timers vs cart timers
A concert drop needs each seat counting down; a spa booking wants one timer for the whole basket. Both are first-class modes.
The onsale surge
Ten minutes of madness, then silence. Hold policy tuned per event keeps the hot minute fair and the quiet days relaxed.
Hold policy as configuration
01Two timeout modesPer-seat countdowns or one shared cart countdown, a workspace default with per-event overrides.
02Sane bounds, real defaultsFrom 60 seconds to a full hour, defaulting to five minutes, short enough to be fair, long enough to check out.
03Automatic expiryTTLs end holds by themselves; an idempotent sweeper broadcasts the release so every map updates.
04Frozen during paymentA seat in an active payment can't expire from under the buyer. The hold freezes until the saga resolves.
05Observable lifecyclesession.held and session.released webhooks let your own systems follow every hold, signed and retried.
06Hot-event readyFlag an event as hot and its hold traffic routes to dedicated capacity, configured per session.
Tune a hold policy in minutes
- 01Pick the modeSeat or cart: set the workspace default once.
- 02Set the clockChoose the timeout; override it per event when the onsale demands it.
- 03Watch it workMaps countdown live, expiries release automatically, webhooks keep your systems in sync.
Set your hold policy
Modes, timers, and lifecycle webhooks, in the demo.