Competitor MappingReference node

VPC

Competitor mapping for Linode (Akamai).

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

Details

Quake AI concept: Networks

VPCs are region-scoped and isolate Linodes from the public internet and from other customers; OpenStack networks are project-scoped Neutron networks.
A VPC contains one or more subnets, each with a CIDR block defined at create time; routing between subnets is implicit within the VPC.
Linodes attach to a VPC by configuration interface rather than via Neutron ports; trunking is not the same model.
VLANs and VPCs are distinct products; OpenStack collapses these into Neutron network types (vlan, vxlan, geneve).

Quake AI concept: Networking

Linode exposes networking as per-instance interfaces managed in Cloud Manager and the Linode API, not as OpenStack Neutron networks, ports, and routers. The docs say Linode interfaces are directly associated with a given Linode and can be public, VPC, or VLAN, with API operations like `GET/POST /{apiVersion}/linode/instances/{linodeId}/interfaces` and `GET /{apiVersion}/networking/vlans`.
A Linode can have at most one VPC interface, at most one public interface, and multiple VLAN interfaces only if they belong to distinct VLANs. That is a different resource model from OpenStack's general network, subnet, port, and router topology.
VPC public internet access is modeled as an optional interface setting called `Allow public IPv4 access (1:1 NAT)`, and the docs also expose separate IPv4 sharing and assignment operations such as `POST /{apiVersion}/networking/ipv4/share` and `POST /{apiVersion}/networking/ips/assign`. OpenStack instead typically models NAT and floating IP behavior through routers, external networks, and port associations rather than an explicit per-interface 1:1 NAT toggle.
The VPC workflow is tied to Cloud Manager and requires power-off for many interface changes, including adding interfaces and editing VPC settings. The docs also state VLAN interfaces cannot be edited in place and must be deleted and recreated, which is more restrictive than OpenStack's usual mutable Neutron port and subnet update model.

Quake AI concept: Routers

Linode does not expose a standalone router resource; routing between VPC subnets is implicit, and egress to the internet is provided by the Linode's public interface, not a Neutron router.
There is no equivalent to Neutron router gateways or SNAT-from-router; outbound NAT happens at the Linode interface level.
Cross-VPC routing requires VPC peering-equivalent features that are not exposed at the same surface as Neutron routers.

Quake AI concept: Subnets

Subnets exist only inside a VPC and inherit its region; OpenStack subnets attach to any Neutron network in the project.
CIDR is set at subnet create time and is not editable post-creation; OpenStack allows allocation pool changes more freely.
Linode does not expose DHCP options or host routes as first-class subnet attributes.

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