Skip to main content

Welcome to PatchMon

Introduction

Welcome to PatchMons Documentation

PatchMon is an open open-source softwareLinux patch management system that helpsgives system administrators monitorcentralised visibility over patches and managepackages across their infrastructure.

It works with standard Linux patches, mainly working around package managers such- asapt, apt, yum, and dnf.

dnf

The- featureand listrequires isno growinginbound ports on ayour weeklymonitored basishosts.

and
these

Contributing docsto documentation

Documentation is an area where we need help :)

  • You can signup with your email or use SSO using your github account
  • After which we will enable your account to be updateda accordingly.

    contributor so you can edit
  • Please send us a message on Discord or email for your role to change to a contributor

How PatchMon Works

PatchMon

Howuses doesa itlightweight work

agent

It'smodel prettywith simple;three simple steps:

  1. YouDeploy the Server - Self-host PatchMon using Docker or the native installer, or use our managed Cloud version.
  2. Install the Agent - Add a host in the dashboard and run the one-liner install PatchMon Server (or setup with our Cloud hosted version on our website here )
  3. You add a Linux host on the platform and copy the script installer command for the "agent" (uses curl )
  4. The Agent that lives on your Linux systemserver.
  5. Monitor - The agent sends periodically via cron system and patchpackage informationdata outbound to PatchMon.
    6. PatchMon
on

Therea isschedule. noNo inbound ports need for any ports to be opened upon your servers.

Network requirements: Agents only need outbound access on theport linux server, however outbound you would need 80/443 to(HTTPS). be opened up. Normally outbound connections are allowed however ifIf your systems are air-gapped or behind firewalls that inspect SSL / SSL/DNS traffic thenor pleaseare amendair-gapped, adjust your rules to suit.accordingly.

Whilst

there
may

Key beFeatures

methodsinensuringupdateshappensuchasutilisingAnsibleorother
Area Details
Dashboard Customisable scripts,per-user card layout with fleet-wide overview
Host ManagementHost inventory, grouping, and OS detail tracking
Package TrackingPackage and Repo inventory, outdated package counts, and repository tracking per host
Agent SystemLightweight GO agents with outbound-only communication connected via Web Sockets
Users & AuthMulti-user accounts with roles, permissions, and RBAC
OIDC SSOSingle Sign-On via external identity providers
API & IntegrationsREST API for managing hosts and data, templates for getHomepage and others available
Proxmox IntegrationAuto-enrollment for LXC containers from Proxmox hosts
BETA - Security ComplianceOpenSCAP CIS Benchmarks and Docker Bench for Security with scheduled and on-demand scans
Docker InventoryContainer discovery and tracking across your hosts
SSH TerminalIn-browser SSH terminal with AI assistance
Extensive ConfigurationConfigurable parameters using .env variables

Architecture

End Users (Browser)  ──HTTPS──▶  nginx (frontend + API proxy)
                                        │
                                        ▼
                                Backend (Node.js / Express / Prisma)
                                        │
                                        ▼
                                   PostgreSQL
                                        ▲
Agents on your servers  ──HTTPS──▶  Backend API (/api/v1)
     (outbound only)
  • Backend: Node.js, Express, Prisma ORM
  • Frontend: Vite + React
  • Database: PostgreSQL
  • Reverse Proxy: nginx
  • Service Management: systemd

Support

inventory
system was needed to provide an advanced insight into Patch status. 

License

"Can it patch my systems?" 

The featurePatchMon is beinglicensed built.under AGPLv3.

It's pretty straight forward for us to build a mechanism that will update the systems but it requires a lot of thought in terms of security and workflows. 

The last thing I want is for someone to press update and it break  a webserver, so there will be policies, rollback options and we want to utilise Ansible for this.

I anticipate that we will get a beta version of patch Management out mid November 2025.

Quick links:

Installation

Roadmap / Issues

Youtube

Key:

Will be linked

Back to top