Competitor MappingReference node
Hetzner Cloud Networking (Private Networks + Floating IPs + Firewalls)
Competitor mapping for Hetzner Cloud.
This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.
Details
- Provider
- Hetzner Cloud
- Service term
- Hetzner Cloud Networking (Private Networks + Floating IPs + Firewalls)
- Provider documentation
- External reference
Behavioral divergences
Hetzner Cloud Networking (Private Networks + Floating IPs + Firewalls)
Quake AI concept: Networking
- Hetzner's network model has three main primitives: Private Networks (L3 SDN), Floating IPs (public IP reassignment), and Firewalls (stateful L3/L4 rules). Neutron separates these into networks, subnets, routers, ports, floating IPs, security groups, and FWaaS rules as independently addressable resources.
- Hetzner does not have a concept of external networks, provider networks, or network types (flat/VLAN/VXLAN). All private networking is via Hetzner's proprietary SDN; Neutron supports multiple backend drivers (OVN, OVS, ML2 plugins).
- IPv6 on Hetzner private networks is not supported as of April 2026; only public interfaces can have IPv6 addresses. Neutron supports dual-stack subnets (IPv4+IPv6) on private networks.
- Hetzner network limits: max 100 servers per private network, max 50 private networks per project. Neutron quotas are operator-defined and typically much higher.
Related
Diverges from (incoming)
Citations
- Hetzner Cloud
- Hetzner Cloud
These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.