Back to blog

Autotask Pricing in 2026: What MSPs Actually Pay

6 min read

Autotask pricing is one of those things every MSP wants to know and nobody can get a straight answer on. The product has gone through enough name changes — Autotask, Datto PSA, now technically part of Kaseya’s IT Complete suite — that even figuring out what to search for is confusing. The pricing page on Kaseya’s site? It says “contact sales.”

Here’s what MSPs actually report paying, what the bundle economics look like, and why the automation gap matters more than the line item on your PSA invoice.

A note upfront: the numbers in this piece come from MSP community discussions, peer groups, published reviews, and direct conversations. Kaseya does not publicly disclose Autotask pricing, and your actual rate will depend on your endpoint count, contract length, and negotiation. Treat these as directional estimates.

What Autotask Costs: The Known Numbers

Autotask — now officially Datto PSA — uses per-user pricing. Each technician seat carries a monthly cost. Based on community reports from MSPs currently on the platform:

Per-user rates typically fall in the $110-$175/user/month range. The spread depends on which IT Complete bundle you’re on, how many endpoints you manage, and when you last negotiated.

For a 15-person MSP with 10 technician seats, that’s roughly $1,100-$1,750/month just for the PSA. Not unreasonable on its own — until you factor in the rest.

The Bundle Factor

Here’s where autotask pricing gets complicated. Kaseya increasingly packages Autotask inside IT Complete bundles rather than selling it standalone. That means you might be buying Autotask alongside Kaseya VSA, IT Glue, Datto RMM, Datto Networking, and other products in the portfolio.

The bundled per-endpoint pricing MSPs report ranges from $3-$6/endpoint/month depending on which products are included and your total endpoint count. For a 3,000-endpoint MSP, that’s $9,000-$18,000/month for the full bundle.

If you only want the PSA, you may still be able to negotiate a standalone agreement, but Kaseya’s sales motion pushes toward bundles. Some MSPs report being told standalone Autotask isn’t available for new customers — though this varies by region and sales team.

Implementation and Migration Costs

If you’re moving to Autotask from another PSA, budget for implementation. Kaseya offers professional services for data migration and setup, and third-party Autotask consultants are common. Reported costs:

  • Self-guided implementation: $0 in fees, but 80-200 hours of internal time over 2-4 months
  • Kaseya professional services: $5,000-$15,000 depending on complexity
  • Third-party consultants: $150-$250/hour, with full implementations running $10,000-$25,000

These are one-time costs, but they’re real. An MSP spending $15,000 on implementation plus $15,000/month on a bundle is looking at $195,000 in year-one costs before they’ve automated a single ticket.

The Contract Trap

The detail that matters most in autotask pricing isn’t the per-user rate. It’s the contract structure.

Kaseya typically requires three-year agreements. These contracts include auto-renewal clauses with narrow opt-out windows — often 60-90 days before the renewal date. Miss that window and you’re locked in for another three years at whatever the new rate is.

MSPs in community forums report price increases of 15-40% at renewal, applied to the new three-year term. If you’re on a $12,000/month bundle and it goes up 25% at renewal, you just committed to $15,000/month for 36 months — $540,000 total — because you missed a cancellation deadline.

Read the contract. Calendar the opt-out date. Negotiate renewal terms into the original agreement if possible. This isn’t unique to Kaseya, but the three-year lock-in and aggressive renewal increases make it higher-stakes than most vendor agreements.

What You Get for the Money

To be fair, Autotask is a capable PSA. What you get:

  • Ticketing and service desk: Mature, customizable, with workflow rules and SLA management
  • Project management: Built-in project tracking tied to contracts and billing
  • CRM and sales pipeline: Basic but functional for MSP sales workflows
  • Time tracking and billing: Tight integration between ticket time entries and invoicing
  • Reporting: Solid reporting engine, though building custom reports has a learning curve
  • API: Well-documented REST API that most MSP tools integrate with

