Kaseya CMQ Billing: What Your Next Datto and Autotask Bill Looks Like

Your December Kaseya invoice reads differently than your November one, and the line that changed decides your margin for the next year. In late 2025 Kaseya retired High Watermark pricing on Datto RMM, Autotask PSA, and SaaS Protection and moved them to Committed Minimum Quantity billing, or CMQ. It's a real change, not a relabel. For a shrinking fleet it can be cheaper, and for a growing one it quietly sets a new floor under the bill. This post breaks down how kaseya cmq billing works, shows what your next invoice looks like with worked numbers, and lays out the stay-versus-leave math so you can make the call with your own endpoint counts in front of you.

TL;DR

What Changed: From High Watermark To Committed Minimum

For years the loudest complaint about Datto RMM pricing on r/msp was High Watermark billing. The model charged you for the highest endpoint count you hit during your term, and it never came back down. Onboard a big client in March, hit 500 endpoints, then lose them in June and drop to 400, and your bill still read 500 for the rest of the contract. You paid for devices you no longer managed.

Kaseya ended that. Effective November 2025 and showing up on invoices after December 1, 2025, Datto RMM, Autotask PSA, and SaaS Protection moved to Committed Minimum Quantity plus Variable Consumption. Kaseya has signaled the rest of its portfolio, including the tools behind Kaseya VSA pricing, will follow by the end of June 2026. So if you run anything in the Kaseya 365 or IT Complete bundle, this reaches you eventually even if your December bill looked normal.

The headline is genuinely good news for anyone whose fleet moves around. Seasonal churn, a lost client, a client that offboards a department, all of it can now pull your usage back down instead of freezing it at your worst month. That's the part Kaseya's own announcement leads with, and it's fair.

The part worth reading twice is the word "minimum."

How Kaseya CMQ Billing Works

Under CMQ, your monthly charge is simple to state: you pay for the greater of your Committed Minimum Quantity or your calculated license usage for that period. Whichever number is bigger wins.

From December 1, 2025 onward, Kaseya calculates that usage from your license count at midnight UTC on the last day of the previous month. The vendor's own worked example is clean: if your Committed Minimum Quantity is 200 licenses and you're using 205 on November 30, your bill is for 205. Usage beat the floor, so you pay for usage.

Now flip it. Same 200 committed, but a client offboards and you drop to 190 real endpoints. You still pay for 200. The floor held. Variable licenses you added above the commitment can be reduced in a later billing period, but they can never pull the total below your CMQ. On a standard one-year term, that commitment is fixed for the year while the variable piece floats up and down on top of it.

One detail hides in that snapshot date. Because usage is read at midnight UTC on the last day of the month, the exact timing of onboarding and offboarding lands you on one side of a billing period or the other. Decommission a departing client's endpoints on the 29th and they're gone from the count. Let the cleanup slip to the 2nd and you carry them for a full extra month. Under High Watermark that timing never mattered, since the number only ratcheted upward and stayed there. Under CMQ, tight month-end hygiene is worth a recurring calendar reminder for whoever runs your billing.

So the mechanic has two moving parts and one anchor. The variable consumption is the flexible layer that finally lets a bill shrink. The committed minimum is the anchor, and you set its weight the day you sign. Set it low and you keep flexibility. Set it high, chasing a volume discount on kaseya pricing, and you've built yourself a new watermark by hand.

What Your Next Bill Looks Like

Numbers make this concrete. The scenarios below use round endpoint counts to show the shape of the change, not a Datto RMM price list, since per-endpoint rates vary by contract and aren't published.

Take an MSP that peaked at 500 managed endpoints last spring, then settled at 420 after a client left.

Under High Watermark, that MSP paid for 500 endpoints every month for the rest of the term, including the months it managed 420. Eighty phantom endpoints on every invoice.

Under CMQ with a committed minimum of 400, the same MSP using 420 pays for 420 this month. Drop to 410 next month and the bill follows to 410. Drop to 395 and it stops at the 400 floor. Across a slow quarter, that's real money back compared to the old model.

Now the trap. Picture an MSP mid-growth pitch that commits to 600 licenses at signing to lock a better rate, then loses an anchor client and runs at 450 actual endpoints. That MSP pays for 600. The variable layer can't rescue it, because 450 is below the commitment. It's High Watermark behavior again, except this time the MSP chose the watermark itself at the negotiating table.

The same logic runs through Autotask pricing. Autotask PSA is licensed per technician, and mid-market shops running 10 to 25 techs report roughly $85 to $130 per technician per month for the PSA module alone, before Datto RMM endpoints, IT Glue, or add-ons. Commit to 20 seats to hit a tier, then trim to 15 techs in a lean year, and you're paying for five empty chairs every month. Autotask psa pricing rewards you for guessing your headcount low and growing into it, not for padding the commitment.

SaaS Protection moved to CMQ too, and it bills the same way per protected seat for Microsoft 365 and Google Workspace backup. The trap is identical. License count tends to drift as clients hire and churn, so a committed minimum set during a client's headcount peak keeps charging after the layoffs land. Reconcile protected seats against active mailboxes before you set that floor, because backup licenses for departed users are the quietest line item on any Kaseya billing statement. That single reconciliation has clawed back seats for MSPs who assumed the count still matched their client's real headcount.

Here's how the three models compare on the things that decide your margin.

