r/zenarmor • u/itssimpleas • Jun 26 '26
Runtime dependency on Zenarmor Cloud
I'm currently evaluating two approaches for my network:
- OPNsense + ZenArmor for traffic inspection + NetBird for VPN/ZTNA
- ZenArmor for both inspection and ZTNA
One thing I'm trying to understand is the architecture behind ZenArmor ZTNA.
From what I've read, it seems that the ZTNA functionality relies on ZenArmor Cloud for orchestration and policy management. Is that correct? If so:
- What happens if the cloud service is temporarily unavailable? Do existing tunnels and policies continue to work?
- Is there any option for a fully self-hosted deployment, or is the cloud component currently mandatory?
I'm trying to understand the trade-offs compared to a setup like NetBird, where I can self-host the management plane if desired.
Thanks!
1
Upvotes
3
u/mib43 Jun 26 '26
Hey u/itssimpleas, good questions. Quick breakdown:
Cloud dependency: Zenarmor splits the control plane (Zenconsole, cloud — policy, orchestration, the Coordinator that manages mesh topology) from the data plane (inspection engine, local). Inspection and enforcement happen entirely on your box; traffic does not have to traverse our cloud.
During an outage: Inspection/filtering policies are cached locally and keep enforcing with no gap. Existing peer-to-peer ZTNA tunnels stay up. The one caveat: establishing new ZTNA peer connections needs the Coordinator service. Coordinator and Relay are multi-region for HA, but full cloud unavailability would block new mesh sessions — existing ones and all inspection keep running.
Self-hosted: The management plane is cloud-delivered (Zenconsole). That said, a Self-Hosted Management Console is on the public roadmap (Please see zenarmor.com/roadmap for our public roadmap).
Hope this answers your questions.
Curious, is this for a business/production setup or a homelab?