Regions
A region is a geographic location where Bahriya operates physical, virtual or hybrid clusters. Deploying your container to multiple regions runs it closer to your users, reduces latency, and provides redundancy.
A region is a geographic location where Bahriya operates physical, virtual or hybrid clusters. Deploying your container to multiple regions runs it closer to your users, reduces latency, and provides redundancy.
Available regions
| Region ID | Location |
|---|---|
helsinki-1 | Helsinki, Finland (Europe) |
falkenstein-1 | Falkenstein, Germany (Europe) |
virginia-1 | Virginia, USA (North America) |
singapore-1 | Singapore (Asia-Pacific) |
Choosing regions
When creating or editing a container, you select which regions it should run in. Your container runs independently in each selected region — each instance is isolated and serves traffic indepdently.
Single region
Running in a single region is the simplest setup. All traffic goes to one location. Good for:
- Development and staging environments
- Applications with users concentrated in one geography
- Cost-sensitive workloads
Multiple regions
Running in multiple regions means your application is available globally. Bahriya automatically:
- Deploys the container to each selected region
- Creates DNS records for each regional instance
- Routes traffic based on your chosen DNS mode (round-robin or geo)
Good for:
- Production applications with global users
- Applications where latency matters
- High availability (one region can go down without total outage)
How multi-region deployment works
When you add a region to a container, Bahriya:
- Creates a deployment in the new region
- Applies any required secrets and registry pull credentials to that region
- Provisions a TLS certificate for the container's hostname in that region
- Adds the region's IP to the DNS records
When you remove a region, the reverse happens — Bahriya deletes the container, removes DNS records, and cleans up all resources in that region.
Billing per region
Each region where your container runs is billed independently. A container running in 3 regions with 2 replicas each has 6 replicas billed globally. See How Billing Works for details.
Region classes
Regions are classified as standard or premium based on infrastructure cost. This affects pricing — premium regions have a higher per-millicore and per-GB rate. The region class is shown alongside each region in the console.
From the blog