Multi-Tenant SaaS Platform
Guessto
Restaurant discovery and ordering platform. Every venue gets its own subdomain and menu off a single codebase, with QR ordering, Stripe payments and transactional email built in.
- Role
- Own product — architecture to production
- Status
- Live
- Live site
- guessto.com (opens in a new tab)
Problem
Independent restaurants want their own website, digital menu, ordering and card payments, but cannot pay for a bespoke build and a developer per venue.
Solution
A multi-tenant SaaS: every venue gets its own subdomain, menu, allergen and diet filters, QR-code ordering, Stripe payments and transactional email — all served from one codebase and one deployment.
Architecture
- Venue subdomain
- Tenant resolution
- Next.js app
- PostgreSQL (tenant-scoped)
- Stripe payments
- Transactional email
- Next.js
- TypeScript
- PostgreSQL
- Stripe
Result
Live and taking orders. MJ Carros Koblenz runs its full digital menu and direct ordering on the platform today, and new venues onboard without new code.
Why it matters to you
Proof that I can build a complete SaaS product — auth, billing, multi-tenancy and deployment — not only the AI layer. This is the foundation I reuse for AI MVPs.