Documentation › Configure

Regions and moving a project

Where your project runs, and how to move it to another region: downtime, new addresses, DNS and price.

Where a project runs

Each project runs on a server in one region, for example Europe or the UAE. The region is picked when you buy a plan or create the project, and it decides where your databases, files and backups are stored, the project's addresses ( <project>.cloud.knovadigital.com or the region's own domain) and the price. Settings → Move project shows the current region.

Moving a project to another region

A project admin can move the whole project (production, staging, backups and custom domains) from Settings → Move project . Nothing changes before you confirm.

Pick the region Choose where to go, when to start (now, or a quiet hour later) and what to do with the old backups: move them along, or delete them with the rest of the old data.

Review The wizard measures the project and shows how long the move takes, how long production is down, the new price, the new addresses and the DNS records your custom domains will need.

Confirm Type the project's name to start or schedule the move.

Follow it Each step shows up as it runs, with the log. Until production is switched over, Cancel move stops everything and the project stays where it was.

What changes

Downtime. Production keeps running while most of the data is copied, and is stopped only for the final copy: usually a few minutes, estimated before you confirm. A first copy is made beforehand; in that window a small project is copied again in full, a larger one only has its database and the files added since the first copy copied.

Addresses. The default addresses move to the new region's domain. The old ones keep working for 30 days: they redirect to the new addresses.

Custom domains. They need a DNS change: the record to create (a CNAME, or an A record for a bare domain) is shown in the wizard and on the move once it is done. Until you change it, the old server forwards visitors for 30 days. HTTPS is issued automatically once the record points to the new server.

Price. Prices depend on the region. Your subscription is updated when the move is done, with proration by Stripe: the difference for the rest of the current period is on the next invoice.

Staging and development. Staging branches are rebuilt on the new server from a fresh copy of production. Development branches are not copied: each one rebuilds on its next push, or with Rebuild .

Tools. Open notebooks and shells are closed when production switches to the new server.

The data left on the old server

The old copy of the project (its databases, files and, unless you chose to move them, the old backups) is kept for 7 days after the move in case anything is missing, then deleted for good. To have it deleted right away, for example so your data only stays in the new region, use Delete source data now on the finished move.

Before you move Pick a quiet hour with Start at , lower the TTL of your custom domains' DNS records a day ahead so the change spreads quickly, and tell your users about the short interruption.