Regions
One region per organization: which origin to call for each product, and what happens when a credential reaches the wrong one.
An organization is pinned to one region by its jurisdiction, and a credential carries that region in its prefix (csk_live_eu_). Ciresk runs in the EU only today.
| Region | Ciresk CI origin |
|---|---|
EU (eu-central-1) | https://ci.eu.ciresk.com |
| US | Not available yet |
Ciresk CI's MCP endpoint is on the same origin, https://ci.eu.ciresk.com/v1/ci/mcp. The Platform API answers at https://api.ciresk.com.
The wrong region
A credential sent to another region's origin is refused with 421 wrong_region before any query; the problem names the right one. The ciresk ci CLI retries once against it on its own; ciresk dev does not and exits 3, so pass --region <region> or set CIRESK_REGION; a script should send the request there. Everything with content (source deltas, logs, artifacts, caches, test results) stays in the organization's cell; only identity, organization placement and API key records are shared across regions. See Data residency.