Jan 2026 – Present11 moGastova · Founder, own product
A back-office platform for gastronomy venues, planned during my sabbatical and built end to end since.
Gastova · Founder, own product
A back-office platform for gastronomy venues, planned during my sabbatical and built end to end since.
Berlin, Germany
It solves a real problem for venue owners, and it’s where I keep my architecture and tooling current. Soft-launched with pilot venues.
Isolation per venue
- Each venue gets its own namespace, database, encryption keys and service identity, and its services scale to zero when the venue is closed
Identity
- One account for a person across every venue they work at
- Credentials and token issuing split into separate self-hosted services (Ory Kratos and Hydra)
- Venue access checked on each request instead of being written into tokens, so switching venue costs no new token
Authorization
- Task-based authorization on SpiceDB: staff get access through the tasks they’re assigned (“count the till tonight”), and that access opens and closes with the shift. There are no fixed roles
Encryption
- Envelope encryption with Vault and Asherah: a key hierarchy per venue, with keys bound to data categories so the payroll key cannot open invoices
Compliance
- GDPR and German retention law (AO, HGB, GoBD) built into the data model: employee records can only be added to, never edited or deleted, and where the law requires records to be kept, a deletion request restricts access instead of deleting
- An audit trail that shows any tampering
Finance
- A double-entry ledger that fits how bars actually run: every entry is permanent, a repeated request is never recorded twice, transfers are never blocked on balance, and a separate account absorbs till-count differences
Infrastructure
- Moved the platform from Hetzner Cloud to a Proxmox cluster on Hetzner dedicated servers, managed with Ansible and Flux
CRM
- Self-hosted Twenty as the company CRM, replacing Attio, and built a Twenty app on it: custom objects for customers, venues and promo codes, with their views and record pages
- A public intake endpoint that records website enquiries as people, companies and notes, with a honeypot against spam
- Venues synced from the platform into Twenty over an OIDC service connection
How it’s built
- LLM agents as the development team, working to written specs and coding standards, with agentic QA that tests the product’s public claims against live services