Elastic BNG and eSwitch share one architecture: three independent planes that scale, upgrade, and fail on their own terms. Here's how a subscriber packet moves through it.
Declarative intent, GitOps pipelines, streaming telemetry, and lifecycle. This is where operators express what the network should do — and where every change is versioned, canaried, and reversible.
Session state, AAA, routing, and policy computation run as a highly-available cluster. It programs the user plane over a standard interface (PFCP-style) and holds the authoritative view of every subscriber.
Line-rate forwarding on merchant silicon or DPDK. Stateless instances you add and remove freely — QoS, CGNAT, and encapsulation all happen here, at sub-microsecond latency.
Capacity is a number of instances, not a hardware SKU. Every plane scales horizontally on commodity servers and whitebox switches.
Subscriber state lives in a distributed store. Any data-plane instance can take over a session, so a failure drains instead of drops.
PFCP, RADIUS, BGP, gNMI, OpenConfig. Interfaces are open so the platform drops into networks you already operate.
Every plane streams telemetry continuously. You debug the live network with the same data the control loop uses.
Our architects will walk your team through a deployment tailored to your topology.