Where The Room To Negotiate Moved

CMQ doesn't remove the negotiation. It moves it earlier and makes one number matter more than any other: the commitment you sign.

Under the old model, the fight was about rate and term length. Under CMQ, the rate still matters, but the committed minimum is where a bad signature costs you for twelve months. r/msp threads on the change keep landing on the same advice, and it's sound: commit to your floor, not your ceiling. Your CMQ should reflect the endpoint count you're confident you'll hold through the worst month of the term, not the number you hope to reach.

A few things worth pushing on before you sign a Kaseya renewal:

• Set the committed minimum at your realistic low, then let variable consumption carry the growth. Overshooting the commit is the one mistake CMQ can't undo mid-term.
• Ask, in writing, how mid-term additions are treated and when they can roll back off. Variable is only useful if you know the rules for reducing it.
• Price the whole bundle, not the line item. A softer Datto RMM number means little if Autotask, IT Glue, and SaaS Protection commitments climb to cover it.

If your renewal quote already came back with a double-digit kaseya price increase, the commitment conversation is where you claw some of it back. And if the rep won't move on the floor, that's useful information too, because it tells you what leaving would save. For a full walkthrough of what to push on at the table, the best Kaseya alternative breakdown covers the renewal levers vendor by vendor.

The Zero-Commitment Stack: TacticalRMM Plus ITFlow

The reason CMQ math stings is the commitment itself. So it's worth knowing what zero commitment looks like, because a growing share of MSPs weighing a datto rmm alternative are pricing the open source route.

TacticalRMM is a free, open source RMM. There's no per-endpoint license and no contract. You self-host it, which is the trade: there's no cloud version, so you run it on a low-cost host like Hetzner or Vultr for roughly $30 to $60 a month regardless of how many endpoints you monitor. Optional sponsorship tiers unlock a reporting module and priority support. What tactical rmm doesn't ship is a PSA, so ticketing and billing live in a separate tool.

That separate tool is usually ITFlow. ITFlow is a GPL-licensed, free open source PSA that covers ticketing, documentation, asset tracking, and client billing. Like TacticalRMM it's self-hosted, running around $20 to $60 a month on a VPS, and if you'd rather not babysit a server the project offers managed hosting through services.itflow.org while you keep the open-source application and your data. Together, itflow plus TacticalRMM form a working open source psa and RMM stack for something like $40 to $120 a month in infrastructure, flat, with nothing committed and nothing to negotiate.

The honest trade is labor. You own updates, backups, uptime, and the integration between the two tools. For a technically strong shop that wants total control and a predictable infrastructure bill, that's a fair swap. For a team already stretched thin, the hours can outweigh the license savings. That tension, control versus overhead, is the real decision under every open source rmm conversation, and the Datto alternative guide walks through where each option lands.

Where OpenFrame Fits

Between a Kaseya commitment and a pair of self-hosted open source tools sits a third option, and it's the one that answers the complaint underneath all of this: you shouldn't have to choose between vendor lock-in and running your own servers.

OpenFrame is an AI-native, all-in-one MSP and IT platform. It ships native PSA, so ticketing, documentation, and billing are included in the platform, not bolted on from a third party or left for you to wire up. RMM and endpoint management sit in the same place, and an AI agent triages and works level-one and level-two tickets instead of leaving them in a queue. Pricing is per-endpoint with no multi-year lock-in, which means no committed minimum acting as a floor and no term you're trapped inside if a client leaves.

The pitch isn't that it's the cheapest box on a spreadsheet. It's that the all-in-one design removes the exact mechanic causing the pain: you're not stacking a Datto RMM commitment, an Autotask psa pricing tier, and separate add-on contracts and then defending each one at renewal. One platform, one bill, no lock-in. That's the AI-native, no-lock-in lane, and for MSPs who want the consolidation of Kaseya without the contract behavior, it's worth a look next to any autotask alternative you're already weighing. The Autotask alternative roundup lines it up against the usual PSA names.

Stay Or Move: How To Make The Call

CMQ changes the stay-or-go decision, but it doesn't settle it. For a lot of shops, the right move in the near term is to stay and renegotiate the commitment, not rip out a working stack over a billing change that mostly helped shrinking fleets.

Here's a clean way to decide who each path fits:

1. Stay and negotiate if your fleet is stable or shrinking, your CMQ can be set at a realistic floor, and the migration cost of leaving outweighs a year of the new pricing. CMQ rewards you here.
2. Reprice the stack if your renewal came back with a real kaseya price increase, your commitment is being pushed above your comfortable low, or you're paying for empty Autotask seats. Get a zero-commitment quote and an all-in-one quote before you sign, if only to size the gap.
3. Move if you're technically equipped and want infrastructure-cost predictability (the open source route), or you want consolidation without the contract (the AI-native all-in-one route). Either one ends the annual commitment fight for good.

The math is different for every fleet, which is the whole point. High Watermark was a flat bad deal for anyone who ever lost a client. CMQ is a fairer model with one sharp edge, and that edge is a number you control. Read your December invoice, find your committed minimum, and ask one question: if this were the worst month of the year, would that floor still make sense? Whatever you decide, decide it with the number in front of you, not the one the rep hopes you'll sign for.

Kaseya finally let the bill shrink. Just don't hand back the flexibility by committing to a floor you can't stand on.