Kaseya VSA pricing in 2026: what MSPs report paying, and what the contract adds
Kaseya VSA pricing is not published: Kaseya quotes it per endpoint, and the number you are offered depends on fleet size, contract term, minimum commitment and whether VSA is sold alone or inside a Kaseya 365 or IT Complete bundle. No reliable public per-endpoint figure exists, so the useful test is your quote's effective monthly cost per endpoint across the whole term, including onboarding and minimums.
That is less satisfying than a number. It is also more honest than the figures that circulate without a source. Here is what can be checked, what cannot, and how to read a VSA quote line by line.
Why there is no Kaseya VSA price list
At the time of writing, Kaseya's VSA product pages direct you to a demo or quote request rather than a price table. That is a deliberate model, not an oversight. Quote-only pricing lets a vendor price each deal against your current tool, your growth plans and how close the sales team is to quarter end.
For you, the consequence is simple: two MSPs of the same size can pay meaningfully different amounts for the same product, and both will believe they got a fair deal. A forum figure from another shop is therefore a data point about their negotiation, not about your price.
A per-endpoint figure quoted without its term, minimum and bundle is a guess wearing a spreadsheet's clothes.
What is publicly reported, and how far to trust it
We set out to compile dated, sourced figures. The honest result is a short table, because most of what circulates does not survive the request for a source.
| Item | Public status | Where it comes from |
|---|---|---|
| Per-endpoint list price | Not published | Kaseya VSA product pages, quote request only (checked at time of writing, 2026) |
| Per-endpoint price paid | Anecdotal only | MSP owner posts on Reddit's r/msp and similar forums; figures vary widely and rarely state term or bundle |
| Contract term | Commonly reported as multi-year | Recurring theme in r/msp threads and verified-review comments; not stated as a fixed rule by Kaseya publicly |
| Auto-renewal | Frequently reported | Forum and review complaints about renewal notice windows; check the clause in your own agreement |
| Onboarding or implementation fee | Sometimes reported, inconsistently | Forum anecdotes; often waived or folded into bundles in negotiation |
| Minimum endpoint commitment | Frequently reported | Forum anecdotes and review comments |
We have deliberately left out per-endpoint numbers. We could not find a figure tied to a named, checkable source with a date and a stated term, and printing an unsourced one would make this page part of the problem it is trying to solve.
Rule of thumb: treat any VSA price you read online as a negotiating anchor, never a benchmark. The only number that matters is the one on your order form, divided correctly.
What the contract adds to the headline per-endpoint rate
The per-endpoint rate is the line the sales conversation focuses on. The contract is where the real cost lives. These are the items to find and price before you compare anything.
- Term length. A multi-year term turns a monthly price into a total liability. Multiply it out: rate times committed endpoints times months. Skip this and you are comparing a monthly figure against a three-year obligation.
- Minimum commitment. If you commit to more endpoints than you manage today, you pay for empty seats until you grow into them. Shrinkage is the bigger risk: lose a large client mid-term and the minimum does not shrink with you.
- Auto-renewal and notice windows. Find the clause, the notice period and the method of notice. Missing a window by a week can roll you into another full term. Put the date in a calendar the day you sign.
- Onboarding and implementation fees. One-off, but they belong in the total. Ask whether they are waivable; anecdotally they often are.
- Bundle scope. VSA is increasingly sold alongside other Kaseya products. A bundle can be good value if you would use every part, and expensive shelfware if you would not. List each component and whether you would buy it on its own.
- Price escalators. Check whether renewal pricing is fixed, capped, or at the vendor's then-current rate.
We cover these same traps across vendors in the add-ons, minimums and hidden fees vendors leave off the pricing page.
How to sanity-check a Kaseya VSA quote
You do not need anyone else's price to tell whether yours is reasonable. You need arithmetic and a comparison set.
- Total the term. Add every recurring charge across the full term, plus every one-off fee. This is your true contract value.
- Divide by real endpoints, not committed ones. Use the endpoints you actually manage today, and a cautious forecast for each year. This gives the effective cost per managed endpoint per month, which is the figure that hits your margin.
- Strip out what you would not use. If the bundle includes products you will leave switched off, their cost still counts. Do not let them flatter the per-endpoint rate.
- Compare against published prices. Several competitors now publish their pricing. Run the same arithmetic against them at your fleet size; our 2026 RMM pricing comparison does the legwork for the main alternatives.
- Apply the exit test. Ask what it would cost to leave in year two. If the answer is "the rest of the contract", that is part of the price.
Worked example: a quote of a given rate on a 36-month term, with a minimum 20 per cent above your current fleet, means you pay for those extra seats every month until you fill them. If your fleet stays flat, your effective rate is 1.2 times the headline rate. Do that division before you negotiate, not after.
Negotiating: where the room usually is
Because the price is quoted rather than listed, almost everything on the order form is negotiable to some degree. The levers MSPs most often report pulling are these.
- The minimum. Push it down to your actual fleet. This protects you far more than a few pence off the rate.
- Ramp schedules. Ask for the minimum to step up over the term in line with realistic growth, rather than starting at the top.
- Renewal terms. A cap on renewal increases and a shorter notice window are worth more over five years than a discount in year one.
- Onboarding fees. Ask for them to be waived. The worst answer is no.
- Bundle components. Remove what you would not use and ask for the price without it.
Timing matters too. Vendors with quarterly targets tend to be more flexible near the end of a quarter, which is a widely held view in MSP forums rather than anything Kaseya states.
Failure modes: how VSA buyers overpay
The pattern in forum complaints is consistent, and none of it is about the per-endpoint rate itself.
- Signing for growth that did not arrive. The minimum was set on the forecast, the fleet stayed flat, and the empty seats were paid for every month.
- Missing the renewal window. The term rolled over because nobody owned the notice date.
- Buying the bundle for one product. The rest sat unused while being paid for.
- Comparing monthly against multi-year. A slightly cheaper rate on a longer term felt like a saving and was not one.
If you are already inside a term and want out, our guide to leaving Kaseya VSA around a multi-year contract works backwards from the notice date.
Where this fits with Helios
Most of this article is arithmetic and contract discipline, and it applies whatever you end up buying. Helios takes the opposite approach to quote-only pricing: flat per-MSP plans at £99, £199 and £399 a month by fleet size, a £4 per device Launch tier for 5 to 25 devices, every feature on every plan and no annual lock-in. That removes the minimum, the renewal window and the bundle question from the conversation entirely. It will not suit every shop, and you should run the same sums against it as against VSA; our pricing page shows the full figures.
Helios: AI-native RMM and PSA in one platform, with Helio, an agent that investigates and fixes device issues and triages tickets. 14-day trial and no feature gating. Start free.
Read next
Why MSPs choose Helios
One platform that does the work, at a price that stays put
Helio fixes, not just flags
When an alert fires, Helio, the AI technician built into Helios, investigates it, writes the fix and runs it once you approve. It keeps what works, so the next one is quicker.
Everything in one product
RMM, a service desk with SLAs, patching including third-party apps, remote access, Microsoft 365 and Defender checks, backup monitoring, a client portal and billing into Xero or QuickBooks.
Priced by fleet, not by people
£4 a device on Launch up to 25 devices, from £20 a month, then £99, £199 or £399 a month by fleet size, with any number of technicians and every feature on every plan.
A price that stays put
Your price is locked for as long as you stay subscribed, and that is written into our terms. Monthly billing, cancel any time.
Bring your clients across
Import your clients and machines from another RMM's CSV export, then roll the Helios agent out at your own pace, with a count of how many have arrived.
14 days free, no card
The full platform from the first minute, on your own machines. No sales call, no feature held back for the trial.
See it on your own fleet
Helios is the AI-native platform for MSPs: monitoring, patching, security, Microsoft 365, backup monitoring, remote access, client billing and an AI service desk in one product, at one flat price per MSP. Contracts and logged time become invoices in Xero or QuickBooks without leaving the platform. Every feature is on every plan. 14-day free trial, card-free, set up in minutes, cancel any time.
Start freeResearched and written with Helio SEO, our AI writer for business blogs.