Regions

During the beta, Fjordrun runs in one region:

Region	Location	Provider
nbg1	Nuremberg, Germany	Hetzner Online GmbH

All services, databases, volumes, builds and logs of your team are stored and processed there. See Security model and Privacy and GDPR.

Where your services run

Every project has a region, chosen when you create it. All services of the project run on servers in that region: web services, workers, cron jobs, databases and agents. Their volumes are created there too.

Image builds are not tied to a region. They run on Fjordrun's build servers, and the image is then deployed to the project's region.

First deploy in a new region

Fjordrun adds servers to a region when it needs them. If no server in your project's region has room for a service, the deploy starts one and waits for it. The deploy log shows it, for example:

No server in Helsinki (hel1) yet: starting one (cax21), this takes 2-4 minutes

The deploy then continues as usual. Later deploys in the same region use the servers already there.

If no server can be added in the region at that moment, the deploy fails with a message that says so. Try again later, or contact support.

Changing a project's region

You can change the region in the project settings, or with PATCH /api/v1/projects/{id} and {"region": "..."}. Services move to the new region on their next deploy.

Volumes stay in the region they were created in, so a project that has volumes can't change its region (the API answers 409 Conflict). Remove the volumes first, or create a new project in the other region and move your data.