---
title: Regions
description: Where your services physically run, and how they're placed.
---

## Introduction

A **region** is where a service actually runs. Every serverlet, proxy, and DNS zone is placed in a region, and every region is backed by one or more [servers](/docs/servers/) — the physical or virtual machines running [Futrou Nasua](/docs/nasua/) underneath it.

Regions come in two kinds:

- **Public regions** — operated by Futrou, available to every workspace. This is what you're using unless you've joined your own hardware.
- **Private regions** — backed by your own [servers](/docs/servers/), visible only to your workspace. A private region is created automatically the first time you add a server; see [Servers](/docs/servers/) for joining one.

## Choosing a region

When creating a serverlet, you pick a region explicitly or leave it on **Auto** and let Futrou choose. See [Serverlet → Region](/docs/serverlet/#region) for the creation-time details.

Proxies and DNS zones don't have their own region picker — they're placed alongside the services they front. Keeping a project's serverlets, proxies, and DNS zones in the same region keeps the path between them short, since traffic doesn't have to leave the region to reach its backend.

## Viewing regions

Your workspace's available regions — the public regions Futrou operates, plus any private regions from servers you've joined — are listed at **Settings → Regions**, and shown as the region picker wherever a service is created. A region's page shows its servers and, for a private region, lets you manage them directly; see [Servers](/docs/servers/) for what that involves.

## Permissions

Viewing regions requires at least the **Viewer** role in the workspace. Creating a private region happens implicitly when [adding a server](/docs/servers/#adding-a-server), which requires **Administrator** or higher. See [Roles](/docs/members/) for what each role can do.