TL;DR

Action1 pricing did not return a readable figure when its page was fetched directly. That is not the same as publishing nothing, and the difference matters: the page renders its pricing in JavaScript, so a browser may well show you a full table where an automated reader sees an empty page.

  • The page renders in JavaScript; figures sit in script.
  • That is not the same as publishing nothing.
  • Open it in a browser before believing any comparison.
  • Patching is usually priced per endpoint.
  • A free tier with a device ceiling is a real option.
  • Budget the cadence, not just the licence.

What a direct fetch returns

Worth describing exactly, because the conclusion people draw from it is usually too strong.

The pricing page returns a normal response to a plain request. Strip out the script and style tags and the remaining text is about five thousand characters and contains no currency figures at all. A raw search of the file does turn up dollar amounts, and every one of them sits inside script.

The page also refused one automated reader outright while answering another, which is ordinary bot handling and not evidence of anything about the pricing.

So the honest statement is that it did not return a readable figure. It is not that the vendor publishes no price.

Why that distinction is not pedantry

A tool in this same category was recorded for months as not publishing prices on exactly this reasoning. It publishes them in full, as plain text. The real cause was a wrong URL that returned a 404, read as a rendering problem. Check the URL and open a browser before concluding anything about a vendor’s transparency.

How to check it in two minutes

Four steps, and they apply to any vendor whose page looks empty.

Open the page in an ordinary browser and look. This settles most cases immediately.

Check the URL itself. Try the obvious variants, including a business or app subdomain, because vendors move pricing and leave the old path returning a 404.

Disable JavaScript and reload. If the figures vanish, you have confirmed the rendering explanation rather than assumed it.

Note the date. Pricing pages in this category change often enough that an undated figure is one you will check again anyway.

Write down what you saw with its unit and term attached. A number without a unit is not a price, and a per-endpoint figure and a per-technician figure can look identical in a table while differing by an order of magnitude on a real fleet. The unit decides the bill, so record it in the same cell as the figure rather than in a footnote nobody reads.

How patching tools are usually priced

Useful background whatever the figure turns out to be, because the basis decides the total.

Patch management sits in a category that mostly prices per endpoint or per device, and that is the basis to expect. Several competitors in the same space do publish: one states a per-endpoint monthly rate with an annual commitment, another publishes per-device rates with a licence minimum.

Other adjacent tools price per user, which quietly favours you if people carry several machines, or per technician, which favours a small admin team with a large estate.

Basis Bill tracks Good for
Per endpoint Hardware count Few devices per person
Per user Headcount Several devices each
Per technician Admin team Small team, large fleet

endpoint management software covers which vendors sit where, which is the comparison worth building before you care about any single number.

Free tiers with a device ceiling

Common in this category and genuinely useful, with one thing to plan around.

Several vendors offer a free tier capped at a device count. For a small team that is not a trial, it is an answer, and it covers a lot of companies currently managing nothing at all.

The thing to plan for is the step. A ceiling of thirty devices means that at thirty one you are on a paid plan, and paid plans in this category often carry their own licence minimum, so the increase is a step rather than a slope.

Work out where your headcount puts you in twelve months, not today. Adopting a free tier and being forced off it mid-year is a worse outcome than starting paid, because the migration costs you time you did not budget.

What to confirm about any free tier

  • The exact device ceiling, and whether it counts servers.
  • Whether support is included at all.
  • What happens on the day you exceed it.

The licence is not the cost

Patching has an operational cost that dwarfs the software on most estates.

Someone has to decide the cadence, test that an update does not break a critical application, schedule it around people who are working, and deal with the machines that did not take it.

That last group is the one that consumes the time. Devices that are off, offline, or belong to somebody on leave fall out of every patch run, and chasing them is manual on every tool.

CISA’s known exploited vulnerabilities catalogue is the right reference for deciding what cadence you are actually committing to, because it distinguishes what is being exploited now from what is merely outstanding, and that distinction is what makes a patch policy achievable rather than aspirational.

