Sandbox and production
On this page
Cloudgate uses sandbox for development and production for released APIs. The environment selects workflow and resource configuration, but each integration still needs a deliberate isolation plan.
Understand what changes#
| Area | What to check |
|---|---|
| API route | /sbx/ for sandbox; /prod/ for production |
| Workflow | Sandbox can use the editable draft; production uses the released workflow |
| Key Selectors | Separate sandbox and production values |
| Database node | Its selected environment-specific database binding |
| API access | The credentials, permissions, and limits for that environment |
| CORS | Independent enabled state, origins, and credentials setting |
| Schedules and logs | The environment selected for the job or recorded request |
Configure test resources#
Use a test database and a provider's test credentials when exercising writes. Verify the actual upstream hostname and selected database, not only the /sbx/ prefix on your Cloudgate URL.
App-user identities are shared within the tenant. An IdP Users update executed in sandbox can change a real app account. Use dedicated fixture accounts for identity tests.
Shared SMTP settings and other tenant-wide services can also affect multiple apps. An environment name is not a promise that an email, payment, or external write is simulated.
Compare before releasing#
- Check the draft against the intended production version.
- Confirm production selectors and resource bindings are populated.
- Confirm the public production URL and client authentication.
- Review browser origins, schedules, and dependent apps.
- Release through the review process and run a controlled production check.
Diagnose environment mismatches#
A workflow working internally but returning 404 publicly may have the wrong route, method, or release state. A request reaching the wrong service usually points to a selector or database binding. An empty dashboard may simply be filtered to the other environment.
Use testing and release review to verify the complete path.
Need to investigate a problem? Start with troubleshooting