Skip to main content
A location is where an application or a database runs: one Kubernetes cluster in one cloud region, such as Frankfurt, Germany. You choose it when you create the service, in the Data center field, and you can’t change it afterwards. Static sites and load balancers have no location; buckets have a location hint.

​
Which locations you see

Each company runs its applications and databases on one cloud, Oracle Cloud Infrastructure (OCI) or Google Cloud, and sees only that cloud’s locations:
  • New companies, and companies that have moved to OCI, see the 20 OCI locations.
  • Companies that haven’t moved yet see the 25 Google Cloud locations until their migration. Each of these locations moves to an OCI location.
Applications and databases use the same list. The Data center field preselects a location on your continent, based on your browser’s time zone, and lists the others grouped by continent, with Recently used at the top once you’ve used more than one. Each entry shows the location’s name and its region ID.

​
Locations on Oracle Cloud Infrastructure

Applications in an OCI location send outbound traffic from one fixed IP address per location. Egress IP addresses lists them.

​
Locations on Google Cloud

These are the locations of companies that haven’t moved to OCI yet, with the OCI location each one moves to. Migration to Oracle Cloud Infrastructure explains the move. Madrid, Spain and Dubai, UAE are new locations with no Google Cloud counterpart.

​
Static sites

A static site has no location. Sevalla builds it in Oracle Cloud’s US East (Ashburn) data center for every company, stores the files in Cloudflare R2, and serves them from Cloudflare’s edge network, close to each visitor. See Static sites.

​
Object storage

Each bucket is a Cloudflare R2 bucket. When you create it, you pick a location that says where most of its traffic will come from, and you can’t change it later. It isn’t a data residency guarantee: The dashboard preselects Western Europe when your browser’s time zone is in Europe and Western North America otherwise. The API and CLI use enam when you don’t set one. Public files are served through Cloudflare’s edge, whatever the bucket’s location. See Object storage.

​
Load balancers

A load balancer has no location: it runs on Cloudflare’s edge network, and each of its destinations keeps its own location. With Geo routing, it sends each visitor to the closest destination. See Load balancers.

​
Choose a location

  • Put the service close to its users. Latency grows with distance, so pick the location nearest to where most requests come from. Your analytics tool’s visitor countries, or the Analytics tab of an existing Sevalla service, show where traffic comes from.
  • Keep an application and its databases together. Internal connections only work between services in the same location, and they’re faster than going over the internet.
  • Check the database versions. The engine versions you can pick depend on the location’s cloud. Create a database lists them.
  • Plan for the location to be permanent. To run an application somewhere else, clone it into the new location with the API or CLI, then move your domains. A database can’t be moved: create a new one in the new location and copy the data, as described in Import and export PostgreSQL and the other engines’ guides.

​
API and CLI

The API calls a location a cluster: pass its id, not the region ID. AI agents connected to the Sevalla MCP server get the same list from the get_platform_options tool.