The booking engine you should not have to write again

Description and use

Bookrail is an open‑source booking infrastructure that removes common pain points—double bookings, idempotency, policy snapshots, and daylight‑saving handling—by enforcing guarantees in the database and providing a robust API, CLI, SDK, and agent server.

Problem

Developers building booking products face eight common problems—concurrency, double bookings, time‑zone shifts, policy changes, idempotency, cancellation rules, availability reporting, and API consistency—leading to frequent rewrites.

Outcome

Bookrail eliminates the need to re‑implement core booking logic, reducing development time, preventing double bookings, ensuring policy consistency, and handling daylight‑saving transitions correctly.

Workflow

• 1. Define resources and capacities in Bookrail’s PostgreSQL schema.
• 2. Use the CLI or SDK to create a project and describe the booking product.
• 3. Expose the Bookrail API (api.bookrail.dev) to the front‑end or agent.
• 4. Make booking requests with Idempotency‑Key headers to ensure single creation.
• 5. Query availability with the explain flag to see why slots are occupied.
• 6. Rely on Bookrail’s built‑in policies and time‑zone logic for consistent behavior.
• 7. Integrate coding agents via the MCP server to automate product setup and bookings.

Evidence

Zero double bookings. A resource with capacity 1 has a PostgreSQL exclusion constraint on its occupancies.

Source

Idempotent by construction. Every POST accepts an Idempotency-Key.

Source

Time zones done properly. Schedules live on a local clock… materialised into UTC day by day from the IANA database.

Source