Last updated
Quick Answer
Atlas Reach
Atlas Reach is the RMM built into the Atlas AVD endpoint agent, deployed with Atlas into your own Azure subscription, with technicians signing in through Microsoft Entra ID. It monitors every enrolled device with checks for CPU, memory, disk, services, event logs, HTTP endpoints, TCP ports, certificate expiry, your own scripts and SNMP network devices, under alert policies that inherit from global to tenant to device, and a failing check can run a remediation script. It approves Windows updates by severity and category and rolls them out ring by ring, keeps third-party software current through winget, and runs scripts on one device or hundreds, on demand or on a schedule. Remote view and control on Windows, macOS and Linux is limited to entitled operators, can be switched off for the whole deployment, uses an outbound-only channel, and every session is audited. Any AVD session host in a host pool Atlas has synced is free.
Kaseya VSA 10
Kaseya VSA 10 is available for SaaS and on-premises deployments. It monitors Windows, macOS and Linux endpoints, defines patch policies for operating systems and third-party software, runs Bash, PowerShell and VBScript scripts and event-triggered workflows, and adds mobile device management for Apple and Android devices. Two-factor authentication is enforced for every account, with SSO through KaseyaOne. It integrates with Autotask, Kaseya BMS and ConnectWise, and is bundled into Kaseya 365 Endpoint with EDR, antivirus and backup.
Feature Comparison
| Feature | Atlas Reach | Kaseya VSA 10 |
|---|---|---|
| Product category | RMM built into the Atlas AVD endpoint agent, alongside AVD management, documentation and ticketing | Standalone RMM, also sold in the Kaseya 365 Endpoint bundle |
| Hosting | Runs in your own Azure subscription as part of Atlas AVD; no RMM server to maintain | SaaS or on-premises; on-premises needs Windows Server and SQL Server, internet access, and no offline install |
| Technician sign-in | Microsoft Entra ID, so your MFA and Conditional Access apply | Two-factor authentication enforced for all accounts; SSO through KaseyaOne or OIDC |
| Agents | Windows, macOS and Linux | Windows, macOS and Linux, plus Apple and Android mobile device management |
| Patching | Windows update rings with approvals, plus third-party updates through winget | Patch policies for operating systems and third-party software, with Linux updates from the device card |
| Remote control | View-only or full control on Windows, macOS and Linux; entitled operators only, switchable off for the whole deployment | Remote control on Windows, and on macOS when no user is logged in locally; Kaseya notes devices hosted on Azure may have issues with its remote control tools |
| Remote session audit | Every view, control and terminal session in the audit trail, with full terminal transcripts | Session recording enabled per device profile, Windows to Windows only |
| Automation | Scripts on one device or hundreds, on demand or on a schedule; remediation scripts on failing checks | A script library, event-triggered workflows, and Kaseya Assist to build workflows from plain-language goals |
| Client grouping and permissions | Per-tenant data and access isolation; remote control limited to entitled operators | Devices grouped by customer, organization, site, group or tag; team permissions per organization |
| AVD session hosts | Free when the host is in a host pool Atlas has synced; every other managed device, an Azure VM that is not a session host included, is one unit | Priced by device volume like any other managed device |
| PSA integration | Two-way ticket sync with ConnectWise Manage; preview connectors for Autotask and HaloPSA; Atlas Flow ticketing in preview | Autotask, Kaseya BMS and ConnectWise (one PSA active at a time; the ConnectWise integration is one-way) |
| Works without the wider platform | Requires the Atlas platform and agent | Standalone RMM |
Comparison reflects publicly documented capabilities and each vendor's own positioning as of 2026-11-09. Vendors change their products and pricing; confirm current details directly, or contact us for a side-by-side on your environment.
Who Each Platform Is Best For
Atlas Reach is best for
- MSPs whose clients run on Azure and Azure Virtual Desktop and who want the RMM in the same console as the desktops
- Remote support for Azure-hosted session hosts and VMs, with every session audited
- AVD-heavy estates that don't want to license every session host
- Practices that want RMM data in their own Azure tenant without an on-premises server
Kaseya VSA 10 may be the better fit when
- You're standardized on Autotask and the wider Kaseya ecosystem
- You need mobile device management in the same tool
- You want RMM, EDR, antivirus and backup on one Kaseya 365 subscription
- You need an on-premises RMM
Pricing philosophy
Atlas Reach meters one unit per month for each managed device, drawn first from your plan's pooled allowance, with unlimited technician seats. Any AVD session host in a synced host pool is free however much Reach is used on it (a session host Atlas cannot verify yet is billed); every other managed device is a unit, an Azure VM that is not a session host included. Kaseya prices VSA 10 by device volume, deployment model and packaging through its sales team, so rather than quote a competitor figure we will model your actual device mix against the Reach meter.
Key Differences Explained
Remote support for Azure-hosted machines
Kaseya's own documentation for VSA 10 remote control says devices hosted on Azure may experience issues with its remote control tools, that macOS remote control works when no user is logged in locally, and that session recording is Windows to Windows. Atlas Reach is built around Azure and AVD: view-only or full control on Windows, macOS and Linux, limited to entitled operators, switchable off for the whole deployment, over an outbound-only channel, with every session and terminal transcript audited. If most of the machines you support live in Azure, test remote control on them during any evaluation.
Patching, automation and MDM
VSA 10 covers more ground here: patch policies for operating systems and third-party software, Linux updates from the device card, a script library with event-triggered workflows, Kaseya Assist for building workflows from plain-language goals, and mobile device management for Apple and Android. Reach approves Windows updates by severity and category, rolls them out ring by ring, updates third-party software through winget, and runs scripts and remediation across the fleet. If macOS patching or MDM decides it, VSA 10 is the safer fit.
Hosting and sign-in
VSA 10 runs as SaaS or on your own Windows Server and SQL Server; Kaseya's documentation notes the on-premises server needs internet access and can't be installed offline. Two-factor authentication is enforced for every account. Atlas Reach runs as part of Atlas AVD in your own Azure subscription, with no RMM server to maintain, and technicians sign in through Microsoft Entra ID so your MFA and Conditional Access policies apply.
AVD session hosts and pricing
Kaseya prices VSA 10 by device volume, deployment model and packaging, and Kaseya 365 Endpoint is licensed per endpoint. Every pooled AVD session host is another device, and pooled hosts are rebuilt regularly. Reach meters one unit per managed device per month from a pooled allowance with unlimited technician seats, and any session host in a host pool Atlas has synced uses no unit.
Pros and Cons
Atlas Reach
Pros
- Monitoring checks, inheritable alert policies and automated remediation built into the Atlas agent
- Windows update rings and patch approvals, plus third-party updates through winget
- Remote control limited to entitled operators, switchable off for the whole deployment, with every session audited, terminal transcripts included
- Runs in your own Azure subscription with Microsoft Entra ID sign-in and no RMM server to maintain
- AVD session hosts in synced host pools use no unit
- Atlas Vault documentation and Atlas Flow ticketing in the same console
Cons
- A younger RMM, with a smaller script and integration ecosystem
- Patching covers Windows updates and winget-managed software, not macOS
- Requires the Atlas platform rather than running standalone
- Autotask and HaloPSA connectors are in preview; ConnectWise Manage sync is two-way today
Kaseya VSA 10
Pros
- SaaS or on-premises deployment
- Operating system and third-party patch policies, including Linux updates
- Mobile device management for Apple and Android
- Event-triggered workflows and Kaseya Assist
- Bundled with EDR, antivirus and backup in Kaseya 365 Endpoint
Cons
- Kaseya documents possible remote control issues for devices hosted on Azure
- Session recording is Windows to Windows only
- One PSA integration active at a time, and the ConnectWise integration is one-way
- No Azure Virtual Desktop management in the same console
Frequently Asked Questions
Is Kaseya VSA 10 the same as Datto RMM?
No. Kaseya owns both, but they're separate products: Datto RMM is cloud-based, while VSA 10 is available as SaaS or on-premises. Kaseya 365 Endpoint lets you choose Datto RMM, VSA 10 or VSA 9 as its RMM.
Can Atlas Reach replace Kaseya VSA 10?
For Windows-centric MSPs whose clients run on Azure and AVD, often yes. Check the edges first: Reach doesn't patch macOS or manage mobile devices, needs the Atlas platform, and its Autotask connector is in preview.
Does Atlas Reach work with Autotask?
Atlas has an Autotask connector in preview, and syncs tickets both ways with ConnectWise Manage today.
How are AVD session hosts licensed?
In Atlas Reach, any AVD session host in a host pool Atlas has synced uses no unit; every other managed device, an Azure VM that is not a session host included, is one unit per month. Kaseya prices VSA 10 by device volume, so each session host counts.
Microsoft documentation referenced
- Kaseya: VSA 10
- Kaseya VSA 10 help: on-premises setup
- Kaseya VSA 10 help: remote control
- Kaseya VSA 10 help: scripts
- Kaseya VSA 10 help: two-factor authentication
- Kaseya VSA 10 help: team permissions
- Kaseya VSA 10 help: third-party integrations
- Kaseya VSA 10 help: ConnectWise integration
- Kaseya 365 Endpoint overview