Multi-tenant SaaS · voice ordering
CleonAI Voice Ordering Platform
I built a restaurant and voice-agent administration platform with tenant-scoped backend operations, ordering tools, and provider integration foundations. The case study separates the implemented configuration and domain work from unverified live-order outcomes.
Actual integrations screen from the public Loom walkthrough at about 00:17. Provider tiles show configuration UI, not verified operation for every provider.
01 / Snapshot
At a glance
- Built
- Restaurant, agent, and integration management with voice-ordering foundations
- Problem
- Keep conversations, menus, carts, and provider state scoped to a restaurant
- Ownership
- Full-stack product engineering across dashboard, API, data, and integrations
- Delivery
- Working admin and integration foundation; live customer orders not evidenced
02 / Context
The engineering problem
A phone-ordering assistant has to turn conversational input into a deterministic menu and cart state. A wrong restaurant or tenant context would make even a fluent conversation unsafe for ordering.
External voice and ordering providers add configuration and failure boundaries. The public walkthrough shows the integrations management surface, but it does not prove every listed connection processed real orders.
03 / System
System architecture
Restaurant-scoped ordering path
A logical map based on the owner's project notes and visible integration UI. The diagram does not claim a particular deployment topology or that every provider tile is operational.
Tenant-scoped FastAPI domain
Validates tenant → restaurant → agent context for business operations
- Next.js adminRestaurant, agent, and integration configuration
- Voice layerVapi agent with Deepgram STT and ElevenLabs TTS in project notes
- Ordering toolsMenu ingestion, cart state, and checkout workflow
- PostgreSQL modelsTenants, restaurants, agents, orders; SQLAlchemy + Alembic
- OrderOut foundationMerchant/menu identifiers and create-order groundwork
Provider relationships and backend details are owner-described; the screenshot confirms the integration configuration UI. OrderOut remains an integration foundation.
04 / Judgment
Engineering choices & trade-offs
Scope operations by tenant and restaurant
- Problem
- Shared SaaS APIs must not cross restaurant data boundaries.
- Implementation
- The project notes describe tenant → restaurant → agent mapping and scoped backend request validation.
- Implication / limit
- The API needs context checks at each business operation; a screenshot cannot verify isolation tests or production enforcement.
Owner project record
Keep ordering state deterministic
- Problem
- A conversation may be flexible, but menu selection, cart state, and checkout need explicit transitions.
- Implementation
- The recorded implementation uses voice tools for menu ingestion, cart management, and checkout rather than treating chat text as the order record.
- Implication / limit
- Business state can be validated independently of a voice response; the record does not establish live-order volume or completion rates.
Owner project record
Keep provider boundaries replaceable
- Problem
- Voice and merchant services have separate credentials, data shapes, and failure modes.
- Implementation
- The project record describes provider-agnostic domain boundaries and an integration management UI; the walkthrough shows provider tiles and statuses.
- Implication / limit
- This supports future swaps, but a visible tile is not evidence that every provider is fully integrated. OrderOut is a foundation.
Owner project record; public Loom integration view
05 / Execution
Hard problems, concrete responses
Context during a live conversation
The assistant needs the correct restaurant menu and cart while interacting with a voice service.
Response. The described backend maps each voice agent to a restaurant and scopes tool calls to that context.
External API uncertainty
Provider calls can time out or return partial data while an ordering flow is in progress.
Response. The project notes describe fallbacks and integration boundaries; no specific uptime, retry guarantee, or incident result is claimed.
06 / Status
Delivery & outcome
Admin and domain foundation
Restaurant, agent, and integration management, tenant-scoped FastAPI operations, and PostgreSQL domain models are documented in the project record. The walkthrough shows the integrations UI.
OrderOut and provider expansion
OrderOut merchant/menu configuration and create-quote/create-order groundwork are described as a foundation. The visible provider tiles are configuration surfaces, not proof of full production operation.
Live commercial ordering
No verified customer order volume, revenue, or production processing outcome is presented.
07 / Proof
Real product evidence
The screenshot is an authentic walkthrough frame of the integrations page. The public Loom video remains linked; architecture details beyond the visible UI are identified as owner-provided project facts.
Product captures
Actual interfaces, reference demonstrations, and their source details.
08 / Stack
Technology by responsibility
- Admin application
- Next.js · TypeScript
- API and data
- FastAPI · PostgreSQL · SQLAlchemy · Alembic
- Voice and providers
- Vapi · Deepgram · ElevenLabs · OrderOut foundation