Skip to content

Going to production

Work down the list before launch. Each line links the page that owns it.

  • Start sessions from your server with an sk_ key. Use a pk_ only on a public page, and never in a native app, which sends no Origin. Connect your app
  • List every production origin on each pk_, and only those. Keys and authentication
  • Know how you will rotate a key: mint, redeploy, then revoke the old one. Practise it once. Rotating a key
  • Grant members the narrowest role, and remember add_member grants access at once. MCP server
  • Serve an inbound wss:// route behind your TLS and load balancer, and set it as the agent’s brain_url. Use Cortex in production only for serverless or egress-only brains. Deploy the brain
  • Verify the brain-connection token, which run_session does by default. Never set allow_unverified=True outside local development. The brain-connection token
  • Pin exact versions of voqalize-agent-sdk on your server and @voqalize/client-transport in your page. Versions
  • Handle on_error, and log overload so you know when a queue is shedding frames. Error codes
  • Run the conformance suite in CI, plus your own scenarios, so a broken turn fails a build rather than a session. Test the brain
  • Decide record from the user’s consent, per session, on your server. Recordings
  • Send identifiers, not personal data, in init: it is stored on the session. Context and history
  • Check region and retention fit your obligations. Sessions are processed and stored in India today. Status and support
  • Download any recording you must keep before retention ends. Status and support
  • Plan for the one-hour session cap: a session ends with max_duration at the hour. Usage and limits
  • Know that a live call cannot be stopped from outside it. Archiving the agent or revoking its key refuses new sessions; calls already connected run until the caller or your brain ends them, or the hour cap does. To end one yourself, close the brain’s socket for that session.
  • Ask us about concurrency and minutes if launch traffic may exceed your plan. Usage and limits
  • Alert on the gap between sessions_created and sessions_started: a wide gap is a broken embed. Usage and limits
  • Read a sample of sessions back each week, the call record first, including never_spoken units and gaps. Reading a call back
  • Log the session_id on your side with configure_logging or your own loguru format, so both halves of a session join. Reading a call back