Multi-region Deployment
Supported regions
| Code | Region | Phase |
|---|---|---|
| KR | Korea | GA |
| JP | Japan | Beta |
| SG | Singapore | GA |
| ID | Indonesia | Beta |
Tenant residency
Each tenant is assigned a home region at provisioning time. Data at rest (D1 database, KV) is stored in that region’s Cloudflare data centre.
Requests are routed to the nearest edge PoP for compute, but sensitive data never leaves the home region.
Configuring residency (Control Plane)
curl -X POST $CONTROL_PLANE_URL/v1/tenants \ -H "Authorization: Bearer $ADMIN_KEY" \ -d '{"slug": "acme-kr", "region": "KR", "plan": "pro", "adminEmail": "admin@acme.kr"}'Geo-routing
Requests from outside the home region are proxied through the Cloudflare global network with a single hop. Latency budget: <100ms intra-region, <200ms cross-region.