Regions
DockHive runs in eight regions. Choose a region close to your users: requests travel a shorter distance, so your app feels faster.
| Region | Location |
|---|---|
us |
United States (Los Angeles) |
eu |
Europe (London) |
de |
Germany (Frankfurt) |
asia |
Asia (Singapore) |
africa |
South Africa (Johannesburg) |
ng |
Nigeria (Lagos) |
abuja |
Nigeria (Abuja) |
pt |
Portugal (Lisbon) |
Apps, databases, n8n workspaces, HivePods and tunnels are available in every region. Hive Buckets has a global S3 endpoint plus regional ones; see Endpoints and regions.
Picking a region
Section titled “Picking a region”- Console: apps and databases have a Deployment Region menu, n8n has a Region menu, and HivePods have Choose Datacenter Region cards. Each region shows its status: Healthy, Degraded or Unavailable.
- CLI:
hivepod create --region eufor pods.hivepod deploykeeps the region of the app it redeploys. - Tunnel:
dockhive expose 3000 --region eu, or leave the defaultautoto use the fastest region from where you are. See Names and regions. - API: send
X-Region: euor?region=eu. See Using the API.
A resource stays in the region where you created it.
Addresses work everywhere
Section titled “Addresses work everywhere”Your app’s address (<name>.dockhive.app) works the same wherever the app runs; you don’t need a regional hostname.
Plan limits are global
Section titled “Plan limits are global”Your plan’s limits (for example, the number of apps or HivePods) count everything you run across all regions combined. See Plans.
Check region status
Section titled “Check region status”The public endpoint below lists the regions and their health:
curl https://api.dockhive.io/api/v1/regions