# VPC on Quake AI

Source: https://docs.quake.ai/docs/network/concepts/vpc
Markdown: https://docs.quake.ai/docs/network/concepts/vpc.md

---

# VPC on Quake AI

Quake AI does not expose a single object named **VPC** or **virtual private cloud**. The same job is done with **[networks](/docs/network/concepts/networks)** (including **subnets** as IP ranges inside a network), **[routers](/docs/network/concepts/routers)** (routing and NAT between segments), and **[floating IPs](/docs/network/concepts/floating-ips)** (stable public addresses on private instances).

If you are used to AWS VPC, Azure VNet, or GCP VPC networks, map that mental model to these Neutron primitives inside a **project**.

## How the pieces map

| VPC habit | On Quake AI |
|---|---|
| One isolated network per environment | Create a **private network** per tier or environment |
| Subnets in availability zones | **Subnets** with CIDR blocks on that network |
| Internet gateway + route tables | **Router** attached to `PublicStatic` plus static routes |
| Elastic IP on a private instance | **Floating IP** associated to the instance port |
| Security group / NACL | **[Security groups](/docs/network/concepts/security-groups)** on ports (stateful rules) |

Each project scopes networks by default. Instances on the same private network reach each other at Layer 2; routers provide north-south paths and NAT.

## On Quake AI

Built-in external networks include **PublicEphemeral** (direct provider attachment for quick tests) and **PublicStatic** (routed access through a router). Production layouts typically use a private network, a router, and floating IPs rather than attaching workloads directly to a public provider network.

## What other providers call this

| Provider | Their term | Quake AI mapping |
|---|---|---|
| AWS | VPC | Networks + subnets + routers |
| Azure | Virtual network (VNet) | Networks + subnets + routers |
| Google Cloud | VPC network | Networks + subnets + routers |
| DigitalOcean | VPC | Networks + subnets (region-scoped attachment rules differ) |
| Hetzner | Network | Private networks attached to servers |

## What to read next

- [Networks](/docs/network/concepts/networks): private segments, built-in external networks, and topology
- [Build a private network with two VMs](/resources/deployments/build-private-network-two-vms): hands-on VPC-shaped layout
- [Migrate from an AWS VPC](/docs/network/migration/migrate-from-aws-vpc): subnet and routing cutover patterns