The best Linux patch management software in 2026

Updated November 15, 2026By HostCrust11 tools compared14 min read

Automox is the best Linux patch management software for most teams: it supports current RHEL-family, Debian, Ubuntu, SLES and Amazon Linux releases and publishes its price ($1 per endpoint per month, billed annually). NinjaOne is the best pick if you also want a full RMM, and Action1 is the best free option, at no cost for the first 200 endpoints.

For Ubuntu-only fleets, use Canonical Landscape; for RHEL-only fleets, Red Hat Satellite; for a free, self-hosted tool across many distros, Uyuni. One or two servers may need nothing more than unattended-upgrades or dnf-automatic, checked regularly.

Our top picks

Compare at a glance

ToolBest forPricingOpen sourceDeploymentTested by us
Automoxmixed Windows, Mac and Linux fleets that want a published pricePatch OS: $1 per endpoint per month with an annual commitment; Automate Essentials and Enterprise: custom pricingNoSaaS with an agent on each deviceDocs only
NinjaOneIT teams that want patching inside a full RMMNo public list price (per device, by quote); NinjaOne says it starts at $1.50 per device per month at 10,000 endpoints and $3.75 at 50 or fewerNoSaaS with an agent on each deviceDocs only
Action1small teams that want free cloud patching for up to 200 endpointsFree for the first 200 endpoints with every feature; more endpoints: no public price (request a quote)NoSaaS with an agent on each deviceDocs only
ManageEngine Patch Manager Pluson-premises patching with a free tier and published pricesFree edition (20 workstations and 5 servers); Professional from $245 per year for 50 computers on-premises or $345 per year in the cloud; servers from $95 per year per 10NoOn-premises (Windows server) or cloudDocs only
Canonical LandscapeUbuntu-only fleetsLandscape SaaS is included with Ubuntu Pro ($500 per machine per year for Server with unlimited VMs; $25 per year for Workstation); Landscape's docs say a free personal Ubuntu Pro subscription manages up to 5 machines on Landscape SaaS; Managed Landscape add-on $3,099 per Landscape VM or $9,470 per physical machine per yearNoSaaS, Canonical-managed or self-hostedDocs only
Red Hat SatelliteRHEL estates with Red Hat subscriptionsNo public price for Satellite alone (contact sales); the Red Hat Store offers a Satellite bundle option on RHEL Server subscriptionsNoSelf-hosted (Satellite Server plus optional Capsules)Docs only
SUSE Multi-Linux Managervendor-supported patching of mixed Linux fleetsNo public price (contact sales; the SUSE shop shows prices only after login)NoSelf-hosted (container-based server), also on cloud marketplacesDocs only
Uyunifree, self-hosted patching across many distrosFree (open source); the commercial edition is SUSE Multi-Linux ManagerYesSelf-hosted (containerized server on Podman)Docs only
Foreman with Katellofree content management for RHEL-family fleetsFree (open source)YesSelf-hostedDocs only
Ansibleteams that already automate their servers with codeFree (open source); Red Hat Ansible Automation Platform: no public price (contact sales)YesSelf-hosted CLI, agentless over SSH (Red Hat Ansible Automation Platform is the commercial edition)Yes
HostCrust Ourssmall Linux fleets that want patches and reboots approved and recorded by defaultFree for up to 3 servers, then $5 per server per month (free for everyone during early access)NoSaaS with an outbound-only agent on each serverOurs

The full ranking

Automox

Best for: mixed Windows, Mac and Linux fleets that want a published price

Automox is the simplest pick when Linux servers sit next to Windows and Mac machines. Its supported-OS page lists RHEL, Rocky, AlmaLinux and Oracle Linux 8–10, Debian 11–13, Ubuntu 16.04 to 26.04, SLES 15.5–16, Amazon Linux 2023 and Fedora. On Linux it installs updates from each server's own repositories and doesn't cache packages, so those repositories must stay reachable. OS patching has a public price: $1 per endpoint per month on an annual plan. Third-party patching, software deployment and API access are in the custom-priced Automate tiers, and end-of-life releases such as RHEL 7 and CentOS 7 aren't supported.

