ABOUT BNGSOFT

Ten people who wrote the data plane

There is no support tier between you and the engineers who built the forwarding path. When you report something in the data plane, it reaches the person who wrote that code path.

What we build

BNGSOFT builds carrier BNG/BRAS and CGNAT software that runs on commodity x86. One XDP data plane handles subscriber termination, address translation, hierarchical shaping, filtering and border routing on a single server — no appliance, no line cards, and no per-subscriber licence tied to hardware.

The platform ships as OrionOS, a purpose-built carrier image built from source into one signed artefact rather than a general-purpose distribution with a BNG installed on top.

How we work

Kernel depth, not workarounds

When a NIC driver misbehaves at line rate, the fix goes into the driver. We are not assembling other people’s components — we maintain the path a packet actually takes.

Patched in days, not release trains

Releases 6.46 and 6.47 shipped on consecutive days, 18 and 19 August 2026. An upstream Python snapshot dated 1 September shipped in a release on 4 September.

One artefact, every node

The platform is built from source into a single image and flashed. Configuration drift between nodes cannot change what code is running.

Small enough to answer

Ten people. No support tier sits between you and the engineers who wrote the forwarding path.

Security and patch policy

A BNG sits between every subscriber and the internet, which makes it the most security-sensitive box in the access network. Three things a vendor-security review actually asks:

Attack surface

OrionOS ships the kernel, the XDP forwarding path, the BNG daemon and very little else. If a package or daemon is not required to run a BNG, it is not in the image. A vulnerability in a package you never shipped is one you never patch, never test and never explain.

Image integrity

Boots from a signed image into a RAM root, so every reboot returns the node to a known-good state. The data-plane binary comes only from the built boot image — no ad-hoc local change survives.

Patch cadence

Release contents and dates are published and checkable against upstream release dates. Because the data plane is software on x86, a security fix is a build — not a line-card refresh.

Release contents and dates are published and checkable against upstream release dates. The technical record sits in the brief library: 83 briefs and datasheets.

What we don’t claim

Not certified. We hold no Common Criteria, FIPS or equivalent certification, and we do not imply one.
Not zero CVEs. We ship a kernel and a userspace. What we claim is a small surface and a short interval between an upstream fix and a shipped release.
Not legal compliance. We produce the records a retention or intercept obligation needs. Mapping them to your legal regime is yours.

If your security team has a standard assessment, send it. Questions we cannot answer honestly we will say so about, rather than returning a form with every box ticked.

Prove it on your hardware

A proof of concept runs on your own x86 against your own traffic. Send subscriber count and busy-hour throughput and we size it with you.

sales@bngsoft.com