The Bookesto booking desk holds each slot the moment it is chosen.

Five capabilities have shipped.

Each is marked shipped on Bookesto's public status ledger.

• Availability

  Venue hours and staff shifts are intersected in the resource's own timezone and re-derived across daylight-saving changes, with buffers either side of each service. One booking can need a room, a person and a machine at once.

• Holds

  Choosing a time places a hold with a visible expiry. A PostgreSQL exclusion constraint refuses any overlapping booking, so the database itself stops a double booking.

• Guest booking

  The customer books without an account: catalogue, slot, visible hold, a confirmation that a retry cannot duplicate, and a private link to view or cancel.

• English and Arabic

  Right to left from the first commit, with the layout mirrored and digits set for Gulf commercial practice. Screenshot tests hold it in place on every release.

• Tenant isolation

  Row-level security forced in PostgreSQL, with separate runtime, sign-in and schema-owner database roles.

Everything else is marked in build, planned or gated.

Bookesto labels each capability on the page that describes it, and this table follows its public ledger.

Availability depends on the room's own clock.

A slot is bookable only where venue hours, the staff member's shift, buffers and every required resource overlap, computed in the resource's own timezone. The UAE keeps its clocks fixed all year. A customer booking from abroad, or a branch in a country that changes its clocks, meets days 23 or 25 hours long.

Timezone rules are kept in the IANA time zone database, and they change. Bookesto re-derives its slots across each daylight-saving change, so a time shown to a customer anywhere is true in the room.

The database enforces every hold.

Two customers can press the same time in the same second, and a retry or a double tap can send one request twice. Code that checks availability and then writes leaves a gap between the two.

Bookesto closes that gap twice. A hold with an expiry reserves the slot while details are typed, and a PostgreSQL exclusion constraint refuses any overlapping booking even when the application errs. Confirmation is idempotent, so a retry cannot create a second booking.

Early access is open and asks for no card.

Join the list on bookesto.com to get the build log first and the beta after it. Nothing can be bought yet.

Bookesto is pre-launch and has no customers yet, which its own site states.

SolaryxDev runs Bookesto as a product.

Booking systems are no longer built to order. Bookesto is one booking core that we run for service businesses to use. Where booking is only part of a larger system, we scope the whole as a custom web application, and the rest of a practice is covered under clinics and healthcare.