Pricing
Patch OS: $1 per endpoint per month with an annual commitment; Automate Essentials and Enterprise: custom pricing (checked November 15, 2026, source)
License
Proprietary
Deployment
SaaS with an agent on each device
Runs on
Agents for Windows, macOS and Linux: RHEL, Rocky, AlmaLinux and Oracle Linux 8–10, CentOS Stream 9–10, Fedora, Amazon Linux 2023, Debian 11–13, Ubuntu 16.04–26.04 LTS, SLES 15.5–16 and some desktop derivatives

Pros

  • Public price for OS patching: $1 per endpoint per month (annual)
  • Current RHEL-family, Debian, Ubuntu, SLES and Amazon Linux releases
  • One console for Windows, macOS and Linux

Cons

  • End-of-life distros such as RHEL 7 and CentOS 7 aren't supported
  • Third-party patching, deployment and API need a custom-priced tier
  • Linux packages aren't cached: every server needs its own repository access

Not tested by us yet: based on the vendor's documentation.

NinjaOne

Best for: IT teams that want patching inside a full RMM

NinjaOne patches Linux through each server's own package manager (APT, DNF, YUM or Zypper) and its configured repositories, so third-party apps from those repositories get patched too. Its fully supported list covers RHEL 7–10, Debian 11–13, Ubuntu 20.04–26.04, Oracle Linux, Amazon Linux and SLES 12+, with Rocky, AlmaLinux and Fedora in a less thoroughly tested extended tier. The same agent brings monitoring, scripting and a remote terminal. NinjaOne doesn't publish a full price list: it says per-device prices run from $3.75 a month at 50 devices down to $1.50 at 10,000. Its Patch Intelligence AI doesn't cover Linux, and it doesn't do major distro upgrades.

Pricing
No public list price (per device, by quote); NinjaOne says it starts at $1.50 per device per month at 10,000 endpoints and $3.75 at 50 or fewer (checked November 15, 2026, source)
License
Proprietary
Deployment
SaaS with an agent on each device
Runs on
Agents for Windows, macOS and Linux. Full support: RHEL 7–10, Debian 11–13, Ubuntu 20.04–26.04 LTS, Oracle Linux 7–10, Amazon Linux 2 and 2023, SLES 12+, Raspberry Pi OS; Rocky, AlmaLinux, Fedora and others under extended support. Needs systemd

Pros

  • Uses the server's own package manager and repositories
  • Patching, monitoring, scripts and terminal in one agent
  • Fully supported list includes RHEL 7 and SLES 12+

Cons

  • No public price list (quote only)
  • Rocky and AlmaLinux are only under extended support
  • Patch Intelligence AI doesn't cover Linux

Not tested by us yet: based on the vendor's documentation.

Action1

Best for: small teams that want free cloud patching for up to 200 endpoints

Action1 is free for the first 200 endpoints with every feature and no time limit, which no other commercial tool here matches. Its Linux support is new: Action1 announced it in November 2025, starting with Ubuntu, Debian, Red Hat and SUSE, and its Linux patching page still names those four families, even though the agent installs on more distros, including Rocky, AlmaLinux and Fedora. The agent is x64 only and needs outbound access to Action1's cloud, and remote desktop works only on Windows. Pick it for a small mixed fleet; pick Automox or NinjaOne if your servers run distros outside Action1's patch list.

Pricing
Free for the first 200 endpoints with every feature; more endpoints: no public price (request a quote) (checked November 15, 2026, source)
License
Proprietary
Deployment
SaaS with an agent on each device
Runs on
Agents for Windows, macOS and Linux (x64): Ubuntu 18.04–26.04 LTS, Debian 12–13, RHEL 8–10, Rocky, AlmaLinux, Oracle Linux 10, Amazon Linux, SLES, openSUSE, Fedora and others; Linux patching covers Ubuntu, Debian, RHEL and SLES

Pros

  • Free for the first 200 endpoints, all features, no expiry
  • No on-premises server or VPN needed
  • Also patches Windows and macOS

Cons

  • Linux patching is documented for Ubuntu, Debian, RHEL and SLES only
  • Linux agent is x64 only
  • Above 200 endpoints, price by quote only

