---
description: Creating a private network and its subnets
revision_date: 20.10.2026
---

# Create a private network

!!! warning "Draft — pilot feature"
    Private Networks is in a limited pilot and this page is a work in progress.

You can create a network ahead of time from the console, or create a subnet
inline while deploying your first instance.

## Create a network

In the console sidebar, under **Networking**, open **Private networks**. The
page lists your project's networks, the subnets in each one, and their IDs. The
project's default network is marked **Default**. Create new networks from this
page.

## Create a subnet

In the deploy form's **Network** step, next to the **Subnet** dropdown, choose
**Create new**.

| Field | Notes |
|-------|-------|
| **Private network** | Which network the subnet belongs to. Pre-filled with your project's default network. |
| **Subnet location** | Which datacenter location the subnet belongs to. |
| **Subnet name** | Free-form label, up to 64 characters. Unique inside the network. |
| **IP range (CIDR)** | The IPv4 block private addresses are allocated from, e.g. `10.0.0.0/24`. |
| **Enable internet gateway** | *Coming soon.* See [Internet access](https://docs.verda.com/private-networks/internet-access/) for what works today. |

The subnet is created in the datacenter location you are deploying into. Each subnet
belongs to exactly one location and cannot be moved.

### Choosing an IP range

- IPv4 only. IPv6 is not supported.
- Must be written in CIDR notation, e.g. `10.0.0.0/24`, not
  `10.0.0.5/24`.
- The prefix must be `/30` or shorter, a `/31` or `/32` has no usable host
  addresses.
- Use a private range (RFC 1918): `10.0.0.0/8`, `172.16.0.0/12`, or
  `192.168.0.0/16`.
- The first and last addresses of the block (network and broadcast) are not
  handed out.

## The first subnet becomes the default

The first subnet you create in a network automatically becomes its **default subnet**. Deployments use the default subnet when you specify a network but not a subnet. Subnets you create later don’t become the default unless you change the default yourself.

## Deleting

An instance cannot be detached from its network or moved to another subnet:
networking is fixed when the instance is deployed (see
[Deploy an instance](https://docs.verda.com/private-networks/deploy-an-instance/)).

A subnet cannot be deleted while any instance still holds an address in it, and
a network cannot be deleted while any instance is still on it. Delete those
instances first.

Deleting a network also removes its subnets and routes.