Data Residency & Regional Boundaries
For enterprise and regulated sectors with strict compliance mandates, regional isolation and on-premises deployments follow the specification's dual-region architecture. Exact server endpoints, SLAs, and commercial boundaries are formalized through contractual agreements.
1. Regional Architecture
| Region Tag | Base URL | Architectural Scope |
|---|---|---|
| cn-mainland (contract reserved) | https://api.sequenxai.com/cn/v1 | OpenAPI regional path; not edge-routed yet. |
| Current live endpoint | https://api.sequenxai.com/v1 | Live now, with sqx_live_* keys created self-service on the SequenxAI Platform; mainland traffic also uses this path for now. |
Use /v1 until regional routing ships. The X-SequenX-Region request header is not read today.
2. On-Premises Boundaries
Planned delivery forms are Docker and Helm, evaluated per project, with the same wire format as the cloud OpenAPI. There are no public offline images or Helm charts today (see On-Premises). Authentication, quotas, offline operations and accelerator support are validated during enterprise engagements.