PatchMon provides centralized patch management across diverse server environments. Agents communicate outbound-only to the PatchMon server, eliminating inbound ports on monitored hosts while delivering comprehensive visibility and safe automation.
- Customisable dashboard with per‑user card layout and ordering
- Multi-user accounts (admin and standard users)
- Roles, Permissions & RBAC
- Host inventory/groups with key attributes and OS details
- Host grouping (create and manage host groups)
- Package inventory across hosts
- Outdated packages overview and counts
- Repositories per host tracking
- Agent version management and script content stored in DB
- Server URL/protocol/host/port
- Signup toggle and default user role selection
- REST API under
/api/v1with JWT auth
- Rate limiting for general, auth, and agent endpoints
- Outbound‑only agent model reduces attack surface
- Docker installation & One‑line self‑host installer (Ubuntu/Debian)
- systemd service for backend lifecycle
- nginx vhost for frontend + API proxy; optional Let’s Encrypt integration
Managed, zero-maintenance PatchMon hosting. Stay tuned.
For getting started with Docker, see the Docker documentation
Run on a clean Ubuntu/Debian server with internet access:
curl -fsSL -o setup.sh https://raw.githubusercontent.com/9technologygroup/patchmon.net/main/setup.sh && chmod +x setup.sh && bash setup.shDuring setup you’ll be asked:
- Domain/IP: public DNS or local IP (default:
patchmon.internal) - SSL/HTTPS:
yfor public deployments with a public IP,nfor internal networks - Email: only if SSL is enabled (for Let’s Encrypt)
- Git Branch: default is
main(press Enter)
The script will:
- Install prerequisites (Node.js, PostgreSQL, nginx)
- Clone the repo, install dependencies, build the frontend, run migrations
- Create a systemd service and nginx site vhost config
- Start the service and write a consolidated info file at:
/opt/<your-domain>/deployment-info.txt- Copies the full installer log to
/opt/<your-domain>/patchmon-install.logfrom /var/log/patchmon-install.log
After installation:
- Visit
http(s)://<your-domain>and complete first-time admin setup - See all useful info in
deployment-info.txt
- Outbound-only agents: servers initiate communication to PatchMon
- No inbound connections required on monitored servers
- Secure server-side API with JWT authentication and rate limiting
- Backend: Node.js/Express + Prisma + PostgreSQL
- Frontend: Vite + React
- Reverse proxy: nginx
- Database: PostgreSQL
- System service: systemd-managed backend
+----------------------+ HTTPS +--------------------+ HTTP +------------------------+ TCP +---------------+
| End Users (Browser) | ---------> | nginx | --------> | Backend (Node/Express) | ------> | PostgreSQL |
| Admin UI / Frontend | | serve FE, proxy API| | /api, auth, Prisma | | Database |
+----------------------+ +--------------------+ +------------------------+ +---------------+
Agents (Outbound Only)
+---------------------------+ HTTPS +------------------------+
| Agents on your servers | ----------> | Backend API (/api/v1) |
+---------------------------+ +------------------------+
Operational
- systemd manages backend service
- certbot/nginx for TLS (public)
- setup.sh bootstraps OS, app, DB, config
- Discord: https://discord.com/invite/6GF9jczKkR
- Email: support@patchmon.net
- Roadmap board: https://github.com/users/9technologygroup/projects/1
- AGPLv3 (More information on this soon)
We welcome contributions from the community! Here's how you can get involved:
-
Fork the Repository
# Click the "Fork" button on GitHub, then clone your fork git clone https://github.com/YOUR_USERNAME/patchmon.net.git cd patchmon.net
-
Create a Feature Branch
git checkout -b feature/your-feature-name # or git checkout -b fix/your-bug-fix -
Make Your Changes
- Write clean, well-documented code
- Follow existing code style and patterns
- Add tests for new functionality
- Update documentation as needed
-
Test Your Changes
# Run backend tests cd backend npm test # Run frontend tests cd ../frontend npm test
-
Commit and Push
git add . git commit -m "Add: descriptive commit message" git push origin feature/your-feature-name
-
Create a Pull Request
- Go to your fork on GitHub
- Click "New Pull Request"
- Provide a clear description of your changes
- Link any related issues
- Code Style: Follow the existing code patterns and ESLint configuration
- Commits: Use conventional commit messages (feat:, fix:, docs:, etc.)
- Testing: Ensure all tests pass and add tests for new features
- Documentation: Update README and code comments as needed
- Issues: Check existing issues before creating new ones
- Fully Managed: We handle all infrastructure and maintenance
- Scalable: Grows with your organization
- Secure: Enterprise-grade security and compliance
- Support: Dedicated support team
- API Development: Custom endpoints for your specific needs
- Third-Party Integrations: Connect with your existing tools
- Custom Dashboards: Tailored reporting and visualization
- White-Label Solutions: Brand PatchMon as your own
- On-Premises: Deploy in your own data center
- Air-Gapped: Support for isolated environments
- Compliance: Meet industry-specific requirements
- Training: Comprehensive team training and onboarding
Contact us at support@patchmon.net for enterprise inquiries
- Jonathan Higson - For inspiration, ideas, and valuable feedback
- @Adam20054 - For working on Docker Compose deployment
- @tigattack - For working on GitHub CI/CD pipelines
- Cloud X and Crazy Dead - For moderating our Discord server and keeping the community awesome
- Beta Testers - For keeping me awake at night
- My family - For understanding my passion
Thank you to all our contributors who help make PatchMon better every day!
- Website: patchmon.net (New website coming soon)
- Discord: discord.gg/6GF9jczKkR
- Roadmap: GitHub Projects
- Documentation: [Coming Soon]
- Support: support@patchmon.net
Made with ❤️ by the PatchMon Team
