Fail-safe
What survives a console restart
If the dashboard stops, the office must keep working.
- Sticky paths and NAT keep forwarding
- Last WAN weights and QoS stay applied
- Management services come back on their own
How it works
Desks use the EDGE as gateway and DNS. The edge owns the path. The console helps operators manage it. It does not carry your internet.
Traffic path
One clear chain. Mid-session ISP hop is forbidden. Sticky path is the product.
Office DHCP points gateway and DNS at the EDGE. Desk traffic enters one controlled edge.
Anti-spoof and firewall policy run first so unwanted traffic never reaches the sticky fabric.
Live sessions stay pinned to their ISP. New sessions follow Active-Active weights from the latest link quality.
Traffic leaves on the marked WAN. If that ISP fails later, existing flows drain on their path. New work moves to a healthy link.
Fail-safe
If the dashboard stops, the office must keep working.
Day-to-day
New-session weights update cleanly. Unchanged results skip rewrite. Dangerous all-links-off states are refused.
Rebuilding the sticky fabric can briefly disrupt. Use it at install, planned maintenance, or on a cold spare.
Prove it
Operators prove the edge with real health checks, not with a marketing animation.