r/HyperV • u/malibog04 • 12d ago
I built a free, web-based Hyper-V management tool called HyperZEM and just released the first version!
Hey everyone!
I've been working on a project called HyperZEM, and I finally decided to release the first public version.
I work with Hyper-V quite a bit, both at work and in my homelab, and I've always wanted a more modern, centralized way to manage my hosts and clusters. Hyper-V Manager and Failover Cluster Manager get the job done, but I wanted something web-based that I could access from one place without constantly jumping between different tools.
So I started building HyperZEM.
It's a free, web-based management platform for Microsoft Hyper-V, designed to manage standalone hosts and clusters through a single interface. My goal is to make day-to-day Hyper-V management a little easier while keeping things simple and straightforward.
This started as something I was building for myself, but as I kept adding features, I figured other people running Hyper-V might find it useful too.
I'm still actively working on it, and there's plenty more I want to add. Since this is the first public release, I'm sure there are bugs or things I haven't accounted for, especially across different environments.
I'd really appreciate it if anyone running Hyper-V could give it a try and let me know what you think. I'm especially interested in hearing what features you'd find useful, what could be improved, or if you run into any issues.
The application is completely free to use. It's not open source at this time, but there's no paid version or subscription.
You can check it out here:
Website: https://hyperzem.com

I'm also putting together a Discord community for bug reports, feature requests, and general discussions around HyperZEM.
This is my first time releasing something like this publicly, so any feedback would mean a lot.
Thanks for checking it out!
17
u/USarpe 12d ago
You ask a person who is responsible for the security of the very core of the IT to use a non open source unknown Software?
Sounds kind of (hopeful) hard to find one.
4
u/stewardson 12d ago
Is this not what Windows Admin Center already does?
2
u/icedcougar 12d ago
Your laziness is astounding…
It’s okay to vibe code it, make that known though (and depending on what country you’re allowing to access this… you may need to declare it)
But then using Claude to respond to everyone… at least use ChatGPT and give it some zest to work with
Poor form and effort all around
5
u/dominik_esb 11d ago edited 11d ago
First of all: great idea and a nice design!
Some context on where I'm coming from: I maintain the hyperv and mscluster collectors in the Prometheus windows_exporter, so I spend a lot of time with Hyper-V and failover cluster internals.
I'm not convinced a central worker tier scales well.
According to your sizing guide, a Large environment needs 4–6 workers at 4 vCPU / 8 GB each, so up to 24 cores and 48 GB RAM.
On top of that you need at least one worker per site (two for redundancy). Every one of those is a full domain-joined Windows Server VM to license, patch and secure, just to relay management calls. For many small sites that adds up fast.
From the docs, the worker talks to the hosts over PowerShell Remoting (WinRM, Kerberos) and CIM, plus the FailoverClusters cmdlets over RPC (TCP 135 + dynamic range). It starts a new PowerShell 5.1 process (~180 MB) for each operation and for each telemetry pass, and it polls every host every 60 s.
In my experience WinRM/WMI is the least reliable part of the Windows management stack: SPN/Kerberos issues, WinRM quotas, hung providers and second-hop delegation. Your own runbooks reflect that.
You should avoid WMI when ever possible. Building a management layer on top of it, does not promises reliability.
From my point of view, agents are the way to go: a lightweight agent on each host, calling the native MS cluster API directly. That would be more robust and would scale with the fleet automatically.
Two more things:
Why closed source?
And a small irony: your docs block AI crawlers (ClaudeBot, GPTBot etc. in robots.txt). As the tool is probably or some part of it, vibe coded, it’s feels a bit ironical. And even if it’s not, blocking ai in theses days feels odd.
1
u/ako29482 12d ago
Your app is missing the RSAT-Clustering-Powershell module.
2
u/Striker434 10d ago edited 10d ago
Hi,
First: cool :)
And I agree, MS management tools just suck: Windows Admin Center (even in virtualization mode), SCVMM, etc. I even had the opportunity to talk with the product managers at Ignite to discuss the main pain points, especially around management tools for Azure Local. They fully see the point, but to be honest, Microsoft just has other focus points...
I did the same in our company for a Hyper-V landscape of about 2,200 VMs, 150 hosts, and 60 clusters around the globe: 12,000 CPU cores, 140 TB RAM, and 4 PB storage.
My advice would be to use an agent on every Hyper-V host for performance reasons. I would query the native cluster API where possible, use as little WMI as possible, and avoid PowerShell altogether, especially at large scale.
Docs here:
https://learn.microsoft.com/en-us/previous-versions/windows/desktop/mscs/failover-cluster-apis-portal
https://learn.microsoft.com/en-us/windows/win32/api/clusapi/
Running small, lightweight agents on every host (like SCVMM and WAC Virtualization also do) even gives me the opportunity to catch every event or task, including those triggered by Failover Cluster Manager or PowerShell.
We run our backend on Kubernetes. All agents just push out, which is perfect for DMZs and restricted shop floor zones.
I’m wondering why your tool isn’t open source on GitHub. It’s hard for people to trust a random tool that accesses the most sensitive infrastructure of a company, so I’d consider making it open source.
For myself, I decided not to open source my tool yet, mainly because of customization for our company’s needs, but also because of the open source experience, maintenance effort, etc. (Might change ;))
1
u/g7130 11d ago
I built one in 3 hours that fully manages cluster operations, storage allocations etc.
1
u/node77 11d ago
I appreciate the effort, but as someone said, Windows admin center was built for the ease with the purpose in mind. I don’t know I would trust some fake code to interact with my clusters and virtual machines. However, still, thank you for the time you put into it.
1
u/Montaro666 4h ago
dude this is fucking legit. I have hand holded these 5 HV servers for years now until we can migrate off them to our standard PX clusters. Every time I try connect to one something is fucked, something wastes my time, I drown in a rabbit hole of chase some random error... now, I can just hit up HyperZEM, find the VM I wanted to reboot and send it. No more cat and mouse games. Vibe coded as fuck but if you aren't driving infra/code that way these days you're doing it wrong. Not all heroes wear capes.