VPSie home
Company

Cloud locations

VPSie Cloud runs in 12 locations. Choose where each server, volume, bucket and cluster lives, and keep its data there.

VPSie locationsDot-matrix world map with one pin for each of the 12 VPSie locations: New York 2, New York 3, New Jersey, Virginia, California, Montreal, Amsterdam, Nuremberg, Helsinki, Dubai, Amman, Djibouti. The arcs between sites are decorative.

12 locations, one console

VPSie Cloud runs in 12 locations. You pick the location for each server, volume, bucket or cluster, and your data stays there.

  • Choose the location per resource, not per account
  • The same console, API and Terraform provider in every location
  • Private networks connect your servers inside a location
  • Need your own site instead? See VPSie Private Cloud
VPSie locationsDot-matrix world map with one pin for each of the 12 VPSie locations: New York 2, New York 3, New Jersey, Virginia, California, Montreal, Amsterdam, Nuremberg, Helsinki, Dubai, Amman, Djibouti. The arcs between sites are decorative.CaliforniaMontrealNew York 2New York 3New JerseyVirginiaAmsterdamNurembergHelsinkiAmmanDubaiDjibouti

Named sites and what runs there

Services are not identical in every location. These are the sites the product documentation names today.

LocationService named in the documentation
CaliforniaManaged Kubernetes region
HelsinkiManaged Kubernetes region
Amman, JordanManaged Kubernetes region
MontrealManaged Kubernetes region
New York 2Managed Kubernetes region
VirginiaManaged Kubernetes region
New JerseyBare metal servers, available
New YorkBare metal servers, beta

The full list of 12, with the services in each, is shown in the console when you create a resource, and through the API with GET /datacenter.

Sites on the map: New York 2, New York 3, New Jersey, Virginia, California, Montreal, Amsterdam, Nuremberg, Helsinki, Dubai, Amman, Djibouti.

How to choose a location

Four questions decide it for most workloads.

Where are your users?

Put servers close to the people and systems that use them. Latency matters most for interactive apps, games, voice and databases.

Which law applies to the data?

If a rule says data must stay in a country or region, pick a location there and keep backups and replicas there too.

Which service do you need?

Bare metal, GPU and Kubernetes are not offered everywhere. Check the console list for the service before you plan.

Where is your recovery site?

For disaster recovery, choose a second location far enough away that one event cannot hit both.

Where are your users?Close to users and systemsWhich law applies?Inside the country or regionWhich service?Bare metal, GPU, Kubernetes varyWhere is recovery?A second, distant locationYour locationper resourceWhere are your users?Close to users and systemsWhich law applies?Inside the country or regionYour locationper resourceWhich service?Bare metal, GPU, Kubernetes varyWhere is recovery?A second, distant location
Four questions decide it for most workloads.
ServerVolumeBucketClusterLocation you choseData stays hereBackups tooLocked inMoves only if you move itServerLocation you choseVolumeData stays hereBucketBackups tooLocked inClusterMoves only if you move it

Keep data where you put it

Each resource lives in the location you chose. VPSie owns and develops the platform software, so there is no third-party cloud in the path.

  • Backups and snapshots are stored by location, so you control where copies live
  • Disaster recovery replicates to the second location you pick, see Disaster recovery
  • Audited against ISO 27001, SOC 2 Type II, SOC 3, CSA STAR, PCI DSS and SSAE 18, see Trust

When no location fits

Some workloads have to run in a country or a building we are not in yet.

VPSie Private Cloud

Run the same platform on your own hardware, in your facility, connected or air-gapped.

VPSie Cloud Enabler

Operators and data centers can run VPSie under their own brand and sell it locally.

Hybrid

Keep sensitive workloads on your site and burst or recover to a VPSie location, from one console.

Start in a location in a few minutes

The same steps work in every location.

Create an account

Sign up at my.vpsie.com. One account reaches every location.

Pick the location

When you create a server, volume, bucket or cluster, choose the location first. The console then shows the plans and prices offered there.

Deploy

Create the resource from the console, the API or Terraform. Private networks connect it to your other servers in the same location.

Protect it elsewhere

Set a backup policy, and for important systems add disaster recovery to a second location so one site event cannot stop you.

Questions about locations

How many locations does VPSie Cloud have?

12. The console lists each one with the services available there.

Can I move a server to another location later?

Yes. Plan the move like a migration: take a backup, create the server in the new location and switch when it is ready.

Are prices the same in every location?

The console shows the price of each option in the location you pick before you create anything. See Pricing.

Where can I see the status of each location?

On the service status page.

Can I get a location in my country?

Talk to an expert about VPSie Private Cloud or a Cloud Enabler partner in your market.

Can one account use several locations?

Yes. One account and one API token reach every location, and each resource keeps the location you chose for it.

Not sure which location fits?

Tell us where your users are and which rules apply. We will suggest a location or a private site.