Two things to know before you shortlist Absolute Software. The brand is now Absolute Security, though the legal entity name has not changed. And there is no pricing page at all, so any figure you have seen came from somebody’s quote rather than a published rate.

TL;DR

  • The product brand is now Absolute Security across the homepage, platform page and about page.
  • The old name survives in the copyright footer as Absolute Software Corporation, so contracts will legitimately carry it.
  • That makes this a rebrand rather than a retirement, which is a softer change than a brand being absorbed by another company.
  • No price is published anywhere. The pricing URL returns a 404 rather than redirecting.
  • Its distinguishing claim is a platform built into device firmware, which is a genuinely different design from an installed agent.
  • Firmware residency is also the thing to check hardest, because it depends on your hardware rather than on your configuration.

What happened to Absolute Software

Checked on 30 October 2026, the evidence is consistent across three pages. The homepage title reads “Stop Downtime and Business Disruption | Absolute Security”. The platform page reads “The Absolute Cyber Resilience Platform | Absolute Security”. The about page reads “About Us | Absolute Security” and uses the new name twenty times.

On each of those pages the old product name appears exactly twice, and both occurrences are inside the copyright line, as Absolute Software Corporation. That is the detail that makes this different from a brand disappearing into an acquirer: the corporate entity is unchanged, so your paperwork is not wrong, it is just using the legal name rather than the trading name.

Practical consequence, and it is small. Update runbooks and dashboards to the new brand so colleagues can find the documentation. Leave the contract alone, because the counterparty named in it still exists. Those two sentences are the whole migration.

What the platform actually claims to do

The positioning is cyber resilience, and the specific claim worth paying attention to is that the platform is built into the firmware. Its own platform heading describes a resilience platform embedded at that level in order to reduce downtime.

This is a real architectural difference rather than marketing. An ordinary management agent is software you install, which means it can be uninstalled, wiped by a reimage, or removed by somebody who does not want to be managed. A component that lives below the operating system survives those events. For a fleet where devices genuinely go missing, that distinction is the product.

It also sets the main question for an evaluation. The page carries a compatibility checker asking whether your endpoints are supported, which tells you plainly that firmware residency is conditional on your hardware. Device management is usually a question of configuration. This is a question of which laptops you bought.

So the evaluation order is unusual. Check hardware compatibility across the real fleet before discussing features, because on an unsupported model you get the ordinary-software parts and not the part you are buying it for.

There is no published price

Checked with a browser user agent so bot blocking could be ruled out, the pricing URL returns a 404 with and without a trailing slash, and the products URL does the same. The platform page loads at over half a megabyte and carries no currency figure anywhere in it.

Note the difference from a neighbour. Kaseya also publishes nothing and its pricing page also 404s. Flexera, formerly Snow Software, routes its pricing URL to a contact page instead. Iru, formerly Kandji, serves a pricing page with no figure on it. Four different ways of not telling you, and only one of them trips a link checker.

What publishes, for a reference point: NinjaOne states a rate as low as $1.50 per month at 10,000 endpoints, rising to $3.75 at 50 or fewer endpoints. Use that as a sanity check on the shape of per-device pricing in this market, not as a comparison, because it is a different product doing a different job.

What to do:

  • Run the hardware compatibility check across every laptop model you own, not a representative sample.
  • Establish what the platform does on an unsupported model, since that is your fallback for part of the fleet.
  • Ask for the quote broken out by module rather than as one resilience figure.
  • Ask what happens to the firmware component when a device is sold or returned to a lessor.
  • Update internal references to the new brand, and leave the legal entity name in contracts alone.

Where it fits, and where it does not

This is not a general purpose device management product and it does not try to be. If your problem is configuring settings, pushing applications and enrolling new starters, the Apple-focused and cross-platform management tools do that work directly and publish rates you can compare.

Where it earns its place is a specific and genuine problem: a fleet where machines leave the building and do not reliably come back, where a device may be reimaged by somebody you did not authorise, and where you need to prove a machine was rendered unusable. That is a narrower brief than device management and a much harder one.

