NAT Gateway

Quake AI concept: NAT

• Vultr documents NAT as a separate managed feature inside VPC Networks rather than an OpenStack Neutron router construct. The canonical page describes it as a way to provide secure outbound internet access for private VPC instances, with inbound control handled by NAT Gateway firewall rules and port forwarding. Vultr Docs
• The Vultr docs emphasize gateway provisioning and management workflows, including view details and delete operations, rather than OpenStack-style first-class router, subnet, and port attachment semantics. The page sections explicitly call out Provisioning and Management for the NAT Gateway. Vultr Docs
• Vultr states that NAT Gateway firewall rules can be created, listed, read, updated, and deleted via portal or API. That is a different abstraction from OpenStack Neutron's router-centered NAT behavior, where NAT is typically achieved through router gateway/port rules rather than a dedicated managed NAT gateway object. Firewall Rules | Vultr Docs
• The canonical VPC Networks page does not state billing details or a public API resource path for the NAT Gateway itself, so those behaviors cannot be asserted from the doc. OpenStack implementations usually expose networking resources directly through Neutron APIs, while Vultr's cited docs focus on the managed product surface instead. Vultr Docs