Jason Buffington .com

What if your backup software understood your business organization and what data mattered to your employees before it ever did a backup?

Most cyber resilience solutions don’t. Most are grounded in the foundational backups of your data, but they’re limited by the administrator who points them at the workloads and the policies that that instruct them to start making copies. Any other context or prioritization comes strictly from human conversations between business stakeholders, application owners, and backup administrators to configure protection frequency, repository locations, etc.

Backup is ‘the great aggregator,’ so one of the promises of AI-enhanced resilience solutions is the ability to analyze protected data across otherwise disparate repositories and silos. In theory, the potential is that AI could identify healthcare data that requires a different level of retention, identify financial data that might require a higher level of agility to recover, or recognize sovereign data that may require specific repositories – and then dynamically adapt the protection policies to affect those business requirements. All of those would be massive improvements in an organization’s overall data protection posture, but they all start after the first backup and are dependent on AI’s ability to affect backup policies.

Kaseya has something different in mind. At its Kaseya Connect 2026 conference, they announced ‘Kaseya Intelligence’ — an underlying AI foundation built upon a unified API that persists across the entire Kaseya portfolio which includes 3 super families of products: cyber resilience (backup/DR), cyber security (monitoring and detection), and infrastructure management; including the vision for third parties to also participate within the Kaseya ecosystem via that same API.

Many data protection solutions have varying degrees of integrations between cyber resilience (remediation) and cyber security (prevention), which certainly can aid in entropy detection, identifying clean recovery points, etc., but the potential of Kaseya’s vision is that both cyber portfolios would also be influenced by the infrastructure management product lines (and vice versa), including automation, helpdesk ticketing, and other foundational elements of IT operations that brings us back to the opening question:

What if your backup solution knew how the rest of your IT operated?

If your backup solution knew about your business units, could it customize its protection policies or prioritize its recovery workflows during a large-scale outage; so that the most important platforms came back first?  And then orchestrate those BC/DR/Cyber recoveries using the same operational workflow and automation frameworks that provision and manage the infrastructure to begin with?

If your backup solution understood your organizational structure, could it ensure which users needed endpoint protection like senior leaders and those in regulatorily mandated roles?

As ambitious as that vision sounds, it is grounded in CTO Pratik Wadher’s focus on the operational context that already exists across the Kaseya platform … not just within the protected data itself, but more relevantly within the surrounding information about users, endpoints, support workflows, infrastructure activity, and how those systems interact. It is that broader operational context that could ultimately inform how cyber resilience, cybersecurity, and IT management systems behave together.

Those are some of the potential outcomes for customers, but because Kaseya is focused on delivering its solutions through managed service providers (MSPs), there’s another question to be asked or empowered:

What if your service provider understood your business before they started backing it up?

Reread the opening questions on the human gaps that limit the technologies’ effectiveness for protecting the organization as adequately as possible. Now consider that when a partner is brought in to be part of your overall solution, they are equally (if not more so) limited by whatever level of onboarding is done to help the partner understand what really matters to the organization.

But what if instead, as the partner starts supporting the organization, the business processes, the core systems and platforms, and the users through its IT management frameworks … its backups, and therefore your cyber resilience, started organically improving? The improvements happened because the backup solution was learning from your networking and cyber security stacks on how data moves and understanding your business by how IT operates, which you could only do because all those solution stacks are being brought together through a single API that connects the stacks across the platform. That broader operational history, by nearly 20 years of precedent, could then help affect those policies.

Those are some of the implications of the Kaseya Intelligence announcements made at Kaseya Connect 2026, which will be interesting to watch as their vision unfolds and the next generation of their products are revealed.

It is important to note that the CTO’s vision does come with a caveat … ‘AI only works if the data foundation exists first.’

… which is likely why the CEO’s keynote started by reminding the audience about the 3 Exabytes of anonymized historical data, the 44B backup jobs per year, the 1B historical support desk tickets, the 1.2B patch results, the 16B security events, and the 17M managed endpoints. That’s what is informing Kaseya’s intelligence model.

Be sure to also check out some of the daily reactions as the event unfolded:

• Day 1 – What we will be listening for this week
• Day 2 – What we heard on ‘Cyber Resilience’ throughout the event
• Day 3 – Our favorite quotes and takeaways from the week

Leave your thoughts below.