Not tested by us yet: based on the vendor's documentation.

ManageEngine Patch Manager Plus

Best for: on-premises patching with a free tier and published prices

Patch Manager Plus is the cheapest commercial option with a published price list, and one of the few you can run on your own server instead of a vendor's cloud. Professional starts at $245 a year for 50 computers on-premises, with servers priced separately from $95 a year per 10, and the free edition covers 20 workstations and 5 servers. Its Linux page lists RHEL 8–9, Ubuntu 20.04+, Debian 11–12, SLES 12 SP5+, Rocky 8–9, Oracle Linux 7–9 and Amazon Linux. Two caveats from ManageEngine's own pages: non-security Linux updates work only on Red Hat, CentOS and Ubuntu, and the on-premises server installs on Windows only.

Pricing
Free edition (20 workstations and 5 servers); Professional from $245 per year for 50 computers on-premises or $345 per year in the cloud; servers from $95 per year per 10 (checked November 15, 2026, source)
License
Proprietary
Deployment
On-premises (Windows server) or cloud
Runs on
Agents for Windows, macOS and Linux: RHEL 8–9, Ubuntu 20.04+, Debian 11–12, SLES 12 SP5+, CentOS Stream 9, Oracle Linux 7–9, Rocky 8–9, Amazon Linux 2 and 2023 (Linux patch page list)

Pros

  • Published prices and a free edition
  • On-premises or cloud
  • Covers Windows, macOS, Linux and third-party apps

Cons

  • Non-security Linux updates only on Red Hat, CentOS and Ubuntu
  • On-premises server needs Windows
  • ManageEngine's pages give two different Linux distro lists

Not tested by us yet: based on the vendor's documentation.

Canonical Landscape

Best for: Ubuntu-only fleets

If every server runs Ubuntu, Landscape is the natural choice: it's Canonical's own management tool, and the current release manages Ubuntu 18.04 LTS and newer, including 26.04 LTS. It comes with an Ubuntu Pro subscription, so its price is effectively Ubuntu Pro's ($500 per machine per year for Server with unlimited VMs), and Landscape's docs say a free, personal Ubuntu Pro subscription manages up to 5 machines on Landscape SaaS. You can use Canonical's SaaS, a single-tenant instance that Canonical runs for you, or host it yourself, including air-gapped. It manages nothing but Ubuntu, so a single Debian or RHEL server means a second tool.

Pricing
Landscape SaaS is included with Ubuntu Pro ($500 per machine per year for Server with unlimited VMs; $25 per year for Workstation); Landscape's docs say a free personal Ubuntu Pro subscription manages up to 5 machines on Landscape SaaS; Managed Landscape add-on $3,099 per Landscape VM or $9,470 per physical machine per year (checked November 15, 2026, source)
License
Proprietary (Landscape Client is open source, GPL-2.0)
Deployment
SaaS, Canonical-managed or self-hosted
Runs on
Ubuntu only: manages Ubuntu 18.04 LTS and newer

Pros

  • Made by Ubuntu's publisher for Ubuntu 18.04 LTS and newer
  • SaaS, Canonical-managed or self-hosted, including air-gapped
  • Free SaaS account for up to 5 machines

Cons

  • Ubuntu only
  • Priced through Ubuntu Pro subscriptions
  • Repository management only in the managed and self-hosted editions

Not tested by us yet: based on the vendor's documentation.

Red Hat Satellite

Best for: RHEL estates with Red Hat subscriptions

Satellite is Red Hat's own tool for RHEL fleets: a self-hosted server that mirrors and curates content, applies errata, provisions hosts and reports on compliance, with Capsule servers for remote sites. It's built from the open-source Foreman, Katello, Pulp and Candlepin projects (Satellite 6.19 ships Foreman 3.18 and Katello 4.20) and comes with Red Hat support. Its content-management documentation lists only RHEL 7, 8, 9 and 10 as supported clients, so it's the wrong tool for Ubuntu or Debian. Red Hat doesn't publish a price for Satellite alone; its store sells it as a bundle option on RHEL Server subscriptions.

