If you came here looking for a tier breakdown, there is not one to give you. Checked on 30 October 2026, the vendor’s own pricing URL returns a 404. That absence is the most useful fact available about Kaseya pricing, because it tells you what kind of purchase this is before you spend a week trying to compare it.
TL;DR
- There is no pricing page. Both the trailing-slash and non-slash versions of the URL return a 404, while the homepage loads normally.
- Its Datto subsidiary does have a page titled pricing, and that page carries no figure either.
- So no published number exists to compare, and any figure you find in a third-party roundup is somebody’s estimate.
- The product is sold as a bundle across a large portfolio, so the real variables are which modules and how long a commitment.
- Competitors like NinjaOne do publish a range, which gives you a reference point even if it is not a like for like one.
- Go in with a module list and a term length, because those are what actually set your number.
What is actually published
Checked directly on 30 October 2026, with a browser user agent so bot blocking was not the cause:
| URL | Result | What it means |
|---|---|---|
| The vendor pricing URL, with trailing slash | 404 | No page exists |
| The same URL without the slash | 404 | Not a redirect problem |
| The vendor homepage | 200 | The site is fine, the page is absent |
| Datto, a company in the same group | 200, zero figures | A page titled pricing that publishes no price |
That last row is the interesting one. A pricing page returning 200 with no figure on it is a different thing from no pricing page at all, and it is worth knowing the difference exists, because a status check alone would tell you the second one was fine.
Either way the conclusion is the same for a buyer. There is nothing to look up, so every figure in circulation came from a reseller quote, a review site estimate, or somebody’s renewal invoice. None of those is a list price and none of them is yours.
What Kaseya pricing actually depends on
This is a portfolio business rather than a single product. Remote monitoring, backup, documentation, professional services automation, ticketing and security tooling sit under one commercial umbrella, much of it acquired. You are not buying a plan, you are assembling a set of modules.
That structure explains the missing page better than any theory about transparency. A published tier only works when there is a tier to publish. When the thing being sold is a configuration across a dozen products, each with its own unit of measurement, there is no single number that would be true for two buyers.
It also tells you where your bargaining position sits. With bundle selling, the discount usually comes from breadth and term rather than from volume alone. Adding a module you were going to buy elsewhere can move the rate on everything else. So the module list is a commercial decision, not just a technical one, and it should be written down before the first call.
What does publish, for reference
You cannot benchmark against a number that does not exist, but you can at least know what the published end of this market looks like. Read from the vendor’s own page on 30 October 2026:
NinjaOne starts as low as $1.50 per month at 10,000 endpoints. The same statement puts it at $3.75 at 50 or fewer endpoints, and notes that the rate varies by region and by which products you buy. That is volume-tiered and inverted from the intuition: the cheap figure needs the enormous device count, and a small team pays the high end.
Treat that as a shape rather than a comparison. It tells you that per-device monitoring in this market is priced in low single-digit dollars per month at scale, which is a useful sanity check when a quote arrives. It does not tell you what a bundle including backup and ticketing should cost, because that is a different purchase.
Several neighbours publish nothing at all. Absolute has no pricing page, and its URL returns a 404 in the same way. Lansweeper’s pricing page carries a single six-figure savings claim rather than a rate. Iru, formerly Kandji, publishes no figure on its pricing page. The absence is the category norm now rather than one vendor’s choice.
What to do:
- Write the module list before the first call, separating must-have from would-take-if-cheap.
- Decide your maximum commitment term in advance, because term is a main pricing lever here.
- Get the quote broken out per module, not as one bundled figure, so you can see what each part costs.
- Ask what happens at renewal, specifically whether the rate is held and what notice is required.
- Price at least one specialist alternative per module so you know what you are trading away.
A worked example, and the trap in it
A managed service provider with 1,400 endpoints across 40 client companies wants remote monitoring, backup and documentation. Three modules, one vendor, one invoice, and a real appetite for consolidation.
The attractive version of this is a single bundle at a rate none of the three could be bought for individually. The trap is that the bundle is also the thing that makes switching any one module expensive later, because removing one part may reprice the rest. That is the actual decision behind Kaseya pricing, and it is a contract question rather than a software one.
The way to protect yourself costs nothing: ask for the per-module breakdown in writing even if you intend to buy the bundle. If the vendor will state what documentation alone costs, you know what you are giving up by bundling it. If that number is not forthcoming, you have learned something about your position at renewal.
The half that no monitoring tool covers
Remote monitoring watches a machine that exists and is connected. It does not buy the machine, ship it to a new hire in another country, hold a spare where you have no office, or recover it from someone who left. On a distributed team that physical work is where most of the unplanned effort goes, and no bundle contains it.
Disclosure: RemoAsset is our own product, owned by the same people who publish this site. It does the hardware side: procurement, international shipping, tracking, retrieval and wiping. It is named here as the adjacent problem rather than as an alternative to anything above.
Its limits deserve the same clarity. RemoAsset is not an MDM, so it enrols devices but does not monitor or configure them, and you would run a management tool alongside it. It is also not a certified ITAD, meaning it wipes machines but is not the answer where certified destruction and documentation are required. And its coverage is not every country, so check the market list against your own first.
The verdict
There is no way to research Kaseya pricing to a number, and pretending otherwise wastes your time. The useful preparation is not finding a figure, it is arriving with a module list, a term limit and a per-module breakdown request, because those three things are what the conversation will actually turn on.
Judge the quote you get against your own alternatives per module rather than against a list price that does not exist. You can confirm the state of the pricing page yourself at the Kaseya site, and it is worth rechecking, because vendors in this category have been changing what they publish in both directions.
Checklist:
- Module list written down and split into must-have and optional.
- Maximum commitment term decided before the first conversation.
- Per-module breakdown requested in writing.
- Renewal terms and notice period confirmed.
- At least one specialist alternative priced per module.
- You know who owns buying, shipping and recovering the hardware.
What is Kaseya pricing per endpoint?
There is no published figure. Checked on 30 October 2026, the vendor’s pricing URL returns a 404 with and without a trailing slash, while the homepage loads normally, so this is an absent page rather than a site problem. Any per-endpoint number you find elsewhere came from a quote, an estimate or an invoice, and none of those is a list price you can hold the vendor to.
Why does Kaseya not publish prices?
The most likely reason is structural rather than evasive. This is a portfolio assembled largely through acquisition, covering monitoring, backup, documentation, ticketing and security, each with its own unit of measurement. A published tier needs a tier to publish, and when the product is a configuration across a dozen tools there is no single figure that would be true for two different buyers.
Does Datto publish pricing?
It has a page titled pricing, and that page carries no figure. This is worth knowing as a distinct case: a page that returns 200 and publishes nothing is different from a page that does not exist, and a status check alone would report the first one as healthy. For a buyer the practical outcome is identical, which is that you need a quote.
What should I ask on the first call?
Ask for the quote broken out per module rather than as a single bundled figure, state your maximum commitment term up front, and get the renewal terms and notice period in writing. With bundle selling the discount usually comes from breadth and term, so knowing what each part costs individually is the only way to tell what bundling is actually buying you.
How does it compare with what competitors publish?
Only loosely, because you are comparing a bundle against single products. NinjaOne does publish a volume-tiered range for monitoring, which gives a sense of what per-device monitoring costs at the published end of this market. Use it as a sanity check on a quote rather than as a benchmark, and remember that several neighbours including Absolute publish nothing at all.
Does any of this cover buying and shipping hardware?
No. Monitoring and management tools watch and configure machines that already exist and are connected, so procurement, international shipping, spare stock, recovery from leavers and certified disposal remain separate problems whatever you buy. On a distributed team that physical half generates most of the unplanned work, so decide who owns it before signing a multi-year commitment.