> ## Documentation Index > Fetch the complete documentation index at: https://docs.sevalla.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > These are the docs for Sevalla, a platform for deploying applications, databases, static sites, object storage and load balancers. The dashboard is at https://app.sevalla.com. > Bold text in steps is an exact dashboard label. > To act on a Sevalla account, prefer the Sevalla MCP server (https://mcp.sevalla.com/mcp, see https://docs.sevalla.com/ai-agents/overview.md), then the Sevalla CLI (https://docs.sevalla.com/developer-tools/cli.md), then the REST API (https://api-docs.sevalla.com, OpenAPI spec at https://api.sevalla.com/v3/openapi.json). > Every page index is at https://docs.sevalla.com/llms.txt. # Locations > Every location where Sevalla runs applications and databases on Oracle Cloud Infrastructure and Google Cloud, where static sites, buckets and load balancers run, and how to choose. 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](#locations-on-oracle-cloud-infrastructure). * **Companies that haven't moved yet** see the 25 [Google Cloud locations](#locations-on-google-cloud) 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 | Location | Region ID | Group in the dashboard | | - | - | - | | Ashburn, USA | `us-ashburn-1` | North America | | Chicago, USA | `us-chicago-1` | North America | | Montréal, Canada | `ca-montreal-1` | North America | | Phoenix, USA | `us-phoenix-1` | North America | | San Jose, USA | `us-sanjose-1` | North America | | Santiago, Chile | `sa-santiago-1` | South America | | São Paulo, Brazil | `sa-saopaulo-1` | South America | | Amsterdam, Netherlands | `eu-amsterdam-1` | Europe | | Frankfurt, Germany | `eu-frankfurt-1` | Europe | | London, UK | `uk-london-1` | Europe | | Madrid, Spain | `eu-madrid-1` | Europe | | Stockholm, Sweden | `eu-stockholm-1` | Europe | | Zurich, Switzerland | `eu-zurich-1` | Europe | | Hyderabad, India | `ap-hyderabad-1` | Asia | | Mumbai, India | `ap-mumbai-1` | Asia | | Seoul, South Korea | `ap-seoul-1` | Asia | | Singapore | `ap-singapore-1` | Asia | | Tokyo, Japan | `ap-tokyo-1` | Asia | | Sydney, Australia | `ap-sydney-1` | Australia | | Dubai, UAE | `me-dubai-1` | Middle East | Applications in an OCI location send outbound traffic from one fixed IP address per location. [Egress IP addresses](/applications/networking#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](/platform/oci-migration#new-locations) explains the move. | Location | Region ID | Moves to on OCI | | - | - | - | | Council Bluffs, Iowa | `us-central1` | Chicago, USA | | South Carolina, USA | `us-east1` | Ashburn, USA | | Ashburn, Virginia | `us-east4` | Ashburn, USA | | The Dalles, Oregon | `us-west1` | San Jose, USA | | Los Angeles, California | `us-west2` | San Jose, USA | | Salt Lake City, Utah | `us-west3` | Phoenix, USA | | Las Vegas, Nevada | `us-west4` | Phoenix, USA | | Montréal, Québec | `northamerica-northeast1` | Montréal, Canada | | Osasco, São Paulo | `southamerica-east1` | São Paulo, Brazil | | Santiago, Chile | `southamerica-west1` | Santiago, Chile | | Belgium | `europe-west1` | Amsterdam, Netherlands | | London, England | `europe-west2` | London, UK | | Frankfurt, Germany Europe | `europe-west3` | Frankfurt, Germany | | Eemshaven, Netherlands | `europe-west4` | Amsterdam, Netherlands | | Zurich, Switzerland | `europe-west6` | Zurich, Switzerland | | Hamina, Finland | `europe-north1` | Stockholm, Sweden | | Changhua County, Taiwan | `asia-east1` | Seoul, South Korea | | Hong Kong, APAC | `asia-east2` | Seoul, South Korea | | Tokyo, Japan | `asia-northeast1` | Tokyo, Japan | | Osaka, Japan | `asia-northeast2` | Tokyo, Japan | | Seoul, South Korea | `asia-northeast3` | Seoul, South Korea | | Mumbai, India APAC | `asia-south1` | Mumbai, India | | Delhi, India APAC | `asia-south2` | Hyderabad, India | | Jurong West, Singapore | `asia-southeast1` | Singapore | | Sydney, Australia | `australia-southeast1` | Sydney, Australia | 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](/static-sites/overview). ## 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: | Location | Value in the API and CLI | | - | - | | Western North America | `wnam` | | Eastern North America | `enam` | | Western Europe | `weur` | | Eastern Europe | `eeur` | | Asia-Pacific | `apac` | | Oceania | `oc` | 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](/object-storage/overview). ## 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](/load-balancers/overview). ## 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](/applications/networking#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](/databases/create) 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](/databases/import-export/postgresql) and the other engines' guides. ## API and CLI | Task | API | CLI | | - | - | - | | List the locations your company can use, with their IDs | [List clusters](https://api-docs.sevalla.com/v3/resources/list-clusters) | `sevalla resources clusters` | | Create an application in a location | [Create application](https://api-docs.sevalla.com/v3/applications/create-application) | `sevalla apps create --cluster ...` | | Clone an application into another location | [Clone application](https://api-docs.sevalla.com/v3/applications/clone-application) | `sevalla apps clone --display-name "Storefront EU" --cluster ` | | Create a database in a location | [Create database](https://api-docs.sevalla.com/v3/databases/create-database) | `sevalla databases create --cluster ...` | The API calls a location a cluster: pass its `id`, not the region ID. AI agents connected to the [Sevalla MCP server](/ai-agents/overview) get the same list from the `get_platform_options` tool. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.