> For the complete documentation index, see [llms.txt](https://docs.denvrdata.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.denvrdata.com/docs/platform/networking.md).

# Networking

## VPCs

A VPC (Virtual Private Cloud) is a private network for your instances. Every VM and application you deploy runs in a VPC and gets a private IP address from that VPC's subnet. Use separate VPCs to isolate environments such as production, testing and development.

{% hint style="info" %}
VPCs are local to a region (cluster) and don't span Denvr AI Cloud data center regions.
{% endhint %}

#### Default VPC

Each tenant gets a default VPC in every region, named after your tenant, so you can deploy instances right away without setting up networking first.

#### Traffic between instances

* **Standard VPC:** instances in the same VPC can reach each other on their private IP addresses. Instances in other VPCs can't.
* **Isolated VPC:** turn on **Block Intra VPC Comms** when you create the VPC, and instances in it can't reach one another, even inside the same VPC. Use this when each instance must stand alone.
* **Mesh-net VPC:** VMs and bare metal servers share one private network. Contact Support to set one up.

#### Storage and snapshots follow the VPC

Root disks, [block storage](https://docs.denvrdata.com/docs/platform/storage/block-storage) volumes and snapshots belong to the VPC they were created in. A volume can be attached only to VMs in its own VPC.

#### Create a VPC

**Access:** Administration → VPCs (creating and deleting requires the `TenantAdmin` role; all users can view VPCs)

1. Click **Create VPC**.
2. Select the cluster (region) where the VPC and its workloads will run.
3. Enter a name. VPC names start with your tenant name, so add something that identifies the VPC's purpose.
4. Check **Block Intra VPC Comms** if instances in this VPC must not reach each other.
5. Save. The VPC is ready for deployments.

<figure><img src="https://1008771031-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo84Tuz16JeqaVoFstgKj%2Fuploads%2FkqW1E5U1hCJKCb9cwn0L%2Fimage.png?alt=media&#x26;token=bcd2ae63-b229-452c-b0a0-a9c49fd1dc07" alt=""><figcaption></figcaption></figure>

Your tenant may have a limit on the number of VPCs. If you reach it, contact Support.

VPCs can also be managed through the [VPC API](https://docs.denvrdata.com/docs/api-reference/vpcs).

#### Delete a VPC

On the VPCs page, select **Delete** and type the VPC's name to confirm.

{% hint style="danger" %}
Deleting a VPC also deletes everything in it, including VMs and applications. This can't be undone.
{% endhint %}

#### Limitations

* **Instances can't move between VPCs.** Choose the right VPC when you deploy.