Pricing
No public price for Satellite alone (contact sales); the Red Hat Store offers a Satellite bundle option on RHEL Server subscriptions (checked November 15, 2026, source)
License
Proprietary subscription (built from the open-source Foreman, Katello, Pulp and Candlepin projects)
Deployment
Self-hosted (Satellite Server plus optional Capsules)
Runs on
Red Hat Enterprise Linux 7, 8, 9 and 10 only

Pros

  • Red Hat-supported errata, content views and lifecycle environments
  • Self-hosted, with Capsule servers for remote sites
  • Each subscription includes a RHEL instance to run Satellite on

Cons

  • Supported clients are RHEL only
  • No standalone public price
  • Trails the upstream Foreman and Katello releases

Not tested by us yet: based on the vendor's documentation.

SUSE Multi-Linux Manager

Best for: vendor-supported patching of mixed Linux fleets

SUSE Multi-Linux Manager, formerly SUSE Manager, has the widest supported client list of the commercial servers here: SLES, openSUSE Leap, RHEL 7–10, AlmaLinux, Rocky and Oracle Linux 8–10, Amazon Linux, Debian 13 and Ubuntu 22.04–26.04. It's built on the open-source Uyuni project, its server now runs as containers, and it manages Debian and Ubuntu clients through Salt. Version 5.2 dropped Ubuntu 20.04 and Debian 11 as clients and treats Debian 12 as deprecated, so check your versions first. Prices aren't public: the SUSE shop shows them only after you log in.

Pricing
No public price (contact sales; the SUSE shop shows prices only after login) (checked November 15, 2026, source)
License
Proprietary subscription (based on the open-source Uyuni project)
Deployment
Self-hosted (container-based server), also on cloud marketplaces
Runs on
SLES 12/15/16, openSUSE Leap, RHEL 7–10, AlmaLinux, Rocky and Oracle Linux 8–10, Amazon Linux 2 and 2023, Debian 13, Ubuntu 22.04–26.04

Pros

  • One supported server for SUSE, RHEL-family, Debian and Ubuntu
  • Container-based server, also on major cloud marketplaces
  • Built on the open-source Uyuni project

Cons

  • No public price
  • Ubuntu 20.04 and Debian 11 clients dropped in 5.2
  • Debian 12 is deprecated as a client

Not tested by us yet: based on the vendor's documentation.

Uyuni

Best for: free, self-hosted patching across many distros

Uyuni is the open-source upstream of SUSE Multi-Linux Manager and the strongest free option for mixed fleets. Its client list is even longer than SUSE's, adding openSUSE Tumbleweed, openEuler and Raspberry Pi OS, and it ships often: 2026.10 came out on 23 October 2026. It's GPL-2.0 and Salt-based, and the server runs as containers on Podman. There's no vendor support, and it's a real server to install, back up and upgrade, which makes more sense for a fleet than for three VPSes. Its client table lists Debian 13; Debian 12 appears only in its repository list.

Pricing
Free (open source); the commercial edition is SUSE Multi-Linux Manager (checked November 15, 2026, source)
License
Open source (GPL-2.0)
Deployment
Self-hosted (containerized server on Podman)
Runs on
SLES, openSUSE Leap and Tumbleweed, RHEL 7–10, AlmaLinux, Rocky and Oracle Linux 8–10, Amazon Linux 2 and 2023, Debian 13, Ubuntu 22.04–26.04, Raspberry Pi OS, openEuler

Pros

  • Free and open source (GPL-2.0)
  • Very wide client list, including Debian and Ubuntu
  • Frequent releases

Cons

  • Community support only
  • A full server to run and maintain
  • Debian 12 support is unclear in its own docs

Not tested by us yet: based on the vendor's documentation.

Foreman with Katello

Best for: free content management for RHEL-family fleets

