Hi everyone,
I've noticed a lot of initial "getting started" impressions and vendor-provided case studies about Cato Networks, but I'm more interested in the long-term operational view. The first year is when the real patterns and friction points emerge.
For those who have been running Cato in a live B2B SaaS or similar environment for about a year or more, what's your genuine experience? I'm particularly curious about a few things:
* **Stability & Performance:** How has the SDP/SSE platform held up? Any unexpected latency or reliability issues that weren't apparent in the PoC?
* **Operational Reality:** Is the centralized management truly as simplified as advertised? What does your team's weekly "keeping the lights on" workflow actually look like now?
* **Cost & Scaling:** Has the pricing model been predictable as you've grown? Any surprises when adding new offices, cloud regions, or remote users?
We all know the sales deck. I'm hoping we can share some grounded, practical insights here—the good, the bad, and the lessons learned. This kind of feedback is invaluable for others going through their own vendor evaluation.
Looking forward to the discussion.
~ Amy
Great questions, Amy. We've been on Cato for about 14 months now, and I can share a few observations from our mid-size SaaS operation.
On your point about stability, it's been solid for the core SASE connectivity, but we did see some intermittent latency spikes with their cloud-based threat prevention on west coast POPs last fall. Support acknowledged it as a capacity issue and resolved it within a week, but it's a reminder that "cloud-native" doesn't mean you're immune to growing pains. The weekly operational reality is mostly quiet, which is a good thing. The management console is genuinely simpler than our old stack, but the real simplification came from forcing us to standardize our policies globally. That's a hidden operational cost up front.
The pricing has been predictable for scaling users, but watch the data inspection tiers if your traffic profile changes. We got a surprise on our last true-up because we hadn't fully accounted for the increase in encrypted traffic inspection when we rolled out a new internal tool.
Be kind, stay curious.