N/A (No equivalent — Vultr VPC Networks do not expose an OpenStack-style router resource; routing is handled with a dedicated network gateway instance and static routes)

Quake AI concept: Routers

• Vultr’s VPC docs do not define a first-class router object like OpenStack Neutron routers. Instead, the FAQ says VPC does not support direct gateway services to public networks and instructs customers to create a dedicated network gateway instance inside the VPC to perform routing and gateway services (Vultr VPC FAQ).
• OpenStack Neutron routers are managed resources that connect subnets and external networks, but Vultr’s VPC docs describe routing as static routes uploaded on the VPC management page via Add Routes, not as a separate router resource with interfaces or external gateways (Vultr VPC FAQ).
• The VPC Networks page frames the network as a private isolated network for communication without traversing the public internet, and it separately documents a NAT Gateway for secure outbound internet access for private VPC instances (Vultr VPC Networks). This is different from OpenStack’s router model, where router and NAT behavior are typically part of the networking service rather than an adjacent instance-plus-gateway pattern.
• Vultr documents a hard limit of 5 VPC networks per location, which is a resource constraint on the network model itself rather than a router quota in the OpenStack sense (Vultr VPC FAQ). The same FAQ also says VPC supports multicast, which is a network capability that is not a standard characteristic of OpenStack router resources (Vultr VPC FAQ).