VPC Networks

Quake AI concept: Networking

• Vultr’s base private networking primitive is a region-scoped VPC network, described as a private, isolated network for Vultr resources, rather than an OpenStack-style model of user-composed networks, subnets, and routers. The canonical VPC page does not describe first-class subnet or router resources as part of this primitive. (Vultr Docs)
• Vultr explicitly pairs VPC Networks with a separate NAT Gateway product for outbound internet access from private VPC instances. The docs describe NAT Gateway as providing secure outbound internet access and also mention firewall rules and port forwarding for inbound control, which is a different split from OpenStack Neutron’s router/NAT composition model. (Vultr Docs)
• Vultr instance deployment exposes networking as a choice of connectivity mode, including public IP directly on the instance or private instance behind a NAT Gateway in a VPC Network. That implies networking is attached through instance provisioning choices rather than by assembling ports, routers, and floating IPs as separate Neutron resources. (Vultr Docs, Vultr Docs)
• The VPC Networks page emphasizes management actions such as provision, manage, delete, and monitor, but it does not document OpenStack-like per-port interface objects or a discrete router API. In the canonical docs I found, the only concrete networking resources named alongside VPC are NAT Gateway and related firewall/port-forwarding controls. (Vultr Docs, Vultr Docs)