three use cases
Audit. Prove. Simplify.
One engine, three things it gets bought for. Every estate starts at the same place — a read-only audit — and only the second and third depend on the fabric work.
0100 pick the one you are buying
Each one is independently useful.
Segmentation audit
Know what your network is actually doing.
A three-way compare between declared intent, the configuration in force, and observed traffic. Every rule and every flow classified with a reason attached, not a hit count. Works on estates with no Kubernetes at all — exports only.
core · read-only
Path & jurisdiction assurance
Prove the traffic took the path you prescribed.
Per-segment counters turn “no undeclared segment was ever executed” into a provable negative rather than an absence of alerts — at any volume, because a counter is a counter.
SRv6 in path
Network simplification
One control plane instead of five.
The transition case is simplification, not renumbering: fewer moving parts in the core, no per-tunnel state to scale, and a plan that strands nothing. Reversible by design.
core · planning SRv6 fabric
All three start identically: a read-only audit.
e000 End.DT6 deliver
See it against your own kit.
30–60 minutes. Read-only. We compare your declared intent to what is actually running, and hand back the gap list.
Nothing is installed to have this conversation.