Environments and base URLs
Assayra supports shared SaaS, dedicated region, customer cloud and private deployment. The API and workflow semantics remain consistent; origin, residency and operations change.
| Environment | Evidence | Access | Purpose |
|---|---|---|---|
| Local/showcase | Fictional fixtures only | Internal demonstration | Demonstration and integration development |
| Sandbox | Fictional/test evidence | 50 checks in every free workspace | Customer QA and workflow validation |
| Bounded Live | Real evidence | Up to 10 approved checks; no card required | Validate the real capture and engine path |
| Paid Live SaaS | Approved real coverage | Build or Scale subscription | Ongoing live tenant operations |
| Dedicated/BYOC/private | Customer deployment contract | Enterprise agreement | Residency, isolation or sovereign requirements |
Set base URLs through deployment configuration. Do not derive a production hostname from the tenant name and never fall back from HTTPS to HTTP outside an explicitly enabled loopback sandbox.
The tenant administrator changes the active environment from the environment control in Client Admin Portal. Existing applications never move when the active environment changes. Applications, API keys, evidence, usage and references remain bound to the environment where they were created.
Use pl_sandbox_… keys for Sandbox and pl_live_… keys for Live. Webhook endpoints are environment-bound too: Sandbox events are never queued to a Live endpoint or vice versa. Never copy real evidence into showcase or Sandbox environments. Live can be selected only after independent activation confirms the workspace controls, enabled capabilities, deployable Country Assurance Pack and data route. When the approved complimentary allowance is complete, Sandbox stays available and further Live application creation returns 402 live_trial_exhausted until a package is active.
Service separation
The customer tenant origin serves commercial pages, registration, Client Admin Portal, tenant API, applicant sessions and documentation. Assayra Control Tower uses a different origin/session and excludes tenant/applicant API routes. Customers never integrate against Control Tower.