If you already know OPNsense or pfSense, you already know the packet filter. SecureGuard is a commercial appliance OS on that family: objects and zones as one document, a preview of the rendered daemon diff, commit, rollback by id. You run it on hardware you own.
We sit above pf. We do not rewrite it. The product is closed-source orchestration, not another open-source distro you assemble. The AI layer proposes; a human commits. It is not MDR.
Same FreeBSD and pf family. We sit above pf; we do not rewrite it. SecureGuard is a commercial, closed-source appliance: one canonical config document, and orchestration that renders pf and the other daemons. OPNsense and pfSense are open-source distributions you assemble and operate yourself.
No. The AI layer proposes changes. A human commits. We do not advertise auto-block.
No. It is a next-generation firewall / UTM appliance. Endpoint agents and SOC-as-a-service are a different product.
OPNsense publishes named application control as a plugin, not the base CE; SecureGuard does not ship named application control, anti-spam, identity in policy, or off-box analysis — those four are coming soon.
Read what is actually built, the FAQ, the Sophos UTM replacement, the FortiGate alternative, and how the AI layer is allowed to act.