Production proof layer

The promise has an operating system behind it.

This page is built for sales calls, launch review, and operator trust. It shows the live architecture, repeatable QA commands, build identity, and the exact safeguards that turn a demo into a production system.

Current build identity

Commitunknown

Refunknown

Deploymentdpl_DhH2TGNCsg2HEizJZCyMz7YnTPxy

Generated2026-08-13T04:21:24.822Z

Voice bridge

voice-bridge-production-fb2c.up.railway.app

Browser demo and Twilio streams resolve through the production bridge host.

Stream signing

hmac

Browser voice sessions receive short-lived signed stream tokens.

Twilio path

Credentials present

Inbound TwiML can sign handoff parameters for the voice bridge.

Ops alerting

Delivery armed

Failures can leave the app through webhook or email delivery.

Real usage, last 7 days

Live from production DB

Pulled straight from the orders table on every load. Landing-page browser demo calls and internal QA drills are excluded — this is real restaurant traffic only.

No live calls yet

This updates the moment the first real call lands.

Voice to paid order timeline

Traceable

01Guest callsTwilio receives the restaurant phone call and connects a bidirectional audio stream.

02AI answersThe voice bridge authenticates the stream and opens the live AI session.

03Order capturedTranscript, order details, totals, and confidence signals are persisted.

04Kitchen sees itThe dashboard updates through the same order and event surfaces operators use daily.

05Payment closesSMS checkout and Stripe webhooks update payment status back onto the order.