Static-rendered, edge-served
Your homepage loads before a guest can second-guess.
The technical version
Astro 5 + Cloudflare. Pages are pre-rendered at build, served from the edge nearest the visitor. No origin round-trip on the hot path.
For the curious
Under the hood.
Most owners don't need to read this page. But if you (or your tech-savvy cousin) want to know why Mise is fast and durable, here's the honest answer.
A real database, not a JSON file
Your menu, hours, and content are structured — so changes are instant and consistent everywhere.
The technical version
Supabase (Postgres) with Row-Level Security per tenant. Schemas are migrated, typed, and queryable. Versioned via standard Postgres migrations.
Edit in 30 seconds, deploy in 30 seconds
You change a price, the world sees it before your espresso lands.
The technical version
Studio (admin SPA) writes through the Mise Engine API. Edits invalidate cache + trigger ISR rebuild on the impacted page. Median publish latency < 30s.
You own everything
Your domain, your data, your content. Want to leave? We hand you a CSV.
The technical version
Domain stays in your registrar. Full data export endpoint for menu + business + media. No proprietary lock-in formats.
Designed to outlast us
Built on stuff that'll be around in 10 years.
The technical version
Astro, Postgres, Cloudflare Workers, Stripe. All standards-leaning, all replaceable. No bespoke runtime, no “our framework only.”
Multi-tenant, single source of truth
You're not on a shared template — but you're also not maintaining a fork.
The technical version
Each restaurant is a tenant on a single Engine. Shared platform improvements ship to everyone. Tenant-specific features feature-flagged per row.
Ready when you are
Got more questions for the engineer?
Email us with anything — architecture diagrams, security posture, data export schema. We answer plainly.