Where availability becomes
How it shows up
One API, four views of the same flows
Flip through availability, payments, embed, and API, each tab is the same tenant model underneath. No second stack to maintain.
Full platform page →Interactive preview
A visitor checks open slots across resources. Your rules, time zones, and capacity stay in sync, no double bookings.
Powered by booking BaaS
Tenant previews
Widget, stays, and sessions in rotation.
Static mocks for three common verticals each backed by the same slots, holds, and webhooks you use in production.
Widget · local services
Studio North
Hair · same-day slots
Next opening surfaces from your API, no manual refresh needed.
Trusted by teams shipping production booking flows from salons to marketplaces.
Bookings orchestrated.
0M+
Across live tenants
API requests.
0M+
Served at the edge
Active businesses.
0+
Growing every week
Trusted by product teams at
Every day, millions of scheduling decisions run through software. Your product deserves a booking layer that is fast, isolated, and ready to monetize without owning the entire calendar stack.
Everything you need to accept bookings
Slots, multi-day stays, payments, and tenant isolation exposed through a single, well-documented surface.
Explore all features →Services & use cases
The same booking core powers stays, hourly appointments, and lane-based venues pick a path to see how it maps to your product.
Flexible scheduling
Time slots, nightly blocks, or custom durations — model what you sell, not what the database allows.
Mollie Connect
Checkout, Connect, and webhooks coordinated server-side with your branding on top.
Embeddable widget
Vanilla JS SDK and iframe flows that inherit your tokens and post bookings to the same API.
Tenant isolation
Row-level security patterns and scoped API keys so customer data never crosses tenants.
Concurrency aware
Redis-backed locks and idempotent writes so high-traffic launches do not double-book.
Multi-tenant by design
Create organizations, resources, schedules, and users with clear roles for ops and developers.
Patterns your team will recognise
Same primitives across embed, dashboard, and API so design and engineering stay aligned.
Open full gallery →Swipe to explore
Built for developers,
loved by operators
REST endpoints, predictable errors, and webhooks for the moments that matter booking confirmed, payment captured, slot released.
- RESTful API with idempotency keys
- Open docs and runnable examples
- Signed webhooks to your stack
- Service role paths for admin automation
// Create a booking (idempotent)
const res = await fetch('/api/bookings', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'X-Publishable-Key': PUBLISHABLE_KEY,
'Idempotency-Key': idempotencyKey,
},
body: JSON.stringify({
resource_id: resourceId,
slot_id: slotId,
customer_name: 'Alex Rivera',
customer_email: 'alex@example.com',
amount_cents: 8900,
currency: 'USD',
}),
});
const { booking } = await res.json();