N/A (No router resource — static routes via network routes API)

Quake AI concept: Routers

• Hetzner has no managed router resource. Inter-subnet and internet routing is configured via static routes in the network (POST /v1/networks/{id}/routes) pointing to a gateway server IP. Neutron provides a managed router resource (POST /v2.0/routers) with a dedicated control-plane service.
• Adding an external gateway in Neutron (connecting a router to the external network for floating IP allocation) is a single API call. On Hetzner, internet egress requires provisioning a server with IP forwarding and iptables MASQUERADE configured as a NAT gateway — all manual or IaC-managed steps.
• Neutron router interfaces can be hot-added and removed. Hetzner routes are defined at the network level and take effect in the SDN without a dedicated router resource to manage.
• Dynamic routing protocols (BGP, OSPF) are not supported on Hetzner private networks; Neutron supports BGP via the neutron-dynamic-routing extension.