Nexaplane networking

The network is
part of the product.

Routers with the protocols a network engineer expects, VPN in one click, and one tenant across many sites — provisioned for each customer, isolated from every other.

What actually separates us

Every tenant gets
their own real routers.

Not a shared gateway with firewall rules bolted on. Each tenant runs their own routing appliances — as many as their network needs — with the protocols a network engineer expects, and none of the operational weight of Neutron or NSX.

Internet
Virtual RouterNAT · firewall · VPN · DHCP · DNS
Load BalancerL4 / L7 · TLS · health checks
Instance
Instance
Instance
Your other datacenters
Customer offices
Remote staff

One tenant. Everything above is provisioned automatically when they click create.

Routing that speaks the language

Your customers’ networks stop being an island the moment they need to reach anything else. Nexaplane gives them the protocols to do it themselves.

  • BGP and OSPF — peer a tenant network with real upstream routing
  • Dual-stack IPv4/IPv6 — not an afterthought; v6 firewalling and peering included
  • Automatic VLAN and subnet allocation — no spreadsheet, no collisions

Isolation you don’t have to configure

Each tenant lands on their own VLAN behind their own router. Noisy neighbours can’t reach each other because they were never on the same wire to begin with.

  • Stateful firewall — per tenant, enforced at their edge
  • Security groups — reusable rule sets applied to instances
  • Port forwarding — expose exactly what they mean to expose

Dual-stack, properly

IPv6 alongside IPv4 across routing, firewalling, peering and address pools — designed in from the start, not retrofitted as a checkbox.

Load balancing included

L4 and L7 balancers with TLS termination, health checks and sticky sessions — as a dedicated appliance, so heavy web traffic never starves routing. HTTPS certificates renew themselves, so expired-certificate outages simply stop happening.

Address management that holds

Public IPv4 and IPv6 pools, per-tenant allocation, DHCP reservations and port forwarding — tracked in one place instead of three.

When a machine fails, nobody notices

One switch makes any customer’s router or load balancer run twice, on two separate machines. If one goes down, the other carries on within seconds — sites stay up, VPNs stay connected, and nobody gets woken up.

  • Sell it as uptime — high availability becomes a line on your price list, not an engineering project
  • Nothing changes for the customer — switching it on means no downtime, no new addresses, nothing to reconfigure
  • No hidden cost — a protected pair doesn’t consume a second public IP address

Simple and secure

VPN that takes
one click, not one ticket.

Remote staff, a branch office, a second datacenter — three requests every hosting customer eventually makes, and three that normally mean keys emailed around, routing tables edited by hand, and an engineer on the call. Nexaplane terminates all of them on the router the tenant already has.

Remote staffclient VPN · WireGuard & IKEv2
Branch officesite-to-site tunnel
Second datacenterrouter-to-router interconnect
The tenant’s Virtual Routerone secure edge, encrypted end to end

No concentrator to buy, no tunnel to hand-configure, no routing table to maintain.

Client VPN people can actually enrol in

Give a person access and they get a working profile — not a config file and a phone call. WireGuard for speed, IKEv2 for the devices that insist on it.

  • One-time enrolment links — no keys pasted into email
  • Per-user access control — reach only what that person should
  • Full or split tunnel, per user
  • Rotate or revoke instantly when someone leaves

Interconnect in a single click

Two of a tenant’s routers, in different datacenters. Toggle the pair on and they are connected — the platform generates the keys, builds the tunnel and programs both sides.

  • Routes follow the network — add a subnet and the far side learns it
  • Conflicts flagged first — overlapping ranges surface before they break routing
  • Encrypted by default — WireGuard, with key handling out of your hands
  • Reversible — toggle it off and both sides clean up
Toronto10.0.1.0/24
London10.0.2.0/24

Toggle the pair on. Routes on both sides update themselves — and keep updating when the subnets change.

Multi-datacenter

One tenant.
Many sites.

Customers who grow past one location are the ones worth keeping. Nexaplane makes the second site a toggle rather than a project — no manual routing tables, no tunnel to hand-configure, no ticket.

See it on your own fabric.

Bring a Proxmox cluster and we will show you a tenant, a network, a router and a running instance — in the same call.

Launching 2027 · Early partners get direct input on the roadmap