Cato Networks has introduced a modular way to adopt its SASE platform, letting organizations start with what they need and expand over time. Instead of committing to a full deployment upfront, teams can roll out capabilities like AI security, SD-WAN, SSE, or zero trust access in phases, all within the same platform.
That reflects how most organizations actually modernize today. Large, all-in transformations are harder to execute, budget for, and maintain. Incremental adoption is more realistic. The challenge has been that adding tools over time often creates more complexity. Cato is trying to remove that tradeoff by keeping everything inside a single system from the start.
Why modular adoption matters operationally
In many environments, what’s called a platform ends up behaving like a bundle of separate products. Each comes with its own console, policies, and data. Over time, that creates gaps in visibility and adds work for already stretched teams. Cato’s model is built around a shared foundation, with one management console, one policy framework, and one data layer. The idea is that adding a new capability doesn’t introduce a new system to manage.
For MSPs, that has a direct operational impact.
Brian Anderson, global field CTO at Cato Networks, told ChannelE2E, “Modular adoption only reduces complexity if it’s built on a true platform. Not a collection of stitched-together products. With Cato, all capabilities run on a single platform with a single management console, single policy framework, and single data lake. For MSPs, that eliminates the need to integrate and maintain multiple tools, reduces console sprawl, and ensures consistent policy enforcement across all tenants.”
That consistency shows up in day-to-day work. Less time spent switching between tools, less effort correlating data, and fewer gaps between systems.
Anderson points to how partners should measure the impact: “Fewer vendors per customer, reduced onboarding time, lower MTTD/MTTR, and decreased operational hours per tenant. The real value is in removing integrations as an ongoing burden, which is where most hidden costs and inefficiencies typically live.”
Packaging services without breaking the model
One of the harder problems for MSPs is keeping service delivery consistent while adding new capabilities. Each new tool can bring its own SLA, performance profile, and operational workflow.
Cato’s modular approach tries to avoid that. Since every capability runs on the same platform, MSPs are enabling features rather than introducing separate products.
“Because all modules are delivered from a single platform and single policy framework, MSPs can package services without fragmenting delivery,” Anderson says. “Instead of managing separate products with different SLAs, they’re enabling capabilities within a single platform. That allows for clean packaging, while maintaining consistent performance for customers.”
This matters for scaling services. Consistency across tenants is what makes multi-tenant operations efficient. Once that breaks, margins usually follow.
AI security as an entry point
One notable piece of this announcement is that AI security is positioned as a standalone module. That lines up with how quickly AI tools are showing up across enterprise environments.
Security teams are now dealing with shadow AI usage, third-party AI apps, and early-stage agent workflows. These are not edge cases anymore. Making AI security something organizations can adopt first suggests it’s becoming a baseline requirement.
It also gives partners a clear starting point for new conversations, especially where AI usage is already visible but not well controlled.
A different sales motion for partners
The modular model also changes how partners go to market. Instead of leading with a full platform pitch, they can start with a specific problem and expand from there.
“Modular adoption shifts the sales motion from major networking and security transformations to a flexible land-and-expand model,” Anderson says. “Starting with a single use case - like AI Security, SD-WAN, SSE, or UZTNA - lowers the barrier to entry and helps partners align with immediate customer needs.”
That doesn’t mean giving up on the platform story. The expansion path is still built in.
“Every module is delivered from the Cato SASE Platform, so partners aren’t deploying a point solution,” Anderson adds. “They’re delivering capabilities from a platform that can expand without re-architecture or additional integrations.”
For partners thinking about deal size, the tradeoff is different. “Rather than leaving money on the table, this approach typically increases win rates and accelerates time-to-value, which drives stronger long-term revenue,” Anderson says. “The most successful partners will land with a focused use case but position the broader platform vision early.”
There is a shift in how SASE platforms are being adopted. Organizations are still working toward converged networking and security, but they are doing it step by step. Vendors that support that approach without adding integration overhead are better aligned with how teams actually operate. For MSPs, platform value shows up in how easy it is to run, scale, and standardize services across customers. If adding a new capability means adding a new system, the model breaks. If it stays within the same platform, it becomes something teams can build on.
