Regions
Every deployment on Ownkube Compute runs in one region, chosen when you create it. Pick the one closest to your users, or the one your data needs to stay in.
| Region | Shown in the app as | Outbound bandwidth |
|---|---|---|
| Mumbai | Asia (Mumbai) | $0.13 per GB |
| Germany | Europe (Germany) | $0.02 per GB |
Compute, database and cache prices are the same in both regions. Only bandwidth differs. Inbound traffic and traffic between deployments in the same region are free. See Plans and pricing.
Choosing a region
Section titled “Choosing a region”- Latency. Put the app where its users are. A European audience on the Germany region sees a fraction of the round-trip it would see on Mumbai.
- Data residency. Data in a region stays in that region. For GDPR scope, Germany keeps data in the EU.
- Keep an app and its data together. A web app and the database it links to should be in the same region. Cross-region traffic counts as outbound bandwidth and adds latency to every query.
What a region contains
Section titled “What a region contains”A region is a failure and networking boundary. Deployments in the same region reach each other over private networking by name. Public hostnames resolve to the region the app runs in. A region cannot be changed after creation; to move, create the deployment in the other region, link the new database, and switch the subdomain. See Public hostnames and TLS.
From the terminal
Section titled “From the terminal”okctl regions listLists the regions you can deploy to, with their identifiers for okctl deploy create manifests.