One data plane. Four kinds of network.

BNGSOFT runs subscriber termination, carrier-grade NAT, hierarchical QoS and ACLs as a single XDP data plane on commodity x86 — 50 Mpps per box with every feature enabled. What changes between deployments is the shape of the network, not the software.

BNG solutions diagram: one BNGSOFT XDP data plane serving broadband ISPs, IPTV and OTT, low-latency and satellite networks

Who this is built for

Each page below covers sizing, the traffic assumptions behind it, and what the box does under load in that specific environment.

Whichever network you run, all four BNG solutions share the same software: PPPoE and IPoE termination with RADIUS AAA and CoA, port-block CGNAT with NAT64 and MAP-T, hierarchical QoS, ACLs and BGP border routing — one XDP data plane at 50 Mpps per box. It runs on a commodity x86 server with Intel X710, XL710 or E810, or NVIDIA ConnectX-6 Dx network cards, and upgrades in service without dropping subscriber sessions.

Broadband providers

PPPoE and IPoE termination, IPv4 conservation through CGNAT, and per-subscriber shaping on one box. Covers sizing from a single demo server up to a 56-core production node, RAM per port speed, and which NIC drivers are qualified.

IPTV and OTT operators

A white-label streaming and subscriber-management platform for operators who want to carry video themselves rather than hand the customer relationship to someone else.

Networks fighting last-mile latency

Enhanced Internet Acceleration reshapes how congestion is absorbed on a subscriber line, so a video call is not slowed by the same proportion as a bulk download sharing that connection.

Satellite operators

Long round-trip links break assumptions that hold on terrestrial networks. This covers what changes in CGNAT state handling, QoS behaviour and sizing when the round trip is measured in hundreds of milliseconds.

Questions that cut across all of them

Running it day to day

Upgrades, failure domains, observability and what an on-call engineer actually sees when something goes wrong.

Latency under load

Where delay is introduced in a subscriber path, and which parts of it a BNG can and cannot remove — including where L4S (IETF RFC 9330) helps.

Edge security

ACLs, filtering and abuse handling in the same XDP pass that already does forwarding, without a separate appliance.

Replacing what you run today

How this compares to chassis BNGs, other software BNGs and the separate-CGNAT-appliance model, on cost and on behaviour.

Buying questions, answered

Not sure which one fits?

Tell us the subscriber count, the port speeds and what terminates them today. We will tell you what the box does with it — or that it is a poor fit.

Need Solution?

Contact us if you need a solution.