Kurrens runs inference in three regions on two continents. Every region runs the same models at the same declared precision, so a request that fails over to another region gets the same model and the same output format.
Johor
Malaysia · Asia Pacific · 3 availability zones
Primary region. Serves all serverless models by default.
Jakarta
Indonesia · Asia Pacific · 3 availability zones
Second Asia Pacific region. Takes traffic when Johor is at capacity or degraded.
Dublin
Ireland · Europe
European region for dedicated deployments, and a failover region for Asia Pacific.
How requests are routed
Serverless. Requests are served from Johor by default. If Johor is at capacity or degraded, the request is served
from Jakarta; if both Asia Pacific regions are unavailable, from Dublin. You don’t need to change anything in
your client — the base URL stays https://api.kurrens.ai/v1.
Dedicated endpoints. A dedicated endpoint is pinned to the region you choose — Johor, Jakarta, or Dublin — and never leaves it. Use this when you need data residency in a specific country, or low latency from Europe. See Dedicated endpoints.
Where your data is processed
| Johor, Malaysia | Jakarta, Indonesia | Dublin, Ireland | |
|---|---|---|---|
| Prompts and completions | In memory, never stored | In memory, never stored | In memory, never stored |
| Serves serverless traffic | Default | Failover | Failover |
| Dedicated endpoints | Available | Available | Available |
Prompts and completions are processed in memory in the region that serves the request and are discarded when the response completes — in every region. Request metadata (token counts, latency, status code) is kept for billing, as described in Zero data retention.
Region ids
The region ids above are published per model in our catalog at
kurrens.ai/models.json (datacenters), which is the file OpenRouter reads.
"datacenters": [
{ "country_code": "MY", "region": "ap-southeast-1" },
{ "country_code": "ID", "region": "ap-southeast-3" },
{ "country_code": "IE", "region": "eu-west-1" }
]The binding statement of where we process data is in our Data Policy and Privacy Policy.