Regions
A region is where an environment’s workloads run: its deployments, and the databases linked to them. You choose the region for each environment when you create it, so one organization can run some apps in the United States and others in South Africa, on different clouds.
Available regions
Salus Cloud offers two regions today:
| Region, as the console names it | Cloud provider | Location |
|---|---|---|
| United States (South Carolina) · GCP | Google Cloud, us-east1 |
South Carolina, USA |
| South Africa (Capetown) · AWS | Amazon Web Services, af-south-1 |
Cape Town, South Africa |
Both run the same platform: the same pipelines, buildpacks and Docker builds, managed PostgreSQL databases, logs and metrics. The Salus MCP server works with both, so an agent can deploy to either.
Choose a region for an environment
- An organization admin enables the regions builders may use, and sets the default, on the organization’s Regions page. See Organizations & Teams.
- When anyone creates an environment, they pick its region from the enabled set; the default is pre-selected. See Configure an Environment.
- Every project that deploys to that environment runs in its region.
A region can’t be changed after the environment is created, so pick it deliberately. To run the same app in both regions, give it an environment in each.
Databases follow the region
A database is created in a region and can only be linked to environments in the same region. Put the database where the app that reads it runs; a database across an ocean adds latency to every query. See Connect a Database.
Which region to pick
- Where your users are. Requests travel to the region and back. An internal tool for staff in Johannesburg responds faster from Cape Town; one for staff in New York, from South Carolina.
- Where the data has to stay. If a policy or a regulator requires data to stay in a country, run the app and its database in an environment in that country’s region. Whether that satisfies the rule is a question for your compliance team; the region decides where the workloads and the database run.
- Where the rest of your systems are. An app that calls other services is quicker next to them.
Moving an app to another region
Create an environment in the other region, add a release configuration for the project there, and deploy. A coding agent connected through the Salus MCP server can do this for you. A database doesn’t move with the app: create one in the new region, link it, and migrate the data yourself.
Your own cloud
On the Enterprise plan, Salus can also run in infrastructure your company owns, in the region you choose. See BYOC.