the NIST Cybersecurity Framework is the broader frame if you need to show how patching fits the rest of your controls.

What patching cannot reach

Three gaps, and they are physical rather than technical.

A device that never connects cannot be patched, reported on, or wiped. In a distributed team that set is larger than people expect and grows quietly after every departure.

A device nobody can locate is not a patching problem at all. RemoAsset’s laptop lifecycle management covers the lifecycle side, including getting hardware back from people who have left.

A device at end of life needs disposal evidence rather than an update. the EPA on electronics and batteries management covers handling and NIST Special Publication 800-88 on media sanitization the sanitization standard.

Count your unreachable machines before buying anything. If a tenth of the fleet has not checked in for a month, your first problem is custody, not patch coverage, and no licence fixes it.

What to do with an unreadable pricing page

Three things, in order, and none of them is to guess.

Look at it yourself in a browser, and record what you see with the unit and the date.

Never write a figure you could not read. An invented number in a budget is worse than a gap, because a gap gets chased and a number gets trusted.

Say which it is in whatever you produce: publishes a price, publishes nothing, or did not return a readable figure. Those three are genuinely different and only the middle one is a criticism of the vendor.

The same goes for a figure you saw six months ago. Pricing in this category moved twice in the last year among the vendors compared here, and a remembered number is the least reliable kind. Re-check anything you are about to put in a document somebody else will act on.

Apply the same standard to any comparison article you read, including the ones that confidently list prices for vendors that do not publish them. Where a figure appears without a plan name, a unit and a term beside it, treat it as unverified until you have seen it on the vendor’s own page.

Patching reaches devices that connect. RemoAsset reaches the ones that do not, in 80+ countries. See RemoAsset’s laptop lifecycle management or RemoAsset’s pricing.

Frequently asked questions

Is action1 pricing published?

It did not return a readable figure to a direct fetch, which is not the same as publishing nothing. Strip the script and style tags from the page and the remaining text is about five thousand characters with no currency figures at all, while a raw search does find dollar amounts, every one of them inside script. The page renders its pricing in JavaScript, so a browser may show a full table.

Why does that distinction matter?

Because a tool in this same category was recorded for months as not publishing prices on exactly this reasoning, and it publishes them in full as plain text. The real cause there was a wrong URL returning a 404, which was read as a rendering problem. Check the URL and open a browser before concluding anything about a vendor’s transparency, and say which of the three situations you actually found.

How do I check a page that looks empty?

Four steps that apply to any vendor. Open it in an ordinary browser and look, which settles most cases. Check the URL itself, trying obvious variants including a business or app subdomain, because vendors move pricing and leave the old path returning a 404. Disable JavaScript and reload to confirm the rendering explanation. And note the date, since these pages change often.

How are patching tools usually priced?

Mostly per endpoint or per device, and that is the basis to expect. Several competitors do publish: one states a per-endpoint monthly rate with an annual commitment, another publishes per-device rates with a licence minimum. Adjacent tools price per user, which favours you if people carry several machines, or per technician, which favours a small admin team with a large estate.

Are free tiers worth using?

Often yes, and for a small team a capped free tier is an answer rather than a trial. The thing to plan for is the step: a ceiling of thirty devices means that at thirty one you are on a paid plan, and paid plans in this category often carry their own licence minimum, so the increase is a step rather than a slope. Work out where your headcount puts you in twelve months.

What is the real cost of patching?

Operational rather than licensing, on most estates. Someone has to decide the cadence, test that an update does not break a critical application, schedule it around people who are working, and deal with machines that did not take it. That last group consumes the time, since devices that are off, offline or belong to somebody on leave fall out of every run and chasing them is manual on every tool.

What should I never do with an unreadable page?

Guess. Never write a figure you could not read, because an invented number in a budget is worse than a gap: a gap gets chased and a number gets trusted. Say which of the three situations applies in whatever you produce, meaning publishes a price, publishes nothing, or did not return a readable figure. Apply the same standard to comparison articles that confidently list prices.