Use case
Network Topology Visualization
Render telecom, ISP, datacenter, SDN, and NFV network topologies — at the scale operators actually run. TopoKit ships in production NMS, OSS, and observability dashboards.
The problem
Thousands of nodes per region
A regional NMS view can contain 5,000–20,000 nodes (RTN, PTN, eNodeB, BBU, RRU, microwave). Most JS libraries collapse past 2,000.
Service vs physical layers
Operators need to switch between service topology (path of a circuit) and physical topology (fiber, microwave, power) without re-loading.
Alarm propagation
When an OLT goes down, every downstream service should be highlighted in real time. Animation must not block panning.
Cross-team UX consistency
NOC, planning, and field teams all need the same map with different overlays. The SDK must theme and configure cleanly.
How TopoKit fits
20K-node Canvas2D + LOD
Smooth pan and zoom past 10,000 nodes thanks to spatial indexing and 4-tier LOD culling.
Built-in highlight + filter
highlight() and filter() APIs work with whatever your domain key is — service ID, region, OLT, status.
Force-directed edge bundling
Reduces visual clutter on dense fiber maps. One config flag.
Web-worker layout
Layout computation never blocks the NOC dashboard tick.
Dot-path data mapping
Map any OSS/BSS export (XML, JSON, GraphML) to nodes and edges with declarative rules.
White-label (Enterprise)
Ship the SDK inside your branded product without TopoKit attribution.
Ready to ship a real NMS view?
See the live telecom topology demo (real RTN/PTN/eNodeB data) or book a 30-minute call to walk through your topology requirements.