Free patch management divides the same way free RMM does, into commercial tiers with a device cap and open-source software with no cap and no support. Both are real answers for the right team and they fail in opposite directions. The commercial tier runs out as you grow; the open-source project runs out when something breaks at three in the morning. Choosing between them is mostly a question of whether your engineers' hours are billable.
Where free stops in the commercial tools
Level publishes the clearest boundary in this record: ten devices free, then $2 per device per month applied to the whole account, published plainly as ten devices free, eleven devices $22 a month, fifty devices $100 a month. Its platform includes patching, so under eleven devices this is genuinely free patch management. Action1 is the vendor most associated with a free patching tier in this market and its pricing page answers a Cloudflare block to every reader available to this site, so no figure is recorded for it here and none is borrowed from elsewhere. That is a limitation of this page rather than a finding about Action1, and the two should not be confused.
What the operating system already gives you free
Windows Server Update Services and its successors, and the built-in update mechanisms on macOS and Linux, patch the operating system at no licence cost, and for a small single-site fleet with a competent administrator that is often sufficient. What none of them does is patch third-party applications, which is where most of the exploitable surface lives, or produce a report an auditor or an insurer will accept. So the honest way to frame a free option is by what it leaves you exposed to. If your reason for buying is an insurance questionnaire or a client's security review, free operating-system patching does not answer it, and no amount of configuration will make it answer it.
What open source costs instead
An open-source patching stack removes the licence and adds a server you own, a database you back up, a catalogue you maintain and an upgrade you test. On Linux fleets in particular the tooling is mature and the trade is often good, because the people running those fleets are already comfortable with it and the package ecosystem does much of the work. On mixed Windows fleets the third-party catalogue is the hard part, and maintaining one yourself is a job rather than a task. Price it as hours. A 500-device fleet at $2 a device is $1,000 a month, which is a few engineer-hours; if maintaining the stack takes more than that, the free option is the expensive one and only the budget line has changed.
Questions people ask about free patch management
Is there free patch management software?
Level's first ten devices are free on a platform that includes patching, then $2 a device across the whole count. Action1 is the vendor most associated with a free tier here, and its pricing page could not be read from this site.
Is built-in Windows patching enough?
For a small single-site fleet with an administrator, often yes for the operating system. It does not patch third-party applications, where most of the exploitable surface is, and it produces no report an auditor or insurer will accept.
Is open source patch management worth it?
On Linux fleets frequently yes. On mixed Windows fleets the third-party catalogue is the hard part and maintaining one is a job. Price it in engineer-hours against roughly $2 a device before deciding.
What does a free tier actually buy me?
A way to run the product against real machines before committing. How it handles an application it does not know, and a user who never reboots, is what decides the choice and is on no pricing page.