So it is usually an addition rather than a replacement. Most buyers end up running it alongside a management tool rather than instead of one, which matters for a budget because you are pricing two products.

A worked example at 600 laptops

A field services business with 600 laptops across four countries, high staff turnover, and a real recovery problem: roughly thirty machines a year go quiet and never come back. They already run a cross-platform management tool.

For this company the firmware argument is exactly right, because their losses are not configuration failures, they are devices leaving. The question is not whether the capability is worth having. It is whether the compatibility check covers the three laptop models they bought over six years, and what the platform can do on whichever generation it does not support.

That answer determines the shape of the deal. Full fleet coverage makes it one purchase. Partial coverage makes it a purchase plus a hardware refresh plan, which is a much larger conversation and belongs in the same business case.

The physical half

Freezing or wiping a missing laptop resolves the data risk. It does not get the machine back, replace it for the person who needs one on Monday, or produce a certificate for the auditor. Recovery as a security event and recovery as a logistics event are different problems.

Disclosure: RemoAsset is our own product, owned by the same people who publish this site. It handles the logistics side: procurement, international shipping, tracking, retrieval and wiping. It belongs here because the fleet described above has both problems and only one of them is solved by firmware.

Its limits should be as clear as its scope. RemoAsset is not an MDM, so it enrols devices but does not configure or secure them, and you would run a management tool as well. 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

Absolute Security, formerly Absolute Software, is solving a real problem that ordinary management tools genuinely cannot, and the firmware approach is a legitimate architectural answer rather than a repackaged agent. For a fleet with a persistent recovery problem it deserves a place on the list.

Go in knowing two things. Hardware compatibility decides how much of the value you actually get, so check it first and across everything. And there is no published price, so budget a sales cycle rather than an afternoon. You can confirm the current state at the vendor’s own site, including the compatibility checker.

Checklist:

  • Compatibility checked across every laptop model in the fleet.
  • Behaviour on unsupported models established in writing.
  • Quote broken out by module.
  • Resale and lease-return handling of the firmware component confirmed.
  • Internal references updated to the new brand; contract left on the legal entity name.
  • You know who owns buying, shipping and physically recovering the hardware.

Is Absolute Software still called that?

The product brand is now Absolute Security, used consistently across the homepage, platform page and about page as of 30 October 2026. The old name survives in exactly two places on each page, both inside the copyright line as Absolute Software Corporation, so the legal entity is unchanged. Update your documentation to the new brand and leave your contract on the legal name.

How much does it cost?

Nothing is published. Checked with a browser user agent, the pricing URL returns a 404 with and without a trailing slash, the products URL does the same, and the platform page carries no currency figure at all. So every number in circulation came from a quote or an estimate. Budget for a sales conversation and ask for the quote broken out by module.

What does firmware-level actually mean?

It means the component sits below the operating system rather than being installed into it. An ordinary agent can be uninstalled, removed by a reimage, or stripped by somebody who does not want to be managed. Something resident in firmware survives those events, which is the entire argument for the product on a fleet where devices genuinely go missing.

Will it work on my laptops?

That is the first question to settle, not the last. The platform page carries a compatibility checker asking whether your endpoints are supported, which tells you residency depends on your hardware rather than your configuration. Check every model you own rather than a sample, and establish what the platform can still do on a model it does not support.

Is this a replacement for device management?

No, and it does not claim to be. If your need is configuring settings, deploying applications and enrolling new starters, the dedicated management products do that directly and several of them publish comparable rates. This is a resilience and recovery product, so most buyers run it alongside a management tool rather than instead of one. Price two products, not one.

Does it recover the physical laptop?

It addresses the data risk on a missing machine rather than the logistics. Freezing or wiping a device resolves exposure, but it does not get the hardware back, put a replacement in someone’s hands for Monday, or produce the certificate an auditor asks for. Those are separate jobs, so decide who owns physical retrieval and certified disposal before you sign.