Foreman with Katello is the open-source upstream of Red Hat Satellite, and it moves faster: Foreman and Katello 5.0.1 were tagged on 2 and 5 October 2026, while Satellite 6.19 is based on Foreman 3.18. Katello syncs repositories, filters them into content views, promotes them through lifecycle environments and applies package and errata updates. It registers Enterprise Linux, Fedora, Amazon Linux, SUSE, Debian and Ubuntu hosts and serves deb content, though its own docs warn that Ubuntu's phased updates can stop updates reaching every Ubuntu host. It's free, but you install, run and upgrade it yourself.

Pricing
Free (open source) (checked November 15, 2026, source)
License
Open source (Foreman GPL-3.0-or-later, with a few files under BSD, MIT or font licenses; Katello GPL-2.0)
Deployment
Self-hosted
Runs on
Registers Enterprise Linux 8–10, Fedora, Amazon Linux, SLES/openSUSE, Debian and Ubuntu hosts; serves yum/RPM and deb content

Pros

  • Free and open source
  • Content views and lifecycle environments, like Satellite
  • Newer releases than Satellite

Cons

  • Community support only
  • Ubuntu phased updates interfere, per its docs
  • A substantial server to run and upgrade

Not tested by us yet: based on the vendor's documentation.

Ansible

Best for: teams that already automate their servers with code

Ansible isn't a patch manager, but many Linux teams patch with it because it needs no agent: a playbook runs over SSH and calls each distro's package module. The dnf module can install security updates only; the apt module has no security-only option, so on Debian and Ubuntu you upgrade everything or name the packages. In our check-mode runs against a Debian 12.15 and an AlmaLinux 9.8 test server, both modules correctly reported nothing left to install. You build the schedule, the reboot handling and the reports yourself, or buy Red Hat Ansible Automation Platform, which has no public price.

Pricing
Free (open source); Red Hat Ansible Automation Platform: no public price (contact sales) (checked November 15, 2026, source)
License
Open source (GPL-3.0-or-later)
Deployment
Self-hosted CLI, agentless over SSH (Red Hat Ansible Automation Platform is the commercial edition)
Runs on
Control node on Linux, macOS or WSL; manages any host with SSH and Python, plus Windows over WinRM, PSRP or SSH

Pros

  • Agentless: SSH and Python on the server are enough
  • The dnf module can apply security-only updates
  • Free and open source (GPL-3.0)

Cons

  • No security-only option in the apt module
  • Scheduling, reboots and reporting are up to you
  • Commercial platform price is quote-only

Tested by us: ansible-core 2.22.0 from a workstation, 14 Nov 2026 (UTC): check-mode apt upgrade=dist on Debian 12.15 and dnf name=* state=latest security=true on AlmaLinux 9.8. Both reported nothing to install; nothing was installed on the servers

HostCrust Ours

Best for: small Linux fleets that want patches and reboots approved and recorded by default

HostCrust is our product, it's in early access, and it's ranked last because it's the least proven tool on this list. It does one narrow job for Ubuntu, Debian, AlmaLinux and Rocky Linux servers: a daily Patch Proof check of which CVEs are really open on each server, then patches, restarts and reboots that wait for an approver by default (your org's policy decides), with a receipt for each step. Verification is reported by the agent on the server. It doesn't patch Windows or macOS, and there's no self-hosted edition. It's free for up to 3 servers, then $5 per server per month, and free during early access.

Pricing
Free for up to 3 servers, then $5 per server per month (free for everyone during early access) (checked November 15, 2026, source)
License
Proprietary service (its free tools Patch Proof and unattended-upgrades-check are open source, Apache-2.0)
Deployment
SaaS with an outbound-only agent on each server
Runs on
Ubuntu 20.04+, Debian 11+, AlmaLinux 8+, Rocky Linux 8+

Pros

  • Approval before patches, restarts and reboots by default, with receipts
  • Daily CVE status that counts backports and the running kernel
  • Free for up to 3 servers; simple per-server price

Cons

  • Early access: the least proven tool here
  • Linux only: Ubuntu, Debian, AlmaLinux and Rocky Linux
  • No self-hosted edition
  • Patching is on request: no schedules, maintenance windows or patch rings
  • Verification is reported by the agent on the server

Ours: we build it and test it ourselves; no independent test yet.

How we picked

