PatchMon Community edition
Production patch management, open source under AGPLv3.
Run PatchMon on your own infrastructure under AGPLv3. Today's Community edition includes patch monitoring, patch deployment, compliance scanning, remote access, Docker monitoring, alerting, RBAC, and reporting, managed entirely by you unless you engage PRO for support, training, or deployment help.
Prefer managed? Start a Cloud trial instead.
Why open source matters for infrastructure tools
Inspect the Code
Security tools should be auditable. Read every line, verify every network call, and confirm that PatchMon does exactly what it says - nothing more.
Own Your Data
Self-hosted means your patch data stays on your infrastructure. No third-party cloud, no telemetry, no data leaving your network without your explicit action.
Your Infrastructure, Your Rules
AGPLv3 lets you run, modify, and distribute PatchMon. Keep the platform close to your infrastructure if that is what your architecture or compliance posture requires.
Community-Driven
Bug reports, feature requests, and contributions come from people running PatchMon in production. The roadmap is shaped by real operational needs.
Extend and Integrate
Build custom integrations, modify the agent for your environment, or contribute features back. The codebase is structured for contributions.
Cross-Platform Agents
The agent builds for Linux (amd64, i386, arm64, arm), FreeBSD (amd64, i386, arm64, arm), and Windows (amd64, i386) - 10 binary variants. ARM support is real, not theoretical.
What's in the Community edition
The Community edition is a full-featured control plane you can run end-to-end on your own infrastructure today. Cloud adds managed hosting, automatic updates, scheduled backups, regional data residency, and tiered support. PRO layers on deployment architecture, training, priority engineering access, and custom development for teams that want expert hands on their setup.
Get started in minutes.
Production installs use the published Docker Compose files from GitHub (PostgreSQL 17, Redis 7, PatchMon server, and guacd for browser RDP). Here's the recommended path: the same flow documented in the PatchMon Docker directory.
1. Run the setup script and start the stack
From an empty directory, the script downloads docker-compose.yml and env.example, generates required secrets, and walks you through URL and timezone. Then start the services:
mkdir patchmon && cd patchmon
bash -c "$(curl -fsSL https://raw.githubusercontent.com/PatchMon/PatchMon/refs/heads/main/docker/setup-env.sh)"
docker compose up -dPrefer manual steps or pinning image tags? See docker/README.md (including ghcr.io/patchmon/patchmon-server tags and updates).
2. Open the dashboard and complete setup
Open the URL you configured (default: http://localhost:3000) and finish the first-time wizard to create your admin account.
3. Install an agent on each host
In PatchMon, open Hosts → Add host, copy the install command, and run it on each machine you want to manage.
Contributions welcome.
PatchMon is built in Go (server + agent) and React (frontend). Whether it's a bug fix, a new feature, documentation improvements, or distribution-specific packaging - we welcome pull requests.
Want it managed or need expert help?
Cloud runs the platform for you with managed hosting, backups, and support. PRO brings in our engineers for deployment design, training, and priority access.