Datto RMM has been a staple in the MSP toolbox for over a decade. Then Kaseya bought Datto for $6.2 billion in 2022, and every MSP running the platform started asking the same question: is this still the right RMM for my stack?
Three years into the Kaseya era, we have enough data to answer that. This review covers what Datto RMM does well, where it falls short, what it costs, and when it makes sense to stay versus start shopping. No vendor spin. Just what MSPs need to know to make a decision.
What Is Datto RMM?
Datto RMM is a cloud-hosted Remote Monitoring and Management platform built for MSPs. It's agent-based – you install a lightweight agent on each managed endpoint, and the platform handles monitoring, alerting, patching, scripting, and remote access from a central dashboard.
Before the acquisition, Datto RMM was part of the standalone Datto ecosystem alongside Autotask PSA, Datto BCDR, and Datto Networking. Post-acquisition, it's now part of the Kaseya portfolio, sitting alongside VSA, IT Glue, BMS, and the rest of the Kaseya stack. This matters because Kaseya's bundling strategy directly affects pricing, contract terms, and your long-term vendor dependency.
If you're evaluating it fresh: Datto RMM is a mid-to-upper tier RMM designed for MSPs managing hundreds to thousands of endpoints. It's not entry-level, and it's not cheap.
Datto RMM Features: What You Get
Here's the feature-by-feature scorecard, then the details.
Feature Scorecard
| Feature | Rating | Notes |
|---|---|---|
| Agent stability | Strong | Lightweight, reliable, cross-platform |
| Monitoring/alerting | Strong | Flexible component monitors, requires setup |
| Patch management (Windows) | Strong | Good policies, scheduling, compliance |
| Patch management (3rd party) | Weak | Limited catalog vs. NinjaOne's 6,000+ apps |
| Remote access | Average | Splashtop built-in, Windows-focused only |
| Scripting/automation | Strong | PowerShell, batch, shell; powerful once built out |
| API | Average | REST API works, documentation could be better |
| Network discovery | Weak | Inconsistent detection, manual cleanup needed |
| Reporting | Weak | Basic built-in, most MSPs need third-party tools |
| UI/UX | Average | Functional but dated, steep learning curve |
Here's what the platform covers and where it's strong or weak in practice.
Datto RMM Agent. The agent is lightweight and deploys fast across Windows, Mac, and Linux. It's one of the more stable agents in the RMM space – rarely causes endpoint issues, doesn't bloat system resources, and handles remote commands reliably. Agent deployment at scale is straightforward through MSI/EXE packages, and you can scope policies per site or device type. For MSPs managing diverse client environments, the Datto RMM agent is a genuine strength.
Datto RMM Monitoring and Alerting. Device health monitoring, SNMP for network gear, custom component monitors, and threshold-based alerts. The component monitor framework is flexible – you can build monitors for nearly anything (disk space, service status, event logs, registry values, custom scripts). The downside: it takes real investment to set up properly. Out-of-the-box monitors are basic. The power is there, but you'll need a senior tech to build the monitoring library your MSP needs.
Datto RMM Patch Management. Windows patching works well – approval policies, scheduling, compliance reporting, and decent visibility into patch status across your client base. Third-party patching exists but is limited compared to NinjaOne's catalog of 6,000+ applications. If your clients run a lot of non-Microsoft software, you'll end up supplementing Datto's patching with scripts or a third-party tool.
Remote Access. Splashtop is built in for remote control. There's also a web remote option for quick connections without installing a viewer. Both work, though Splashtop quality can vary on low-bandwidth connections. No native support for remote access on Linux or Mac from the console – a gap that competitors have closed.
Datto RMM Scripting and Automation. PowerShell, batch, and shell scripting with the ability to deploy scripts as jobs across sites or device groups. The ComStore offers community-contributed scripts and components, though quality varies wildly – some are production-ready, many aren't. The automation engine (component monitors triggering automated responses) is powerful once you invest the time to build it out. This is Datto RMM's technical ceiling – MSPs who master the scripting layer get serious value from the platform.
Datto RMM API. REST API for integrations, custom reporting, and workflow automation. The API documentation is functional but not exceptional. MSPs using it for custom dashboards or integration with ticketing tools report it works but requires development effort.
Network Discovery. Auto-discovers devices on client networks. Useful for audits and catching unmanaged endpoints. However, multiple MSPs report inconsistency – missed devices, inaccurate OS detection, and the need for manual cleanup after scans.
Reporting. Built-in reports cover the basics (patch compliance, device inventory, alerts). Custom reporting is limited. Most MSPs running Datto RMM supplement with third-party reporting tools or export data via the API.
Datto RMM Pricing: What It Costs
Datto doesn't publish pricing publicly – you need to get a quote. Based on community data and MSP feedback, here's the typical range:
Per-endpoint pricing: $2.50–$4.50 per endpoint per month, depending on volume and contract length. Higher endpoint counts and longer commitments get lower per-unit pricing.
Contract terms: 1-year, 3-year, or 5-year contracts. No month-to-month option. This is the single biggest complaint in every Datto RMM pricing discussion. Contracts are rigid – if you lose a client and your endpoint count drops, you're still paying for the committed volume.
The High Watermark problem (changing). Historically, Kaseya billed on your peak endpoint count, not your current one. In 2025, Kaseya announced it's ending the High Watermark model for Datto RMM and transitioning to a Committed Minimum Quantity and Variable Consumption model by mid-2026. This is a step forward, but the details matter – "committed minimum" still means you're locked into a floor.
Bundling. Kaseya pushes bundling Datto RMM with Autotask PSA, IT Glue, and Datto BCDR. Bundles reduce per-tool cost but increase your total vendor commitment and make switching harder. That's the point.
Pricing Comparison: Datto RMM vs. Market
| Datto RMM | NinjaOne | ConnectWise Automate | TacticalRMM | |
|---|---|---|---|---|
| Per-endpoint/month | $2.50–$4.50 | Not published (est. $3–$5) | Not published (est. $2–$6) | Free |
| Minimum contract | 1 year | None (month-to-month) | 1 year | None |
| Public pricing | No | No | No | Yes (free) |
| Setup/onboarding fee | Varies | Free | Varies | Self-service |
| Bundling discounts | Yes (Autotask, IT Glue, BCDR) | Limited | Yes (ConnectWise stack) | N/A |
| Cost for 500 endpoints | ~$1,250–$2,250/mo | ~$1,500–$2,500/mo | ~$1,000–$3,000/mo | $0 + hosting |
| Cost for 2,000 endpoints | ~$5,000–$9,000/mo | ~$6,000–$10,000/mo | ~$4,000–$12,000/mo | $0 + hosting |
Estimates based on community-reported pricing. Actual quotes vary by negotiation, volume, and contract length.
Datto RMM cost in context: NinjaOne offers month-to-month terms with no contract lock-in. ConnectWise Automate requires contracts but offers more granular pricing tiers. TacticalRMM is free and self-hosted. The per-endpoint cost of Datto RMM isn't unreasonable for what you get – the issue is the contract structure, not the sticker price. For a full pricing breakdown across models, see our guide on the cost of IT support for small business.
The Kaseya Factor: What Changed
Kaseya acquired Datto in 2022 with promises of lower prices and increased innovation. Here's what MSPs have seen since:
Pricing pressure. Initial 10% price reductions were announced at acquisition. In practice, many MSPs report that renewal pricing has crept back up, particularly when bundling is involved. The "savings" often come with longer contract commitments.
Contract rigidity. Multi-year contracts with High Watermark billing became the norm. The 2025 announcement to move away from High Watermark is positive, but MSPs are waiting to see the actual terms.
Support quality. Multiple MSPs report a decline in Datto support quality post-acquisition. Longer response times, less knowledgeable first-tier support, and more escalation hoops. This is consistent with the pattern seen in previous Kaseya acquisitions.
Autotask integration tightened. Autotask PSA became the default recommended PSA for Datto RMM users. The integration is strong – ticket creation from alerts, device syncing, billing automation. If you're not on Autotask, the integration story is weaker.
Pre- vs. Post-Acquisition: What Changed
| Factor | Pre-Kaseya (before 2022) | Post-Kaseya (2022–2026) |
|---|---|---|
| Contract terms | 1-year standard, flexible | 1–5 year, rigid minimums |
| Billing model | Straightforward per-endpoint | High Watermark (transitioning mid-2026) |
| Pricing trend | Stable, competitive | Upward pressure at renewal |
| Support quality | Responsive, knowledgeable | Slower, more tier-one gatekeeping |
| PSA integration | Autotask (standalone company) | Autotask (Kaseya-owned, bundling pushed) |
| Innovation pace | Steady feature releases | Mixed – some AI/automation, some stagnation |
| Vendor independence | Datto-only ecosystem | Full Kaseya ecosystem dependency |
r/msp sentiment. The MSP subreddit's reaction to the acquisition was overwhelmingly negative at announcement. Three years in, it's more nuanced – some MSPs have stayed and found the platform stable, others have migrated to NinjaOne or ConnectWise Automate. The thread titled "An open letter to Kaseya" consisting entirely of ":(" comments remains a defining moment in MSP community sentiment.
What Datto RMM Does Well
Credit where it's earned:
-
Agent stability. The Datto RMM agent is one of the most reliable in the market. It doesn't crash endpoints, handles updates cleanly, and maintains a consistent connection. For MSPs managing thousands of devices, agent reliability isn't a feature – it's a requirement.
-
Automation depth. The component monitor and scripting framework gives advanced MSPs serious automation capability. If you invest the time to build out custom monitors, automated remediation scripts, and policy-driven responses, Datto RMM can handle complex environments with minimal manual intervention.
-
Autotask integration. For MSPs running Autotask PSA, the bidirectional integration is the tightest in the market. Alert-to-ticket workflows, device syncing, contract-based billing – it works without duct tape.
-
Windows patching. Patch approval policies, scheduling, and compliance reporting are solid. For Windows-heavy environments, patch management is a strength.
-
Scale. Datto RMM handles large endpoint counts well. MSPs with 2,000–10,000+ endpoints report consistent performance. The platform was built for scale, and it shows.
Where Datto RMM Falls Short
The honest gaps:
-
Contract lock-in. Multi-year commitments with limited flexibility to downsize. If your business changes, your contract doesn't change with it. This is the number-one reason MSPs consider switching.
-
Pricing opacity. No public pricing makes comparison shopping harder. You can't evaluate Datto RMM cost without engaging sales – which puts you in a negotiation before you've even decided if it's the right tool.
-
UI/UX. Functional but dated. The interface works, but it's not intuitive for new technicians. The learning curve is steeper than NinjaOne and requires more training time for new hires. In a market where MSPs struggle to hire and retain techs, UI friction is a real cost.
-
ComStore quality. The community script store (ComStore) was supposed to be a differentiator. In practice, many scripts are outdated, poorly documented, or broken. MSPs end up writing their own anyway.
-
Reporting. Built-in reporting covers basics but lacks depth. Most MSPs need third-party tools (BrightGauge, now also Kaseya-owned) for client-facing reports. That's an additional cost.
-
Third-party patching. Limited compared to NinjaOne's 6,000+ app catalog. If you manage environments with diverse software stacks, you'll need to supplement.
-
Post-acquisition support. Support quality has declined according to consistent MSP feedback since the Kaseya acquisition. Longer wait times, more tier-one runaround, less hands-on help.
Datto RMM vs. Alternatives
Here's how Datto RMM compares to the tools MSPs are most often evaluating against it:
| Datto RMM | NinjaOne | ConnectWise Automate | TacticalRMM | |
|---|---|---|---|---|
| Pricing | $2.50–$4.50/endpoint | Not published, per-endpoint | Not published, per-endpoint | Free (self-hosted) |
| Contract | 1–5 years required | Month-to-month | 1–3 years | None |
| Patch mgmt | Windows + limited 3rd party | Windows + 6,000+ 3rd party apps | Deep customization | Basic, community-driven |
| Remote access | Splashtop (Windows-focused) | Built-in (Win/Mac/Linux) | ConnectWise Control | MeshCentral |
| Scripting | PowerShell, batch, shell | PowerShell, batch, shell | Powerful, complex syntax | Full shell access |
| UI/UX | Functional, dated | Modern, clean | Complex, steep curve | Technical, no-frills |
| PSA integration | Autotask (native, tight) | Multiple via API | ConnectWise Manage (native) | None built-in |
| Best fit | Autotask shops, 500+ endpoints | Growing MSPs, flexibility-first | Large MSPs, deep customization | Technical MSPs, cost-first |
For a comprehensive comparison of all RMM options, see our complete RMM tools guide.
Should You Stay on Datto RMM or Switch?
Decision Matrix
| Your Situation | Recommendation | Why |
|---|---|---|
| Deep in Autotask, 500+ endpoints, contract is fine | Stay | Migration cost outweighs benefit; integration is strong |
| Renewal coming, unhappy with pricing | Evaluate | Get quotes from NinjaOne and ConnectWise before signing |
| Under 200 endpoints, contract minimums hurt | Switch | You're overpaying relative to your scale |
| Techs frustrated with UI, hiring is hard | Switch | NinjaOne's UI reduces training time for new hires |
| Need strong Mac/Linux support | Switch | Datto's cross-platform remote access lags competitors |
| Want to reduce Kaseya dependency | Evaluate | Map your stack first, plan a phased transition |
| Happy with performance, no contract complaints | Stay | Don't fix what works |
Stay if: You're deep in the Autotask ecosystem, your contract terms are acceptable, you have 500+ endpoints, and your techs have built out the automation layer. The switching cost (migration, retraining, rebuilding automations) is real, and the platform is stable.
Evaluate alternatives if: Your contract renewal is approaching, you're frustrated with pricing trends, you want month-to-month flexibility, or your techs are spending too much time fighting the UI instead of working in it.
Switch if: You're a smaller MSP being priced out by contract minimums, you need strong cross-platform support (Mac/Linux), or you've decided to reduce vendor dependency on the Kaseya ecosystem. The tools exist to replace Datto RMM at equal or better capability – the question is whether the migration pain is worth the long-term gain.
Compare your current stack to map out what a transition would look like.
FAQs
What is Datto RMM?
Datto RMM is a cloud-hosted Remote Monitoring and Management platform built for MSPs. It provides endpoint monitoring, patch management, scripting, remote access, and alerting through a centralized dashboard. It's now owned by Kaseya.
How much does Datto RMM cost per endpoint?
Typical pricing ranges from $2.50–$4.50 per endpoint per month, depending on volume and contract length. Pricing isn't public – you need a quote. Bundling with Autotask, IT Glue, or Datto BCDR can lower the per-tool price but increases your total commitment.
Is Datto RMM owned by Kaseya?
Yes. Kaseya acquired Datto in June 2022 for $6.2 billion. Datto RMM is now part of the Kaseya product portfolio alongside VSA, Autotask PSA, IT Glue, and Datto BCDR.
Is Datto RMM spyware?
No. Datto RMM is a legitimate enterprise RMM tool used by MSPs to manage client endpoints. It includes remote access and monitoring capabilities, which is its purpose. It does have a privacy mode setting that controls visibility. If you see the Datto RMM agent on a personal device, it was installed by an IT administrator or MSP managing that device.
What is the Datto RMM agent?
The Datto RMM agent is a lightweight software client installed on managed endpoints (Windows, Mac, Linux). It maintains a persistent connection to the Datto RMM cloud, enabling monitoring, alerting, patching, scripting, and remote access. The agent is known for stability and low resource usage.
Can I use Datto RMM without Autotask?
Yes. Datto RMM works as a standalone RMM without Autotask PSA. However, the deepest integration is with Autotask, and Kaseya's pricing often incentivizes bundling. If you use a different PSA (ConnectWise Manage, HaloPSA, Syncro), the integration will be via API rather than native.
What are the best Datto RMM alternatives?
The most common alternatives MSPs evaluate are NinjaOne (modern UI, month-to-month, strong patching), ConnectWise Automate (powerful but complex, deep ConnectWise ecosystem), and TacticalRMM (open-source, free, self-hosted). The right alternative depends on your PSA, endpoint count, budget, and how much migration effort you can absorb.
The Bottom Line
Datto RMM is a capable RMM with real strengths in agent reliability, automation depth, and Autotask integration. For established MSPs deep in the Kaseya ecosystem with 500+ endpoints, it's a defensible choice.
But the economics have shifted. Contract lock-in, pricing opacity, and post-acquisition support decline are real factors that didn't exist five years ago. If your renewal is approaching, it's worth running the numbers on alternatives – not because Datto RMM is broken, but because the market has moved and your options are better than they were.
The best RMM is the one that fits your stack, your budget, and your growth plan. Not the one your current contract says you're stuck with.
For more from MSPs navigating these exact decisions, join the OpenMSP community.
Kristina Shkriabina
Our flock's megaphone – once a correspondent for Ukraine's Public Broadcasting Company, now the one making sure Flamingo and OpenMSP sound exactly like what they are: direct, useful, and built for MSPs. She runs content and community, writes about stack decisions and marketing strategy.