We started from the tools people actually compare for Linux patching: cloud patch services, RMM platforms with patching, the Linux vendors' own management servers, their open-source upstreams and Ansible. Then we ranked them on five things, in this order:

  1. Linux support you can verify. Distributions and versions from each vendor's own supported-OS page, not a “Linux” checkbox.
  2. What really happens on Linux. Native patch policies or just scripts, security-only updates, and reboots.
  3. Maturity and support. How long it has patched Linux, and who answers when it breaks.
  4. Price you can see. Free tiers and published prices, from vendor pricing pages checked on 15 Nov 2026.
  5. Effort to run. A small agent and a cloud console, or a server of your own.

We ran Ansible ourselves against two test servers (details below). Landscape manages only Ubuntu, and our test servers run Debian and AlmaLinux. The cloud products need accounts we didn't create. So everything else comes from vendor documentation, and each card says which. We left out PDQ because its own pages describe Windows and macOS support only. HostCrust is our product; it's marked “Ours” and ranked by the same criteria.

What does Linux patch management software do?

Linux patch management software finds the updates each server is missing, installs them on a schedule or on request, and shows which servers are behind. On Linux, nearly every tool does the installing through the distribution's own package manager: apt on Debian and Ubuntu, dnf or yum on the RHEL family, zypper on SUSE. What you pay for is everything around that: one view of every server, policies so test servers patch before production, maintenance windows, reboot handling, and a report you can hand an auditor. The bigger servers (Satellite, Katello, Uyuni, SUSE Multi-Linux Manager) also mirror the repositories and freeze tested snapshots, so production installs exactly the packages you tested. The cloud tools install from each server's configured repositories at run time (Automox and NinjaOne document this). Either way, an installed kernel update protects nothing until the server reboots into it, so reboots need a plan and a check afterwards.

What to look for in Linux patch management software

  • Your exact distros and versions. “Supports Linux” can mean four distro families. Action1's patching page names Ubuntu, Debian, RHEL and SLES; ManageEngine offers non-security updates only on Red Hat, CentOS and Ubuntu; Satellite supports RHEL clients only.
  • Security-only updates. dnf can filter on advisories (--security); apt has no equivalent, so Debian and Ubuntu tools either upgrade everything or work from the security archive.
  • Staged content. If “test, then production” matters, you want content views or snapshots (Satellite, Katello, Uyuni, SUSE), not live repositories.
  • Reboots and the running kernel. Kernel and glibc fixes don't protect anything until the server reboots. Look for reboot scheduling and a report of which kernel is actually running.
  • Evidence. Who approved what, when it ran, what changed. Auditors ask for it.
  • Connectivity. Cloud agents need outbound internet; air-gapped networks need a self-hosted server (Landscape self-hosted, Satellite, Uyuni, Katello).

Linux-native or cross-platform?

ToolBuilt forLinux clients (vendor docs)Where it runs
AutomoxWindows, macOS, LinuxRHEL family 8–10, Debian 11–13, Ubuntu 16.04–26.04, SLES 15.5–16, Amazon Linux 2023Cloud
NinjaOneWindows, macOS, LinuxFull: RHEL 7–10, Debian 11–13, Ubuntu 20.04–26.04, SLES 12+; extended: Rocky, AlmaLinux, FedoraCloud
Action1Windows, macOS, LinuxPatching: Ubuntu, Debian, RHEL, SLESCloud
Patch Manager PlusWindows, macOS, LinuxRHEL 8–9, Ubuntu 20.04+, Debian 11–12, SLES 12 SP5+, Rocky 8–9 and othersYour Windows server or cloud
LandscapeUbuntuUbuntu 18.04 LTS and newerCloud or your server
SatelliteRHELRHEL 7–10Your server
SUSE Multi-Linux Manager / UyuniMixed LinuxSLES, RHEL family, Amazon Linux, Debian 13, Ubuntu 22.04–26.04 and moreYour server
Foreman with KatelloMixed Linux, RHEL-firstEL 8–10, Fedora, Amazon Linux, SUSE, Debian, UbuntuYour server

Rule of thumb: if Windows laptops are in scope, a cross-platform cloud tool saves you a second console. If it's all Linux servers, a Linux-native server gives you staged content and works without the internet.

