Built by the people who needed it.
PatchMon started because the existing options for patch monitoring were either too expensive, too locked-down, or ignored half the fleet. Most tools handle Ubuntu. Some handle RHEL. Almost none handle FreeBSD. We built what we wished existed.
If you've managed servers at any real scale, you know the problem. You have hosts running Ubuntu, Debian, RHEL, maybe some CentOS or Rocky Linux. A few FreeBSD firewalls running pfSense. Windows boxes the dev team insisted on. Each one needs patches. Each one uses a different package manager. And nobody has a clear, centralised view of what's pending.
Enterprise patch management tools exist, but they're typically built for Windows-first environments, cost per-host, and require you to trust a third party with access to your infrastructure. Most ignore FreeBSD entirely. For teams with mixed fleets, the options boil down to “write scripts and hope” or “buy something that doesn't quite fit.”
PatchMon is the third option. An open-source platform purpose-built for patch monitoring across Linux, FreeBSD, and Windows. APT, DNF, YUM, APK, Pacman, FreeBSD pkg, and Windows Update Agent - all first-class, all in one dashboard. It uses an outbound-only agent model that your security team will actually approve, and deploys as a single binary with no external dependencies beyond PostgreSQL and Redis.
For MSPs and consultants managing multiple client environments, PatchMon includes multi-tenancy with per-tenant database isolation. Each client gets their own environment, their own data, and their own reporting - all managed from a single operational layer.
We ship three editions. Community is the full platform under AGPLv3 - free to self-host, unlimited hosts, no artificial restrictions. PRO adds enterprise modules and priority support for teams that need it. Cloud removes the infrastructure overhead entirely.
The goal is straightforward: give every infrastructure team - from a five-person startup to a thousand-host enterprise - the patch visibility they need without the vendor tax.
The Company
PatchMon is developed and maintained by the team behind 9 Technology Group Ltd, a UK-based technology company holding ISO 27001 and ISO 9001 certifications. These certifications reflect a commitment to information security management and quality assurance that carries through to how PatchMon is built and operated.
The Team
PatchMon is built by infrastructure engineers who run the same kinds of environments the tool is designed to manage. The team combines experience in Linux systems administration, security operations, and platform engineering.
Infrastructure-first thinking
Every feature is designed from the perspective of someone managing real servers in production.
Open source by conviction
We believe infrastructure tooling should be transparent, auditable, and community-owned.
Security-conscious by default
Security decisions are constraints, not afterthoughts. Least privilege and zero trust guide the architecture.
Community-responsive development
Feedback from production deployments shapes the roadmap. Real-world needs drive priorities.
What we believe
Transparency over trust
Infrastructure tools should be auditable. We open-source the platform so you can verify exactly what it does.
Simplicity over complexity
A single binary, a Docker Compose file, and a one-line agent install. If deployment takes more than 15 minutes, we've failed.
Security by design
Outbound-only agents, least-privilege defaults, and no telemetry. Security isn't a feature - it's a constraint on every decision.
Community-driven development
The roadmap is shaped by people running PatchMon in production. Feature requests and bug reports from real deployments drive priorities.
No artificial limitations
Community edition has no host caps, no user limits, and no feature gates. PRO and Cloud add value - they don't remove it from Community.
Sustainable open source
PRO and Cloud fund continued development. Open source is the foundation, not a marketing strategy. Both models have to work.
Want to work with us?
Whether it's contributing code, partnering, or joining the team.