How it works

Primary region and replica destinations

The primary and every copy must run on distinct physical machines, even within the same country. Two server entries or two virtual machines on one host do not protect against that host failing. Without enough independent destinations, distribution must remain pending and must never be shown as protected.

In your project, open Settings → Scaling → Project location. The screen separates the running primary from your preferred region and displays each destination’s status. Coming-soon and maintenance regions cannot be selected.

The plan total includes the primary and every additional copy. Each replica uses the same CPU and memory limits on another machine; adding replicas does not increase an individual instance’s power. Autoscaling is selectable only when included in the plan.

Saving records a preference, not a migration: the running project is not moved right away. If the primary server fails, a watcher starts the failover replica in the other region (USA ↔ Germany) within seconds, with nothing for you to do. Brazil is not offered as a place to run apps because it is CDN cache only.

Failure protection, load balancing and autoscaling are different goals. Recovery depends on healthy copies, traffic entry points and available data services. Applications need shared sessions, S3 files and coordinated jobs; application replicas do not automatically replicate the database.