For MSPs who’ve been on Autotask for years, the platform does its job. The frustrations aren’t usually about what Autotask does — they’re about what it costs relative to alternatives and what it doesn’t do.

What Autotask Doesn’t Include

No PSA includes this, so it’s not a knock on Autotask specifically. But it’s the gap that matters most for your actual operating costs:

Autotask doesn’t triage tickets. A ticket lands in the queue. A human reads it, figures out what it’s about, checks the RMM for device status, opens IT Glue for documentation, maybe checks M365 admin for the user’s account state. That takes 8-15 minutes per ticket. Multiply by 50-100 tickets per day and you’re burning hours on context-gathering before resolution even starts.

Autotask doesn’t match tickets to runbooks. You might have a documented process for password resets, printer issues, VPN failures, and new user setups. Those runbooks live in IT Glue or a wiki. Autotask doesn’t know they exist. Your L1 tech has to remember which runbook applies, find it, and follow it — or not.

Autotask doesn’t pull cross-tool context. When a user submits a ticket saying “my email isn’t working,” the tech needs to check M365 for mailbox status, the RMM for device connectivity, and maybe Active Directory for account lockouts. Autotask holds the ticket. The context lives everywhere else.

These gaps exist regardless of which PSA you run. They’re the actual cost center — not the subscription line item.

Autotask vs. the Alternatives

A quick comparison on pricing alone:

PSAPricing ModelTypical RangeContract
Autotask (Datto PSA)Per-user or bundled per-endpoint$110-$175/user/month3-year typical
ConnectWise ManagePer-user$90-$150/user/month1-3 year
Halo PSAPer-user$89-$129/user/monthMonthly or annual
SuperOpsPer-tech (PSA+RMM)$79-$129/tech/monthMonthly or annual
SyncroPer-tech (PSA+RMM)$139-$189/tech/monthMonthly

The per-user rates are comparable across the board. The real differences are in contract flexibility, bundling requirements, and the total ecosystem cost. Halo and SuperOps offer shorter commitments. ConnectWise has a deeper integration ecosystem. Syncro includes RMM in the price.

None of them solve the triage and automation gap.

Where Junto Fits

Junto doesn’t replace Autotask. It connects to it.

When a ticket hits Autotask, Junto’s AI reads it, pulls context from your RMM, documentation platform, and M365 environment, matches it against your configured runbooks, and either resolves it automatically or delivers a fully enriched ticket to your tech with the diagnosis and next steps already attached.

The pricing is per-technician, flat monthly, regardless of endpoint count. No three-year lock-in. No bundles you didn’t ask for. Adding clients doesn’t change your bill — it just means more tickets the AI handles.

For MSPs on Autotask who are frustrated with costs, the instinct is to switch PSAs. That’s a 3-6 month project with $10,000-$30,000 in migration costs and months of reduced productivity. And at the end, you have a different PSA with the same triage gap.

The higher-ROI move for most MSPs is keeping the PSA that’s already configured and adding the AI layer that actually reduces your per-ticket cost.

Making the Decision

If you’re evaluating autotask pricing at renewal, you have three options:

  1. Renegotiate. Push back on the increase. Ask for a shorter term. Get competitive quotes and use them as leverage. Kaseya’s sales teams have room to move, especially if you’re willing to walk.

  2. Migrate. If the total cost and contract terms are genuinely unworkable, pick a PSA with better terms and budget 3-6 months for the transition. Go in with realistic expectations about the disruption.

  3. Stay and upgrade. Keep Autotask. Layer Junto on top. Reduce your per-ticket labor cost by automating triage and runbook execution. The savings on technician time often exceed the PSA subscription itself.

Options 1 and 3 aren’t mutually exclusive. Negotiate your renewal and add an AI layer. You’ll spend less and get more from the stack you already know.


Want to see what Junto does on top of Autotask — without migrating anything? Book a demo and we’ll run it on your real ticket queue.

See Junto in action

15-minute demo. We'll show you AI triage working on your actual tickets.

Book a Demo