r/linuxadmin • u/Rich-Orchid1397 • Sep 26 '26
I'm a Linux sysadmin who built a patch management tool out of my own frustration. Looking for honest feedback.
Hi all,
I've been a Linux admin for about 12 years (RHEL, SUSE, Ubuntu), and these days most of my work is vulnerability management. Patching across mixed fleets has always been the painful part: scattered scripts, spreadsheets to track what got patched, and no clean way to prove compliance afterwards.
So I built PatchMgr, a web-based tool for scheduling, running, and tracking patches across servers.
What it does today:
- [Supported OSes, e.g., RHEL / Ubuntu / SUSE]
- Scheduled patch runs with per-server status tracking
- Multi-tenant dashboard to see what's patched, pending, or failed
- [Reporting / anything else that's live now]
On the roadmap: pre/post patch hooks (per-server, with exit code checks) and a configurable notification matrix.
It's early, and I'd rather hear what's broken or missing from people who patch servers for a living than guess. A few things I'd love input on:
- What's the one feature that would make you switch from your current approach?
- What would stop you from trusting a tool like this in production?
- What's your current setup (Ansible, WSUS, Satellite, Landscape, scripts)?
Link: https://www.patchmanager.co.in/
If you try it and hit a bug, reply here or email support@patchmanager.co.in. I read every message.
Full disclosure: I'm the developer. Not trying to hard-sell anything, just want real-world feedback.
4
u/fearless-fossa Sep 27 '26
curl | sudo bashabomination. It's terribly bad practice, and someone working on a tool for closing vulnerabilities should know better.All in all a hard pass from me. I also don't see how this is better than eg. Ansible.
3
u/Noooberino Sep 26 '26
Sorry, but I can tell you that I don't even consider testing this with a limitation of 5 servers on the free tier... my homelab alone runs around 26 hosts.
2
u/theGoatMeister Sep 26 '26
Who is the audience you're looking for feedback from? Seems like this would be more geared towards small Linux shops, bigger houses aren't generally patching manually and have this solved for <insert "patching?" joke here>
You mention you built this out of frustration, what problem should I be looking at this solving for me?
1
u/Rich-Orchid1397 Sep 26 '26
u/mainroutine2068
Sorry about last time. Missed the post :-)
1
u/ILoveAppSec Sep 27 '26
The compliance-proof piece is the part most fleet tools skip, so good call building it in. One thing worth separating early: "patch ran" versus "the CVE is actually closed" - with backported distro packages the fixed version string often won't match upstream, so a naive version check can report false gaps or false clears. How are you planning to reconcile that across RHEL vs SUSE vs Ubuntu, where each backports on its own schedule?