Kaseya alternative
Switching from Kaseya to Command
For MSPs running Datto RMM or VSA, Autotask PSA, and IT Glue. See where each job lives in Command, what changes on the bill, and how to move one batch of clients at a time.
- $6 per endpointEDR and DNS filtering included
- Month-to-monthNo long-term contract
- Unlimited techniciansTechnicians are not billed
- No onboarding feeGuided onboarding is free
Kaseya facts on this page come from Kaseya’s own public websites, as of November 2026. Each one links to its source.
Where your Kaseya work lives in Command
This maps each job to the part of Command that does it. It is not a feature-for-feature parity list: some things work differently, and the last column says what to check before a client moves.
| In your Kaseya stack | Where it lives in Command | Check before you move |
|---|---|---|
| Datto RMM or Kaseya VSARemote monitoring and management | Overwatch (RMM)Endpoint monitoring and fleet health, jobs and automation, application management, patch management and compliance, and remote control with live response. Policies set monitoring, patching, and Windows hardening globally or per client, site, or device group. | List the scripts, monitors, and patch rules you rely on. Each needs a Command equivalent before that client moves. Windows is fully supported; macOS and Linux agents have fewer capabilities. |
| Autotask PSATickets, projects, and service delivery | Service Desk, Project Management, and OperationsTickets, todos, knowledge base, and a shared calendar, with Service Desk and SOC queues on one board. Projects and change requests stay separate from tickets. Procurement and order tracking live in Operations. | Command has no staff billing module, so keep invoicing in your accounting system. If your invoices come from your PSA today, decide where that work goes before you move. |
| IT GlueIT documentation and passwords | Documentation and the credential vaultKnowledge base, assets, locations, and contacts, with version history, restore, and role-based read and edit. Passwords sit in a separate vault with its own permission, a separate encryption key for each client, one-time share links, and expiring-credential alerts. | Move passwords into the vault, not into documents, and decide who gets the vault permission. Password reveals are logged with who revealed them and for which client. |
| Your EDR and DNS filteringWhichever vendor provides it today | Aegis: Sentry EDR and Web ProtectionEndpoint protection and DNS filtering, included in the $6 per endpoint price. Both run on the same policy engine as the rest of Command, and their detections land in Response Ops. | Switch security one batch of clients at a time. In the pilot, check how Sentry EDR runs alongside your current endpoint security before you remove it. |
Also in the same plan
- Microsoft 365 management and cloud alerts
- Response Ops with approval-gated playbooks
- Client portfolio posture and secure score
- Bring your own AI provider: Anthropic (Claude), OpenAI, Google, or a self-hosted model
Left where it is
Kaseya’s platform page also lists Cyber Resilience products (Datto BCDR, Unitrends, Datto Backup for Azure, Datto SaaS Protection) and Connected Security products (INKY, SaaS Alerts, vPenTest). Backup is not part of Command, and this page does not map those security products. Keep them running: nothing in this plan requires turning them off.
Source: kaseya.com/platform, as of November 2026.
What changes on the bill
Command is one plan at $6 per managed endpoint per month, with Sentry EDR and Web Protection (DNS filtering) included. Here are its terms next to the two Kaseya plans we found with a published price, as of November 2026.
| Command | IT Glue | Kaseya 365 Ops | |
|---|---|---|---|
| Published price | $6 per managed endpoint per month, everything included | $29, $38, or $44 per user per month (Basic, Select, Enterprise) | “$129 per user per month” |
| Minimum | 50 endpoints on paid plans ($300 a month); none for the pilot | 5 users | 3 licenses |
| Term | Month-to-month; 10% off with annual prepay | 36 months | 1 year, with renewal increases capped at 5% plus CPI |
| Onboarding fee | None | One-time fee that “cannot be waived” | Not covered in our review |
| How you start | Free 30-day pilot on up to 50 endpoints, for MSPs accepted into the beta | No trial listed | Demo request; no free trial on the kaseya.com pages we checked |
The prices use different units (per endpoint, per user) and cover different products, so compare the terms here, not the totals.
Sources: itglue.com/pricing, Kaseya 365 Ops page, and kaseya.com, as of November 2026.
The cost of moving
- Up to 3 months of Command free while your existing contracts run out
- No onboarding fee
- Migration help from Datto RMM, VSA, and IT Glue
- Free guided onboarding and product walkthrough
- Unlimited technicians
Other Kaseya products
kaseya.com is demo-led: “Get a demo” is its main call to action, and kaseya.com/pricing/ does not exist. Of the kaseya.com pages checked, only Kaseya 365 Ops lists a price. IT Glue publishes its plans on itglue.com.
Sources: kaseya.com and Kaseya 365 Ops page, as of November 2026.
The VSA page’s FAQ says pricing depends on deployment model, devices, packaging, and capabilities, and sends buyers to a pricing request.
Source: Kaseya VSA page, as of November 2026.
datto.com has a Datto RMM trial request page.
Source: Datto RMM trial page, as of November 2026.
A move you can make one batch at a time
Migration help from Datto RMM, VSA, and IT Glue is included, along with free guided onboarding and product walkthrough. IT Glue documentation and passwords import directly; endpoints move by installing the Command agent. Ask in your demo exactly what migration help covers for the rest of your stack. Each phase below ends with a check you can see for yourself.
Phase 1: Take stock
Before anything is installed, write down what the move has to carry, client by client.
- Endpoints per client, and how many run Windows, macOS, or Linux
- The scripts, monitors, and patch rules your team uses every week
- Ticket queues and the PSA workflows you depend on, including billing
- Documentation and passwords for each client
- Each contract’s end date and notice period
Done when: You have one list per client and know which contract ends first.
Phase 2: Pilot on your own machines
Apply for the beta. MSPs accepted get a free 30-day pilot on up to 50 endpoints, with guided onboarding and a walkthrough of how Command works.
- Install the Command agent on your own staff machines, not a client’s
- Set up monitoring, patching, and Windows hardening policies at global scope
- Work your internal tickets in Service Desk and move your own documentation and passwords
Done when: Your team gets through a normal day on your own machines in Command.
Phase 3: Run side by side
Bring in one or two clients you know well and keep their current tools running while you compare.
- Deploy Command to those clients’ machines while the current tools stay in place
- Compare Command’s alerts and patch status with what your current RMM reports
- Pick one switch-over date for patching, so two tools never patch the same machine
Done when: Command’s view of those clients matches what you expect, and your technicians trust it.
Phase 4: Move clients in batches
Move the rest of your clients a few at a time, in the order your contract dates and workload allow.
- Deploy the agent and apply your policies; client, site, and group settings build on the global ones
- Import each client’s documentation and passwords from IT Glue (or Hudu, or CSV), then check who gets the vault permission
- Point the client’s ticket intake at Service Desk
- Switch that batch’s endpoint security to Sentry EDR and Web Protection
Done when: Every moved client is worked in Command, and nothing new happens in the old tools.
Phase 5: Retire the old tools
Turn off the old stack only after each batch is stable.
- Remove the old RMM agent, and any endpoint security that Sentry EDR replaced, from machines that have moved. Leave backup agents in place.
- Export the records you need to keep before access to the old tools ends
- Give notice in time, so each contract ends on its date instead of renewing
Done when: No moved machine runs an old RMM agent, and no contract renews by accident.
Is Command the right move for you?
A move only pays off if Command fits how you work. Here is when it does, and when it does not yet.
A good fit if
- Most of the machines you manage run Windows
- You want EDR and DNS filtering in the per-endpoint price
- You would rather pay month-to-month than sign a multi-year term
- You want documentation and a credential vault in the same console as tickets and endpoints
- You are happy to pilot on your own machines first and give feedback during the beta
Not the right fit today if
- You want backup and disaster recovery from the same vendor: backup is not part of Command
- You need invoicing inside your PSA: Command has no staff billing module
- Much of your fleet runs macOS or Linux: those agents have fewer capabilities than Windows
- You need a generally available product today: Command is in beta
Want the detail first? Read how the credential vault and client boundaries work and what the AI does and does not do.
Questions about switching
Can Command import our data from Datto RMM, VSA, IT Glue, or Autotask?
IT Glue, yes: Documentation’s Import data screen brings configurations and passwords across through the IT Glue API, and can keep a scheduled sync running while you move. Hudu works the same way, and CSV files import with a dry run first. Datto RMM and VSA have no importer: endpoints move by installing the Command agent. For Autotask, ask us in the demo. The plan includes migration help from Datto RMM, VSA, and IT Glue.
Will we pay for Command and Kaseya at the same time?
Only if a contract runs longer than the credit. While your existing contracts run out, you get up to 3 months of Command free; after that, you pay for both until each contract ends. Check each contract’s end date and notice period before you plan your batches.
Can we stop partway through the move?
Yes. Command is month-to-month and clients move in batches, so you can pause after any batch while the clients you have not moved stay on their current tools.
Are EDR and DNS filtering extra?
No. Sentry EDR and Web Protection (DNS filtering) are included in the $6 per endpoint price, along with every other module.
Does Command support macOS and Linux?
Windows is fully supported. macOS and Linux agents are available with fewer capabilities, so test the pilot against the Macs and Linux machines you manage.
Is Command generally available?
Not yet. Command is in beta, with limited early-access spots for MSPs. MSPs accepted into the beta get the free 30-day pilot, then 40% off ($3.60 per endpoint) for 12 months with the rate locked, in exchange for regular feedback and, if it works for you, a case study.
Plan your move off Kaseya
Bring your client list and contract dates to a demo. We will show you where your work lives in Command and what a 30-day pilot on your own machines looks like.