Skip to content
Bookesto

Product

The booking page and the day desk, on one record.

Bookesto starts with the job a local service business repeats every day: publish accurate availability, accept a guest booking, see what needs attention and keep the customer history inside the merchant's own workspace.

Join early access

No card. Merchant access is invite-only — you get the build log and first access.

One customer, one booking record

The customer, service, staff member, venue-local time, policy and every status change belong to the same booking. Bookesto keeps that record inside one tenant boundary, so the public page and the merchant desk read the same operational truth.

Customer
The guest and their private booking history inside one merchant workspace
Service
What can be booked, for how long, at what price and with which resource
Availability
The intersection of venue hours, staff shifts, buffers and timezone
Booking
The customer, service, resource, local time, policy and audit history
Payment
The policy state today; live capture and refunds remain gated
Tenant
The boundary all four sit inside, enforced by the database, not by application code
A dark, empty room lit only by one shuttered window and a narrow band of light falling across a rug on the floor.
A salon before opening: a row of styling chairs facing lit round mirrors, every station empty and set.

What is built, precisely

Every Bookesto capability with its build status and what exists in the codebase today.
CapabilityStatusWhat exists today
Availability engineShippedTimezone and DST-aware slot generation, buffers, compound resources
Holds and concurrencyShippedAtomic Redis holds plus a Postgres exclusion constraint
Booking, guest manage and cancelShippedPublic catalogue, availability, rate-limited hold, idempotent create, guest cancel
Tenant isolationShippedForced row-level security on 105 tables, three separated database roles
English and Arabic interfaceShippedRight-to-left throughout, 12 screenshot cases passing
Deposits and no-show protectionIn buildPolicy resolution exists; charge capture is being written
WhatsAppIn buildOfficial Meta Cloud API adapter, disabled until a verified business account exists
Team scheduling and calendar syncPlannedSpecified. Microsoft Graph first, Google after verification
Routing rules and distributionPlannedSpecified, including weighted distribution and a fairness ledger
Shared inboxPlannedSpecified. Chatwoot Community Edition as the agent surface
AI agentGatedBlocked on a commercial API runtime, a signed DPA and a budget cap
SSO, audit log, EU residencyPlannedSpecified for the top plan

Distinct ALTER TABLE … FORCE ROW LEVEL SECURITY statements in packages/db/prisma/migrations

Status verified against the build on 2026-08-19. The changelog records every change to this table.

  • AvailabilityShipped

    Offer times that are true for the venue and the staff member.

    Venue hours and resource shifts intersect in the venue timezone, with service buffers and daylight-saving transitions handled by the engine.

    The core runs in production. A local correction for resource-specific shifts and venue-time display still awaits the current promotion gate.

    Availability evidence
  • HoldsShipped

    Keep two customers from taking one slot.

    Selecting a time creates an atomic hold with a visible expiry. A database constraint refuses an overlap even when two requests arrive together.

    The production booking round trip has been verified; concurrency and retry behavior remain part of every release gate.

    Hold evidence
  • Guest bookingShipped

    Let a customer book and manage the visit without an account.

    The public flow covers the catalogue, availability, hold, idempotent confirmation and a private manage link for viewing or cancellation.

    It is guest-first by design. Consumer accounts, a marketplace and cross-merchant discovery are deliberately outside the first proof.

    Booking-flow evidence
  • Merchant workspaceIn build

    Run the day from bookings and exceptions, not vanity charts.

    Today, Calendar, booking detail, Customers, Services and guided Setup form the local beta surface, with role-aware tenant access.

    This slice is not the production panel yet. Manual booking, rescheduling, full team and hours management, export and browser acceptance remain before a design partner can self-operate.

    Workspace status
  • Deposits and no-showsIn build

    Attach a cost to not turning up.

    Deposit policy resolves on the booking record. The intended architecture settles through the merchant's Stripe account rather than a Bookesto balance.

    Live capture, webhooks, refunds, reconciliation, disputes, approval and the commercial fee model remain gated. Nothing can be bought today.

    Deposits

English and Arabic · every timezone

Shipped

The booking must read correctly on both sides of the counter.

Bookesto uses logical layout from the first commit and keeps every slot as an instant plus its IANA timezone. The booking surface supports English and Arabic directionality; public Arabic marketing remains unpublished until a native review is complete.

Interface languages at launch
English, Arabic
Direction
Left-to-right and right-to-left, one codebase
Time storage
UTC instant plus the IANA zone identifier — never a numeric offset
DST coverage
Both switchover weekends per launch region, in the test matrix

Not on the roadmap

A product that says yes to everything is a product with no shape. These are out of scope by decision, not by omission.

A consumer marketplace
The proof is the merchant's owned channel, not a directory that resells customers back
Retail POS, inventory or payroll
Those are specialist operating systems, not unfinished tabs in the first booking proof
Clinical records
Health records and clinical workflows require a separate regulatory and product program
Full restaurant, court, tour or venue operations
Each vertical needs its own acceptance pack before Bookesto can claim replacement depth
An AI receptionist in the proof release
It remains off until a commercial runtime, DPA, budget cap, disclosure and human handoff exist

Get the build log and first access

The booking core is live and merchant access is invite-only. Get the changelog as it happens and an invitation when the private beta is ready for your business.

Join early access

No card. Merchant access is invite-only — you get the build log and first access.