OPERATE · Console

One UI for the whole stack.

Operate Runner agents, EdgeGuard nodes, and TinyCore NFs from one browser. Headless products stay headless — the console is management plane only.

browser ingress

products under one UI

RBAC

viewer · operator · admin

impact on the data plane

Surfaces

Operate every plane.

One login, three product areas. Authoring stays in YAML and policy files; the console is for operation.

Agents, flow catalog, environments, subscriber pool, schedules, and report history. Dispatch a job and watch EngineResult stream back.

Registered edge nodes, SBI producers and stats, Diameter peers and routes — without SSHing every host or juggling admin UIs.

Discover TinyCore NFs via the NRF and open per-instance views. The core keeps serving if you take the UI offline.

Principles

The console never sits in the signalling or user plane. If it is down, the network keeps running — you only lose the UI.

Runner, EdgeGuard, and TinyCore stay CLI- and API-first. The console is the single browser surface — nothing embeds a second SPA per binary.

Runner agents register over gRPC reverse-tunnel — NAT-friendly, no inbound ports on the lab host. Control plane always dials out.

One identity for the suite: viewer (read), operator (mutate), admin (users). JWT on the console; product-side trust stays separate.

Topology

Operators only reach the console. Headless products sit below it on the management plane — never on the data path.

UI + BFF · management plane

dflux Console

HTTPS from browser

Runner agents · gRPC tunnel

d3x-run

EdgeGuard nodes

d3x-edge

TinyCore NFs · via NRF

d3x-core-*

Management plane · not on the data path

Next step

Tell us about your lab or production edge — we'll walk through the suite.