Traveo
SaaS · travel · built by Aziz Khan
The problem
Tour operators run bookings across spreadsheets and chat.
What I built
Multi-tenant operating system for travel agencies, one codebase for desktop and web, with type-safe APIs and a Postgres-backed job queue.
Engineering decisions
- Tenancy is enforced in Postgres with row-level security, so a forgotten WHERE returns nothing instead of leaking data from another agency.
- Money is numeric(19,4) in the database and a decimal string on the wire. It never touches a float, and every amount carries its currency.
- The ledger is append-only, enforced by Postgres rules. Corrections are reversing entries and balances are derived, never stored.
Stack
- Bun
- Hono
- tRPC
- Drizzle
- React
- Tauri
Written up in detail
- How to Take an AI-Built App from Prototype to Production
A working checklist for apps built with AI coding tools: secrets, data access, config, payments, background work, deploys and monitoring.
- Two rules you can't fix later in a multi-tenant SaaS
Enforce tenancy in Postgres, not the app, and never let money touch a float. Lessons from building Traveo.
More case studies
Have an AI product to ship?
Tell me what needs to be built, fixed, integrated or deployed. You work with me directly, the engineer who reads the code and ships it.