Skip to content
Digital RF Twin

Ray-traced propagation. Live.

A physics-accurate 3D twin of your wireless environment. Drag sliders to see propagation update in real time. Or describe your space and let GenAI design it.
Next run≈ 3–6 creditsDesign
No runs yet on this tool
GenAI design from prompt
Beta
Floor 03 · live ray-trace
12 APs · 6 GHz · 40% wall loss
RAY-TRACING
ch37ch53ch69ch85ch101ch117ch133ch37ch53ch69ch85ch101
min RSSI: −66 dBm
SNR avg: 37 dB
capacity: 1.8 Gbps
What-if controls
Band
Twin layers
Twin metrics
Sim time
12ms/frame
Rays traced
15,360/s
Coverage
92%
Twin drift
0.4%
Network twin workspace
Dynamic topology templates · traffic flow · failover · DOCX/PDF export
Hot-swap between Campus, SD-WAN and OT/IoT topologies. Animate a flow, simulate a failure, and export a branded executive or engineering report.
Template
13 Healthy
Live · updated 0s ago
Flow · hop 1/4
Status Healthy Degraded Down
Click a node for details
Hub-and-spoke SD-WAN with SASE
SD-WAN Multi-Site

vManage-orchestrated SD-WAN fabric across HQ + 5 branches, MPLS backup transport, and Zscaler SASE for SaaS/private-app access.

Traffic flow
2 scenarios
Hop 1/4
App class
SaaS · DIA breakout
Bandwidth
Avg 8 Mbps per session
Latency
< 120 ms RTT

App-route policy classifies Salesforce on the SFO CPE and breaks out directly to the internet rather than backhauling through HQ. SASE inspection still applies.

Path
u2br2sasesaas
  1. 1
    u2 → br2
    Wi-Fi 6 client, voucher-auth on guest VLAN
  2. 2
    br2 → sase
    GRE tunnel to Zscaler ZIA POP
  3. 3
    sase → saas
    ZIA inspects + forwards to salesforce.com
Failover
Recovery
BFD detects in 300 ms, MPLS path active in ~700 ms
Mechanism
App-route policy with SLA failover to MPLS
Blast radius
84 users · ~700 ms reconnect
Primary path
u1br1hq
Failover path
u1br1mplshq
  1. 1
    BFD probes on the internet transport go silent for 3 consecutive intervals (300 ms total).
  2. 2
    vManage app-route policy 'CRITICAL' shifts SAP traffic to the MPLS standby tunnel.
  3. 3
    TCP sessions re-establish; Outlook/Teams reconnect within ~1.5 s thanks to keep-alives.
  4. 4
    Once the primary circuit returns and stays up for 60 s, traffic preempts back to internet.