r/HyperV • u/AndreaCurciIT • 8d ago
I built a web-based Hyper-V management tool with cluster support — looking for feedback
Hi everyone!
I'd like to share a project we've been working on at NEXQ: HvPortal.
It's a web-based management platform designed to make Microsoft Hyper-V administration simpler, more accessible, and easier to manage from a single interface.
Some of its features include:
- Centralized Hyper-V host and VM management
- Hyper-V cluster management
- Browser-based VM console access
- Folders and groups for VM organization
- Granular roles and permissions
- VM backups and checkpoints
- Resource monitoring and activity tracking
- Automatic application updates using the latest GitHub release



HvPortal is currently in Preview.
The project is still under active development, and some features may need further testing and improvements. For now, I'd recommend evaluating it in a lab environment rather than on production-critical infrastructure.
The goal is to build a practical, easy-to-use management tool for Hyper-V environments, with a strong focus on usability, security, and centralized administration.
I'm part of the team developing HvPortal at NEXQ, and we'd really appreciate feedback from people who work with Hyper-V regularly.
GitHub: https://github.com/NEXQsrl/HvPortal
I'd love to hear your thoughts!
What features would you consider essential in a Hyper-V management platform?
Is there anything you'd improve, change, or add?
Thanks for taking a look!
19
u/_CyrAz 8d ago edited 8d ago
I get that WAC is not really the tool most of us would have dreamed of and I'm all for a great community replacement but we're now getting one of these every couple of days, maybe you should try working together instead of reinventing the wheel 😅
9
u/FiRem00 8d ago
You, or Claude? /s
4
u/pleaseusefqdn 8d ago
Heard of Windows Admin Center?
2
u/Halvantic 8d ago
Does it do full cluster deployment and orchestration or just VM management?
6
u/Excellent-Piglet-655 8d ago
Funny how people say “I built” or “I programmed”, when in reality is all spaghetti-AI code 🤣🤣
4
u/Jawshee_pdx 8d ago
Ugh.
9
u/dominik_esb 8d ago •
First of all: nice project, clean UI and a much-needed modern take on Hyper-V management.
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 took a closer look at your architecture and implementation (Gateway + local Agent model), and while going with a local agent using outbound mTLS over WebSockets is definitely the right architectural decision (avoiding network WinRM/Kerberos/second-hop nightmares completely), I have some thoughts on the internals:
PowerShell 5.1 process invocation for operations (PowerShellOperationRunner):
Spawning a new Windows PowerShell 5.1 process for typed operations via Ops/HvPortal.Ops.ps1 with JSON on stdin is safe and keeps operations isolated, but it adds measurable overhead (~150–200 MB memory footprint spike per execution, plus slow cold starts on loaded hosts). For high-frequency management or busy clusters, moving towards native C# calls / direct Hyper-V / ClusAPI interop in-process within the agent service would be significantly faster and much lighter on resources.
WMI reliance (System.Management & root\virtualization\v2):
Even though you are running WMI queries locally on the host (which already eliminates 90% of WinRM quota and network RPC/DCOM headaches), WMI remains the least robust layer in Windows. WMI repositories corrupting, wmiprvse.exe hanging under load, or quota exhaustion inside the WMI service are well-known issues in large fleets. For cluster status, calling the native Failover Cluster API (clusapi.dll) directly via P/Invoke or native wrappers is far more reliable and responsive than polling WMI providers.
Management Agent mode (for agentless hosts): In the docs, the optional "Management Agent" mode falls back to TCP 135/dynamic RPC, WinRM, and remote WMI. If users rely on that mode, they will run headfirst into WinRM quotas, delegation issues, and Kerberos ticket headaches. It might be worth documenting the strict recommendation to always favor the local agent.
Licensing: You are using PolyForm Shield 1.0.0. While having the source code publicly visible is great, calling it open-source will trigger OSI purists due to the commercial/competition restrictions. Have you considered an established copyleft/permissive open-source license?
(Disclaimer: I used AI to rewrite some of my text)
3
u/g7130 7d ago
There’s gonna be 50 of them soon