Real Sovereignty.
Software sovereignty has two sides: open source code and open interfaces. Both allow you to replace components and vendors. Staying with us is a choice rather than an obligation.
What sovereignty means at BISDN
Open interfaces
Between the OLT and management system, BISDN uses NETCONF/YANG according to BBF TR-383 and TR-385. Between the BNG and AAA, it uses RADIUS. Within the BNG, the separation of control and user planes follows the TR-459 architecture. At each of these interfaces, a component can be replaced, including with one from another vendor.
Open source code
BISDN Linux source code is available on GitHub, except for OF-DPA and the firmware for Trident-3 switches. For BNGbox and PONbox, you receive the source code of the open source components. BISDN retains its integration code. On request, we place it with an escrow agent who releases it to you if we stop maintaining it. The BISDN Linux page explains what is open and what is not.
A team that understands the code
Open source code is useful only if someone can read and change it. That can be your own team or ours in Berlin, working in German or English. This is why interfaces matter: they allow you to replace components without knowing the code behind them.
No hardware lock-in
Whitebox switches with Broadcom ASICs from several vendors. PON modules from Tibit and Sercomm. The BNG runs on commodity servers.
No forced cycle
The operator decides when to patch and schedules maintenance windows. There is no vendor-imposed obligation to upgrade. That makes a difference when dealing with incidents and security vulnerabilities.
One open source project and two products built on it.
BISDN Linux is open source. BNGbox and PONbox are built on open components and open interfaces, but are not themselves open source.
| Component | Open source, in your hands | Shipped as a binary |
|---|---|---|
| BISDN Linux | The entire operating system, including OpenBCM. Developed and maintained in Berlin, with a build process that can be traced through OpenEmbedded and Yocto. | OF-DPA, firmware for Trident-3 switches |
| BNGbox | The components on which BNGbox is built: VPP, DPDK, FRR, FreeRADIUS, ISC Kea and accel-ppp. You receive their source code as required by their licences. | BISDN integration code: control, configuration and communication over NATS JetStream. |
| PON and pOLTA | BISDN Linux on most of the underlying switches. The management interface is NETCONF/YANG according to TR-383 and TR-385, with netopeer2 ↗ and sysrepo ↗ providing the server. | BISDN controllers: vOMCI, switch controllers and drivers for Tibit and Sercomm, implemented as sysrepo plugins. Also the firmware for the PON modules. |
Tell us how we can put you in control
A technical conversation, followed by a test in the BISDN Lab.