
VDOM-based multi-tenancy is the standout feature for me. I used it to simulate an MSP-style environment with dual tenants on one VM, each with its own firewall policies, NAT and VLAN segmentation, without needing separate appliances or instances per client. SD-WAN with SLA-based link steering was straightforward to configure and handled automated failover reliably in testing. Site-to-site IPsec IKEv2 and SSL VPN setup is well documented and behaves predictably once the phase 1/2 parameters are right. The REST API is genuinely useful in practice, I wrote a Python script against it to audit policy hit-counts and flag zero-hit rules, which cut down manual policy cleanup significantly. For troubleshooting, diagnose debug flow and the built-in packet sniffer cover most break/fix scenarios without needing external tools. Review collected by and hosted on G2.com.
Resource sizing matters more than the marketing suggests. SSL inspection and multiple VDOMs can hit vCPU and RAM hard, and if you undersize the VM upfront, performance degrades in ways that are hard to diagnose without knowing to check resource utilization first. There's also a real gap between what's easy to do in the GUI versus the CLI, some policy and routing tasks are far faster in CLI, which means new admins face a learning curve before they're productive. Policy hit-count and log data isn't exposed as cleanly in the GUI as I'd like, which is part of why I ended up scripting against the API instead. Review collected by and hosted on G2.com.