What we saw when we patched with Ansible

We ran ansible-core 2.22.0 from a workstation on 14 Nov 2026 (UTC), with nothing installed on the servers except Ansible's own temporary files, which we removed. Both test servers were already fully patched by their own automatic updates, and check mode (--check) reports what would change without changing anything.

Debian 12.15, full upgrade in check mode:

$ ansible debian -m ansible.builtin.apt -a "upgrade=dist" --check
web-01 | SUCCESS => {
    "changed": false,
    ...
    "0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded."

AlmaLinux 9.8, security updates only, in check mode:

$ ansible alma -m ansible.builtin.dnf -a "name=* state=latest security=true" --check
web-02 | SUCCESS => {
    "changed": false,
    "msg": "Nothing to do",
    "rc": 0,
    "results": []
}

That's the whole appeal and the whole limit of Ansible for patching: it does exactly what you write. The schedule, the reboot (ansible.builtin.reboot), the order of servers and the report are yours to build.

Open source or SaaS?

Open-source patch servers (Uyuni, Foreman with Katello) cost nothing to license but need a server of their own, backups and upgrades, and someone who knows them. In return you get mirrored, staged content, no outbound internet requirement and no per-endpoint bill. Ansible is open source too, but it's a toolkit, not a product.

SaaS tools (Automox, NinjaOne, Action1) are running within an hour: install an agent, set a policy. You pay per endpoint or by quote, the servers need outbound access to the vendor's cloud, and updates come straight from each server's configured repositories. ManageEngine and Landscape sit in between, with both cloud and self-hosted editions. For a small team without a dedicated Linux admin, SaaS usually wins on time. For a large or regulated Linux estate, the self-hosted servers usually win on control.

Automox and Action1 alternatives

If Automox's custom-priced tiers or Action1's 200-endpoint ceiling are the problem, NinjaOne is the closest like-for-like cloud alternative (with a full RMM attached), and ManageEngine Patch Manager Plus is the cheapest with published prices and an on-premises option. If the problem is Linux coverage, a Linux-native server fits better: Landscape for Ubuntu, Satellite for RHEL, Uyuni or SUSE Multi-Linux Manager for a mix.

Do you need patch management software at all?

For one to five Linux servers, often not. Ubuntu Server installs security updates daily out of the box with unattended-upgrades, Debian can do the same after one command, and the RHEL family has dnf-automatic, which installs nothing until you set apply_updates = yes. What those tools don't do is tell you when they silently stop: a masked timer, a held package, a missing security origin or a kernel that never got rebooted into. So the real minimum is automatic updates plus a regular check that they're working and that the running kernel is current. Patch management software starts paying off when you have enough servers that “log in and look” stops happening: you want one view of every server, test-before-production rings, scheduled reboots and a report for an auditor. That point usually comes somewhere past a dozen servers, or immediately if a customer contract asks for patch evidence.

How we checked this: On 14 Nov 2026 (UTC) we ran Ansible (ansible-core 2.22.0, from a workstation, nothing installed on the servers) in check mode against a Debian 12.15 test VM (apt module, upgrade=dist) and an AlmaLinux 9.8 test VM (dnf module, security-only), and removed its temporary files afterwards. Every other tool is researched from the vendor's documentation and pricing pages, checked on 15 Nov 2026, and was not run on our servers. Anything we didn't run ourselves comes from the official documentation listed under Sources.

Check that auto-patching is really working

unattended-upgrades-check runs 12 read-only checks over SSH on Ubuntu, Debian, AlmaLinux and Rocky Linux servers (unattended-upgrades or dnf-automatic) and gives each server a PASS, WARN or FAIL. Free and open source (Apache-2.0).

Get unattended-upgrades-check

Check which CVEs are really open on your server

HostCrust Patch Proof compares every installed package with your distribution's own security data. It counts fixes your distro backported and checks the kernel that is actually running, not just the one on disk. Read-only, no root, free.

Run the free check About Patch Proof

FAQ

What is the best free Linux patch management software?

It depends on what “free” has to cover. Action1 is free for the first 200 endpoints with every feature, and its Linux patching covers Ubuntu, Debian, RHEL and SLES. ManageEngine Patch Manager Plus has a free edition for 20 workstations and 5 servers. If you want open source, Uyuni (GPL-2.0) and Foreman with Katello (GPL) are full patch servers, and Ansible (GPL-3.0) can patch over SSH with no agent. For one or two servers, the built-in unattended-upgrades (Debian, Ubuntu) and dnf-automatic (RHEL family) are free and enough, as long as you check that they actually run.

Does Automox support Linux?

Yes. Automox's supported-OS page lists RHEL, Rocky Linux, AlmaLinux and Oracle Linux 8–10, CentOS Stream 9–10, Fedora, Amazon Linux 2023, Debian 11–13, Ubuntu 16.04 to 26.04 LTS and SLES 15.5–16. On Linux it installs updates from each server's own repositories and doesn't cache packages. End-of-life releases such as RHEL 7, CentOS 7 and Amazon Linux 2 aren't supported.

Can PDQ patch Linux servers?

No. PDQ's own pages describe PDQ Connect and PDQ Deploy & Inventory as Windows and macOS tools, and PDQ's comparison with Automox says teams that need Linux support may still consider Automox. That's why PDQ isn't in this ranking.

Is Ansible good enough for Linux patch management?

For teams that already use it, often yes. The dnf module can install security updates only, the apt module can run a full or safe upgrade, and the reboot module waits for the server to come back. What you don't get is a patch product: you write the playbooks, decide when they run, handle reboots and keep the reports yourself. The apt module also has no security-only option.

What's the difference between Red Hat Satellite and Foreman with Katello?

Satellite is Red Hat's supported product built from Foreman, Katello, Pulp and Candlepin; Satellite 6.19 ships Foreman 3.18 and Katello 4.20. Foreman with Katello is the free upstream, newer (Foreman and Katello 5.0.1 were tagged on 2 and 5 October 2026) and able to register more distributions, including Debian and Ubuntu, but with community support only. Satellite's documentation lists RHEL 7 to 10 as its supported clients.

Do Linux patching tools reboot the server?

Most can, but none should do it silently. A kernel or glibc update is installed on disk, yet the server keeps running the old code until it reboots or the service restarts. Check how each tool schedules reboots, whether it reports the kernel that is actually running, and whether you can require someone to approve a reboot on production servers.

Sources

  1. Automox pricing
  2. Automox docs: supported operating systems
  3. Automox docs: third-party software support (Linux packages come from the device's repositories)
  4. NinjaOne pricing
  5. NinjaOne: Linux patch management (supported distributions)
  6. Action1 pricing
  7. Action1: Linux patch management
  8. Action1 docs: system requirements
  9. ManageEngine Patch Manager Plus pricing
  10. ManageEngine Patch Manager Plus: edition comparison (Free edition: up to 20 workstations and 5 servers)
  11. ManageEngine Patch Manager Plus: Linux patch management
  12. ManageEngine Patch Manager Plus: system requirements (server on Windows)
  13. Ubuntu Pro pricing (includes Landscape)
  14. Landscape docs: supported versions
  15. Landscape docs: create a SaaS account (a free personal Ubuntu Pro subscription manages up to 5 machines)
  16. Red Hat Store: RHEL Server (Satellite bundle option)
  17. Red Hat: Satellite 6 component versions (Satellite 6.19: Foreman 3.18.x, Katello 4.20.x)
  18. Red Hat Satellite 6.19: overview and supported client architectures
  19. SUSE Multi-Linux Manager 5.2: supported clients and features
  20. SUSE Multi-Linux Manager 5.2 release notes
  21. Uyuni: supported clients and features
  22. Foreman 5.0.1 release on GitHub (tagged 2 October 2026)
  23. Katello 5.0.1 release on GitHub (tagged 5 October 2026)
  24. Foreman 5.0 with Katello: Managing Hosts (supported clients)
  25. Ansible docs: ansible.builtin.dnf module
  26. Ansible docs: ansible.builtin.apt module
  27. PDQ: Automox vs PDQ (operating system support)