Skip to content

Regions

DockHive runs in fourteen 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)
virginia United States (Virginia)
eu Europe (London)
de Germany (Frankfurt)
global-1 Global (Frankfurt)
asia Singapore (Asia)
singapore Singapore
hongkong Hong Kong
tokyo Japan (Tokyo)
mumbai India (Mumbai)
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 (not yet in global-1, singapore, tokyo or hongkong); see Endpoints and regions.

Hive Push is available in global-1, us, de, pt, singapore, tokyo and hongkong; see Limits and regions.

  • 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 eu for pods. hivepod deploy keeps the region of the app it redeploys.
  • Tunnel: dockhive expose 3000 --region eu, or leave the default auto to use the fastest region from where you are. See Names and regions.
  • API: send X-Region: eu or ?region=eu. See Using the API.

A resource stays in the region where you created it.

Your app’s address (<name>.dockhive.app) works the same wherever the app runs; you don’t need a regional hostname.

Your plan’s limits (for example, the number of apps or HivePods) count everything you run across all regions combined. See Plans.

The public endpoint below lists the regions and their health:

Terminal window
curl https://api.dockhive.io/api/v1/regions