Skip to content
Bookesto
A dining room laid up before service, the camera moving slowly through it
Barber chairs along a tiled floor
Tattoo studio, dark walls hung with flash, the floor clear
Salon floor, chairs empty, mirrors lit
Nail stations in a black and white salon, every chair empty
Courts from directly overhead
Treatment room under an arched ceiling

Pre-launch · build in progress

In build

Open the day.Hold the slot.Run the booking.

Bookesto is becoming the owned-channel booking desk for service businesses. The core runs today: timezone-correct availability, atomic holds and guest cancellation in English and Arabic. The merchant workspace and payment path are still being completed.

Join early access

No card. Nothing to buy yet. Every capability below carries the status it actually has.

Where we actually are

Zero customers, zero funding, one operator. Here is what is running today.

See the full status ledger

The problem

The booking is simple. The handoff around it is not.

A customer asks on Instagram or WhatsApp. Somebody checks a paper diary, messages a staff member, copies the appointment into a calendar and hopes the slot has not already gone. A reschedule repeats the same chain in reverse.

The customer needs one accurate page. The owner needs one calm view of today: what is next, what needs confirmation and which booking has no staff member assigned. No marketplace or all-in-one promise is required to solve that job well.

An empty room in near-darkness, its only light falling through one shuttered window.Low morning sun crossing the floor of an empty room through a long band of windows.
Scattered intake
Phone, Instagram, WhatsApp and walk-ins all compete with the same diary
False availability
Opening hours are not enough when each staff member works a different shift
Day-of work
Confirmations, unassigned bookings and cancellations need one queue

This is the room.

Barber chairs along a tiled floor
Tattoo studio, dark walls hung with flash, the floor clear
Nail stations in a black and white salon, every chair empty

Whatever it is called, it books the same way: choose the space, hold it while the details are entered, and settle the money into the merchant’s own account.

  • Availability. Correct in the room's own timezone, including the days that do not have twenty-four hours.

    Shipped
    • Slots re-derived across daylight-saving transitions
    • Buffers before and after, per service
    • Compound resources: a room, a person and a machine at once

  • Holds. A slot is reserved the moment it is chosen, and released if the booking is abandoned.

    Shipped
    • Atomic hold with a visible expiry
    • Database-level constraint refuses an overlap
    • Retries and double taps cannot create two bookings

  • Deposits. Policies resolve today; the live charge and refund path is still gated.

    In build
    • Direct-to-merchant settlement is the intended architecture
    • Platform pricing is not published
    • Stripe approval, charge capture and refunds remain launch gates

The part that already runs

Everything below is a screenshot of the live product.

Not a rendering, not a concept. Each one carries the status it actually has.

Availability

Shipped

Times that are true in the room's own timezone.

Slots are generated in the resource's timezone and re-derived across daylight-saving transitions, with buffers and compound resources. A room, a person and a piece of equipment can all be required for one booking.

The same booking page after choosing a service, showing selectable times.

Holds

Shipped

Two people cannot take the same slot.

Choosing a time places an atomic hold with a visible expiry. Underneath, a Postgres exclusion constraint refuses an overlapping booking at the database — so it is impossible, not merely unlikely, and it does not depend on application code being correct.

The booking page for a salon, listing one service with its price and duration.

English and Arabic

Shipped

Right to left from the first commit, not a later port.

The whole booking surface runs in Arabic with the layout mirrored and the digits set for Gulf commercial practice. Twelve screenshot cases hold it in place on every release. Almost nothing else in this category ships it at all.

The same booking page in Arabic, laid out right to left.

What it is

One booking core. One operational day.

Bookesto starts with the owned booking page and the daily desk behind it. The first three capabilities run in production; the workspace and payment path remain visibly in build.

  • AvailabilityShipped

    Offer times that are actually bookable.

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

    Availability evidence
  • HoldsShipped

    Keep two customers from taking one slot.

    An atomic hold protects the selected time while checkout finishes, and the database refuses an overlapping booking.

    Hold evidence
  • Guest bookingShipped

    Let the customer book without an account.

    Catalogue, slot choice, visible hold expiry, idempotent confirmation and a private link to view or cancel the booking.

    Booking flow
  • Merchant workspaceIn build

    Run the day from exceptions, not vanity charts.

    Today, Calendar, booking detail, Customers, Services and guided Setup are implemented locally and still need the production acceptance gate.

    Workspace status
  • Deposits and no-showsIn build

    Attach a cost to not turning up.

    Policy resolution exists. Stripe approval, capture, refunds, reconciliation and the fee model remain launch gates, so no live-payment claim is made.

    Deposits

Shipped today

Shipped
Availability engine
Timezone and DST-aware slot generation with buffers and compound resources
Concurrency
Atomic holds in Redis plus a Postgres exclusion constraint — double-booking is impossible at the database level
Tenant isolation
Forced row-level security on 105 tables, with separate runtime, auth and owner database roles
Languages
English and Arabic, right-to-left, verified across 12 screenshot cases
Rooftop tables at night above city lights

The booking core runs today. The rest is being built in the open.

  • Guest checkout with no account, on a page that loads in under a second

  • A hold with a countdown so a slot cannot be taken while the details are typed

  • English and Arabic right to left, verified on every release

Join early access

No customers yet

We would rather show you the build than a logo we do not have.

Bookesto has no customers, no funding and no reviews. We are not going to manufacture any. What exists instead is a dated changelog and a status ledger that marks every capability shipped, in build, planned or blocked. If a capability is not built, this site says so on the page where it is described.

  • Changelog

    Every release, dated, with what actually changed.

    Read the changelog

  • Roadmap

    Every capability with an honest status and the gate that blocks it.

    See the ledger

  • The operator

    One person builds this. Named, reachable, and the one who answers your email.

    About

Signed

Bookesto is built and run by one operator at AL MANNAN GENERAL TRADING FZE-LLC in Sharjah. If you email hello@bookesto.com, that is who replies.

Open the day. Hold the slot. Run the booking.

Pre-launch. Join the list and you get the build log, then the beta.

Join early access

No card. Nothing to buy yet.

A hotel reception desk under pendant lamps, with nobody standing behind it.