VPC Networks

Quake AI concept: Ports

• Vultr describes this model as a "private, isolated network" for communication between Vultr resources, rather than an OpenStack Neutron-style first-class port object with per-port lifecycle and attachment semantics. The canonical VPC page does not describe a separate port or NIC resource model. (VPC Networks)
• The VPC documentation centers on network-level attachment and NAT Gateway usage, not on creating and managing standalone interface ports through a Neutron-like API. The page explicitly says VPC Networks are for resources to communicate without traversing the public internet. (VPC Networks)
• Vultr documents NAT Gateway as a separate network product with outbound internet access and port forwarding controls for private VPC instances, which is a different abstraction from OpenStack's port-centric networking model. The VPC page names NAT Gateway as a related resource and gives it its own management and deletion behavior. (VPC Networks)
• On the IPv4 instance networking page, adding another public IPv4 is done with `POST https://api.vultr.com/v2/instances/{instance-id}/ipv4`, and the documented console flow says the action attaches a new public IP and restarts the instance. That is instance-scoped address management, not a separate persistent network-interface port resource. (How to Add IPv4 Addresses on a Vultr Optimized Cloud Compute Instance)