Go to production

When you’re ready for real users, this checklist moves you from test to live cleanly.

The checklist

1. 1
   Switch to productionSelect the production environment for your workspace so you’re configuring the live surface.
2. 2
   Mint live keysCreate live publishable and secret keys, and replace any test keys in your site and tools.
3. 3
   Set allowed originsAdd your production domains to the allowed origins so the widget loads there.
4. 4
   Choose a planPick the plan that fits your expected audience, so you have the right MAEU allowance.
5. 5
   Turn on guardrailsSet spend caps and review rate limits so production usage stays predictable.
6. 6
   Verify end-user identity end to endIf the assistant acts for signed-in users, sign in as a real test user on your production domain and confirm the widget carries their identity: the conversation should show user-scoped results, and write actions should require the confirmation step. See End-user auth for the adapter and token options.

Your obligations to your users

Syncanix ships the AI disclosure, the audit trail, and EU data residency — but under GDPR and the EU AI Act, YOU are the deployer toward your own users. The who-handles-what matrix spells out who handles what: keep the AI disclosure visible (it cannot be disabled, by design), name Syncanix as a processor in your privacy notice, and make sure your own lawful basis covers the conversations your users will have.

Practical minimum before launch: update your privacy policy (processor + purposes), make sure what it says about conversation data matches the Syncanix privacy terms you signed up under, and decide how your users reach a human when they ask for one.

Rate limits and what your users see

Production traffic is rate-limited per tenant and per IP (and your plan carries message and action allowances with soft warnings before hard stops). When a user hits a limit, the widget shows a localized, retryable message in their language — it never shows a raw error.

Prepare your side of the conversation: decide what your support team says when users report the assistant asking them to wait, and watch the usage page during your first launch week so allowance warnings reach you before your users feel them.

How isolation stays proven after launch

Every layer of Syncanix is tenant-scoped, and that is continuously verified — a nightly probe matrix attempts cross-tenant reads, writes, log access, secret access, and retrieval queries against production, and every probe must pass before each deploy. The data protection page documents the model your security review can cite.

Next steps