Environments
Neuroon exposes two public environments: Production and Development. They are separate clusters, with different databases and API keys that are not interchangeable.
Comparison
| Production | Development | |
|---|---|---|
| API | https://api.neuroon.ai | https://dev-api.neuroon.ai |
| Dashboard | https://neuroon.ai/dashboard | https://dev.neuroon.ai |
| Public web | https://neuroon.ai | https://neuroon.ai |
| Widget CDN | https://cdn.neuroon.ai | https://cdn.neuroon.ai (same CDN) |
| Status | https://status.neuroon.ai | https://status.neuroon.ai (same) |
| Data persistence | Permanent | Not guaranteed |
| Stability | High | Variable (continuous deploy) |
| Access | Public (with account) | On request — contact support |
The widget CDN is the same across environments. The difference between Production and Development is set via data-api-url on the <script> tag and the corresponding Shop API Key.
When to use each
Production
- Your integration is complete and you have validated the flow in Development.
- You want real traffic, real conversions, real metrics.
- Production keys are generated from
neuroon.ai/dashboard.
Development
- You are testing a new Recipe.
- You need to iterate sync payloads without polluting your Production catalog.
- You want to see error responses and edge cases without risk.
- The "Try It" playground in the documentation points to Development by default.
Switching environments in your integration
All switching boils down to two things:
- The base URL you use in each HTTP client.
- The API Key and, if applicable, the Widget Token for the corresponding environment.
See Switching environments for stack-by-stack examples (tu stack).
Further reading
- Production — URLs, real SLA, obtaining keys.
- Development — access requests, limitations.
- Switching environments — recipes per stack.