Our own product, reservations platform · Built in-house
No fee per cover. Ever.
Our own reservations platform for independent restaurants: flat pricing from €19 a month, and the guest data stays with the restaurant. Invite-only since June 2026.
ReMesa is a reservations platform for independent restaurants, designed and built by Vonzie Studio in five weeks and held invite-only until it opens in stages.
A restaurant with 20 to 100 seats has two choices today: a platform that charges per seated guest and keeps the guest relationship for itself, or a paper book. ReMesa is the third: a flat monthly price from €19, no fee per cover on any plan, and every guest profile belonging to the restaurant that earned it. Work started on 4 March 2026. Five weeks later it was a complete product: a live availability engine, a booking widget, a floor plan, a guest CRM and billing across three plans. Since 25 June 2026 it sits behind an invite gate. Nobody is sold to yet, and each request for access is read by a person.
Specs
Product design, Full-stack build, Brand, Systems
Live availability, floor plan, guest CRM
Invite-only since 25 June 2026
Built March to April 2026, version 0.9.36
Context
The Problem
The reservation platforms an independent can afford were built to charge it, not to serve it.
Success gets taxed.
The dominant platforms charge per seated guest, so a full dining room pays more the better it does. A restaurant's busiest month should not be its most expensive one.
Someone else owns the guest.
The platform's loyalty programme rewards the platform, and the guest list feeds a company with interests beyond restaurants. The restaurant does the cooking; the platform keeps the relationship.
Contracts that trap.
Annual terms that renew themselves, narrow cancellation windows, and prices you have to phone for. Leaving costs more than staying, which is the point.
Built for the wrong size.
Enterprise suites want a training session before the first table is seated; budget tools gate reminders and the widget behind add-ons. Between the two, a 40-seat bistro finds nothing that fits.
Execution
What we built
Three rules shaped every screen: no fee per cover on any plan, the guest data belongs to the restaurant, and a host with thirty seconds between two tables must be able to use it.
Roadmap
Where it stands
A complete, billable product, held back on purpose until the first restaurants have shaped it.
Currently Optimizing
Complete, not launched
Accounts, three plans from €19 a month, a 14-day trial, an insights dashboard with 13 figures the manager reads. What is missing is customers, and that is by design.
Invite-only since June 2026
Public sign-up does not exist. A restaurant requests access, a person reads the request, and an invite goes out. The first restaurants get the maker on the other end of the email.
On the studio's own rails
ReMesa shares its accounts with the client portal we run for restaurant clients, so a Vonzie Studio membership can carry a reservations system inside it, managed by the studio.
The Backlog
What comes after opening
Bookings straight from Google, one guest base shared across locations, and an add-on that acts on the briefing instead of reading it out. Planned, not built.
"Restaurant technology should be infrastructure, not a toll booth. A restaurant's growth should never cost it more."
Vonzie Studio