OpenDot includes a rootDocumentation Index
Fetch the complete documentation index at: https://docs.opendot.ai/llms.txt
Use this file to discover all available pages before exploring further.
render.yaml Blueprint for a Render preview deployment.
It creates:
opendot-web: static Vite console.opendot-api: Docker web service for the platform API.opendot-runtime: Docker web service for realtime voice sessions.
Database
Use Supabase Postgres for the first Render deployment:app_users, user preferences, SDK API keys,
agents, pipelines, devices, device activation requests, device credentials,
runtime session tokens, device state, and deployments. Supabase Auth owns sign-in
without making auth.users the product data table.
Required Render values
The Blueprint marks secrets and deployment-specific URLs assync: false. Fill
them in the Render dashboard during Blueprint creation:
SUPABASE_JWT_SECRET empty unless the Supabase project still uses legacy
HS256 JWT signing.
Auth posture
The Render Blueprint uses:Runtime exposure
The runtime verifies browser voice-session tokens and device credentials with the platform API before accepting/voice or /ws connections. Use the same
OPENDOT_RUNTIME_INTERNAL_SECRET on opendot-api and opendot-runtime.
For public previews, keep provider-key quotas tight and point
OPENDOT_RUNTIME_PUBLIC_HTTP_URL / OPENDOT_RUNTIME_PUBLIC_WS_URL at the
deployed runtime URL.