Own product / hospitality software

Beistella Booking: table reservations as our own product

Own product · Availability by table · Multi-tenant architecture · Three languages

Beistella is not a client project but our own product: a reservation system for restaurants, cafés and bars. This page shows the architecture and the decisions behind it, and explicitly no client results, because there are none yet.

Problem and starting point

A reservation is only well taken when it is clear which table is free at which time for which party. Plain time-slot counters cannot answer that: they do not know whether a party of six fits one table or needs two pushed together, and they do not stop the same table being given out twice.

Beistella starts from two decisions. First, availability is calculated from concrete tables and table combinations, not from abstract slots. Second, the system works next to the venue's till, not in place of it: the till stays, the venue only adds reservations.

This project is our own product. There is no client, no client name and no usage data. The page describes what was built, which requirements apply and where it stands on 14 November 2026.

Project scope

  • Booking page per venue: party size, date, time, details, summary
  • Reservation widget that embeds into any website
  • Guest manages the reservation through a link in the e-mail
  • Cabinet for the venue: day view, reservations, guests, statistics, settings
  • E-mails to the guest and the venue, with a calendar entry (.ics)
  • Website beistella.de in German, English and Russian
  • Interfaces and e-mails in three languages: German, English, Russian

System architecture

One backend, one database for all venues, several clients. The separation between venues sits in the data model and is checked by tests, not by discipline in the code.

  • Multi-tenant architecture — Shared database; every venue-related row carries a tenant_id and the models filter on it globally. The venue is identified by the address: <slug>.beistella.de for booking, <slug>.app.beistella.de for the cabinet, <slug>.api.beistella.de for the API. Isolation tests cover the service and public endpoints, webhooks, broadcast channels and cache keys.
  • Availability calculation — A side-effect-free core checks opening hours (including past midnight), lead time, buffer and party limits. It picks a single table first, then a table combination, then by priority and fewest empty seats.
  • Booking without double-booking — Creating a reservation takes a lock per affected day, recalculates availability inside the lock and only then saves. An idempotency key makes a repeated submission return the same reservation. Concurrent bookings are tested with two parallel processes against PostgreSQL.
  • Status model — A reservation moves through a finite state machine: requested, confirmed or declined, cancelled, seated, no-show, completed. On errors the API returns a code (for example slot_taken); the interface shows the message by code, not by text.
  • Realtime — The Reverb WebSocket server distributes changes over a private channel per venue. The event carries no personal data; the client then loads it through the API.
  • E-mail — Sent through Amazon SES. The sender is "<venue> via Beistella"; replies go to the venue's address. Delivery, bounce and complaint events come back through SNS and are assigned to the venue.
  • Clients — Vue 3 for the booking page, widget, cabinet and platform; Astro for the static website. A staff app on Expo is planned and not yet released.

Product decisions

Day plan in the dashboard

The day's reservations as a timeline per table, with key figures and the next arrivals.

Floor plan editor

Tables, zones and groups are drawn in the editor; the plan can be saved as a draft and published.

Live view of the floor plan

For a chosen time, the plan shows which tables are free, soon reserved, reserved or occupied.

Booking page for guests

Guests choose party size, date and time; unavailable times are struck through.

Widget on the venue's website

The same booking can be shown as a window over the venue's website or embedded in the page.

Widget embedded in the page

The reservation widget embedded directly into a website.

Registration by invitation

The form with invitation code, venue name and booking page address.

Availability by table, not by slot

A reservation occupies a table or a table combination for a duration that depends on party size. The guest only sees times for which a placement actually exists.

Errors by code instead of text

Every conflict, such as a table taken in the meantime, arrives from the API as a machine-readable code. The interface turns it into a message with a way out: another time, another table.

Reservation link without a referrer leak

The management link carries a token; while the page is open it sends no referrer, and only a hash of the token is stored in the database. The guest can change or cancel the reservation until the deadline the venue sets; for a completed or cancelled reservation the link answers "gone" (HTTP 410).

Frugal guest data

Personal data is anonymised overnight after the configured retention period. The CSV export is protected against formula injection.

Next to the till, not instead of it

The product does not ask the venue to change its till system. The venue takes reservations and leaves everything else as it is.

Technical implementation

Backend

  • Laravel (PHP) as the single source for data, status, permissions and e-mail
  • PostgreSQL, Redis, Reverb for realtime
  • Layers: an Action changes data, a Query reads, a Service talks to external systems
  • Schema changes follow expand/contract: rolling back the code does not roll back the schema

Interfaces

  • Vue 3 with TypeScript, Vite, vue-i18n and Tailwind
  • Astro as a static website
  • Playwright tests with an axe accessibility check

Operations

  • Hetzner (VPS) with Docker Compose
  • Releases through signed version tags
  • Website: the Content-Security-Policy allows only own sources (checked on the response headers on 14 November 2026)

Quality requirements (set targets, not measurements)

  • Size budgets: booking form at most 120 KB gzip, widget at most 10 KB
  • WCAG 2.1 AA as the minimum, keyboard and screen reader operation
  • Website without cookies and without requests to third parties before the visitor consents; an automated test checks this on every page

Status

Status: 14 November 2026. Beistella is our own product. There are no client results to report here; instead this section lists dates and facts that can be checked.

  • 29 October 2026: website beistella.de published
  • By 11 November 2026: booking page, widget, cabinet and platform deployed to the production environment (version 1.1.1)
  • 13 November 2026: website released in full ("live") mode
  • Registration for venues: not open yet; the website currently offers an "early access" request button
  • Price: online reservation is currently free of charge; prices for later modules have not been set
  • Not yet released: staff app (Expo) and the graphical floor plan in the cabinet (built, rollout pending)
  • No client venues, no usage figures, no reviews, no awards

What this page does not show

  • No client results: there are no venues using Beistella in production that we could report on yet.
  • No measured load times or Lighthouse scores: only set requirements are named.
  • No statement about later modules or their prices.
  • The screenshots come from a test environment with fictitious data (taken on 14 November 2026).

Frequently asked questions

Is Beistella a client project?

No. Beistella is our own product. There is no client, and this page names no client results.

How does Beistella prevent double-booked tables?

Creating a reservation takes a lock per affected day, availability is recalculated inside the lock, and only then is the reservation saved. A repeated submission with the same idempotency key returns the same reservation.

What does Beistella cost?

Online reservation is currently free of charge. Prices for later modules have not been set.

Plan your own product or a similar system

If you are planning a system with several tenants, availability logic or realtime interfaces, we clarify data, architecture and quality requirements before any code is written.