Skip to content

Knowledge catalog

Generated reference

Read-only pages rendered from the Quake AI knowledge graph.

Competitor MappingReference node

N/A (No router resource — VPC NAT Gateway for egress only; no inter-VPC routing)

Competitor mapping for DigitalOcean.

This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.

Details

Provider
DigitalOcean
Service term
N/A (No router resource — VPC NAT Gateway for egress only; no inter-VPC routing)
Provider documentation
External reference

Behavioral divergences

N/A (No router resource — VPC NAT Gateway for egress only; no inter-VPC routing)

Quake AI concept: Routers

  • DigitalOcean has no managed router resource. The VPC NAT Gateway (GA November 2025) handles outbound internet egress for private Droplets; it is not a general-purpose router and does not support inter-VPC routing.
  • Neutron routers connect multiple networks and subnets with configurable routing tables. DO's VPC is a flat network; there is no concept of connecting multiple VPCs via a router in the data plane.
  • Neutron supports east-west routing between subnets on the same router. DO Droplets in the same VPC communicate directly over private IPs without any router provisioning.
  • NAT Gateway in DO is provisioned at the VPC level (POST /v2/vpc_nat_gateways) with no concept of router interfaces or subnet attachments. Neutron router-interface-add attaches specific subnets to a router for controlled routing.

Related

Citations

  1. DigitalOcean
  2. DigitalOcean

These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.