LIVE → traffic flows
Authorization is valid.
Traffic flows.
Devices are online.
For MSPs managing 10–500+ client networks
Your clients’ networks are active — by default.
Networks should not exist unless explicitly allowed.
When a breach is detected — how long before you can actually stop traffic from leaving?
WATCH THIS 30-SEC DEMO.
Patent pending — App. 19/418,995 · Pilot pricing available · No per-seat licensing
Proof of enforcement
Authorization isn’t a setting. It’s a condition. Without it, the network can’t exist.
DARK → forwarding stops
Authorization revoked.
Traffic stops.
External access is cut off.
Instantly.
LIVE → restored
Authorization restored.
Traffic resumes.
Changes are remote and auditable.
No dependency on a live connection
Authorization is enforced locally. If it is not valid, traffic does not move. Independent of connection state.
Authorization is tied to device identity
Authorization is tied to a single device. Only the intended router can act on it.
No lease. No forwarding. No network.
Controlled rollout for live client networks.
Pilot deployments with live enforcement validation.
Structured onboarding, enforcement validation, and staged rollout before production expansion.
Hardware-backed deployment
Runs on validated OpenWrt hardware. Enforcement happens on the router. Not in the cloud.
Deployment configuration
Deployment staged and verified before enforcement activation. Authorization and enforcement configured per client environment.
Monthly platform
Flat monthly pricing based on fleet size. No per-seat licensing. No per-device costs.
Enforcement validation
Validate enforcement behavior in a live client environment before wider rollout. Test containment and recovery under real network conditions.
Staged validation → confirmed enforcement → production rollout.
Built for MSPs managing client networks
Control whether any client network is allowed to operate.
Security incident
Compromised device or suspicious activity. Revoke authorization. Traffic stops. Restore when resolved.
Deployment control
New site or device comes online. Authorization is required before any traffic flows. Nothing goes live by default.
Access control
Decide exactly when a network is active. Revoke or restore at any time.
Is this a remote toggle?
No. Enforcement happens on the router. If authorization is not valid, traffic does not forward.
What hardware does this run on?
OpenWrt-based devices. Deployed on validated hardware. Support expands over time.
Does this replace our RMM?
No. Your existing tools remain. R66 Network controls whether the network forwards traffic. Everything above that layer continues to operate normally.
What happens if your servers go down?
Enforcement happens locally on the router. If authorization cannot be verified, traffic stops when the current period expires.
Pilot deployments open for qualified MSP partners.
Live enforcement. Validated deployment. Controlled rollout.
Patent pending · Working system · Enforcement active
Control at the forwarding layer.
R66 Network — for MSPs operating real networks.
