About dflux
Built for people who run 5G, not slide decks.
We build tools that protocol engineers, lab operators, and platform teams can actually run — in CI, on a laptop, and in front of real NFs.
About dflux
We build tools that protocol engineers, lab operators, and platform teams can actually run — in CI, on a laptop, and in front of real NFs.
Mission
dflux is a suite of 5G SA tools: a protocol tester, a signaling proxy, a lab core, and one operator console. Products stay headless. The console is management plane only. We document what we support — and what we don't.
The suite
Test, secure, and run on the wire — operate from dflux Console. Products share a protocol vocabulary and stay independent.
Expertise
The tools are only as good as their grasp of the protocols underneath. Ours are built around 3GPP control- and user-plane signaling and the service-based interfaces that tie a 5G core together.
Principles
A few decisions shape every tool we ship.
If it isn't something you can start with a binary or a compose file, we don't ship it as a product page.
Flow counts, protocol lists, and scope limits are generated from the source tree — the 452 on this page was counted by a script, not a marketer.
Data-plane tools stay CLI/API-first. One console for operators — never a second SPA per binary.
TinyCore is in early beta and we say so on its own page, next to the list of what doesn't work yet. Production-grade is where we're driving it — not a claim we make before it's earned.
Get in touch
Tell us what you're building — testing a core, fronting your signaling, or standing up a lab. comms@dflux.io