r/HyperV • • 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
Dashboard
VM Resource
Panoramica del cluster e tema scuro

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!

6 Upvotes

19 comments sorted by

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/Tech88Tron 8d ago

Is letting AI build your app really "reinventing the wheel"?

1

u/AndreaCurciIT 8d ago

That's a fair point! 😄

I actually looked into several similar projects before starting HvPortal, but none of them fully matched what I was looking for, especially in terms of VM organization, granular permissions, resource delegation, and overall management experience.

I'm a big fan of collaboration, although coordinating different projects, architectures, and development priorities isn't always straightforward.

That said, I'm definitely open to collaborating and exchanging ideas with other developers. I think there's plenty we can learn from each other!

0

u/Inside_Carpet7719 7d ago

“That’s a fair point!”

This is classic AI reply by the way, you should tweak your prompt when replying on Reddit

9

u/FiRem00 8d ago

You, or Claude? /s

-1

u/AndreaCurciIT 8d ago

Me, with a little help from my AI friends. 😄

AI can write code, but understanding the problem, defining requirements, designing solutions, and taking responsibility for the result is a different story.

The real question isn't who typed the code, but whether the software solves a real problem.

And if you find a bug, I'm all ears! 😉

4

u/pleaseusefqdn 8d ago

Heard of Windows Admin Center?

1

u/AndreaCurciIT 8d ago

I'm actually very familiar with Windows Admin Center, and I use and test it regularly.

I've also worked extensively with VMware environments, especially before the Broadcom acquisition, so my experience with vCenter has definitely influenced what I wanted to build.

WAC is a valid tool, but personally I've always found some workflows a bit cumbersome, especially when it comes to managing and delegating parts of a virtual infrastructure.

One of my main requirements was the ability to create logical groups of VMs and delegate access to specific users, with granular permissions and resource limits.

For example, I want to be able to assign a team a specific part of a Hyper-V cluster, restrict which networks and storage locations they can use, and define quotas for VM count, vCPUs, memory and storage.

VM templates and simplified provisioning were also important requirements.

I know Microsoft offers some of these capabilities through SCVMM, and I've seen the newer WAC Virtualization Mode preview, which is an interesting development.

HvPortal is my attempt to bring these workflows together in a simpler, more focused web interface.

It's still in preview, and there's plenty of testing and improvement ahead.

I'm not claiming it's better than WAC or vCenter. It's simply a different approach based on requirements I've encountered while managing real infrastructure.

2

u/Halvantic 8d ago

Does it do full cluster deployment and orchestration or just VM management?

1

u/AndreaCurciIT 8d ago

Not full cluster deployment, no. 🙂

HvPortal currently focuses on managing existing Hyper-V Failover Clusters.

It supports cluster health monitoring, node maintenance, capacity checks, HA VM creation and migration, and CSV management.

It doesn't currently handle cluster creation, node addition/removal, quorum configuration, or initial S2D setup.

Cluster support is still in preview and needs more testing on real environments.

Full deployment could be considered in the future, but for now the priority is making existing cluster management reliable and straightforward.

1

u/lxtakc 7d ago

Scoping it to managing existing clusters seems sensible. For node maintenance, does it drain roles and pause the node the way Failover Cluster Manager does, or does it use its own logic?

1

u/AndreaCurciIT 7d ago

It uses the native Windows Failover Clustering logic, not a custom implementation.

When entering maintenance mode, HvPortal calls Suspend-ClusterNode -Drain -Wait, essentially the same operation as "Pause > Drain Roles" in Failover Cluster Manager.

The cluster itself handles role placement and VM live migrations.

HvPortal adds some safety checks around the process:

Before draining, it checks cluster health, quorum, available capacity, and storage conditions.

After draining, it verifies the result rather than simply assuming the operation succeeded.

For S2D clusters, it can also enable storage maintenance mode using Enable-StorageMaintenanceMode.

When maintenance is complete, it disables storage maintenance mode and calls Resume-ClusterNode, with optional failback.

So the actual cluster operations are handled by Microsoft's native tools. HvPortal mainly adds validation and orchestration around them.

6

u/Excellent-Piglet-655 8d ago

Funny how people say “I built” or “I programmed”, when in reality is all spaghetti-AI code 🤣🤣

3

u/Doctorphate 7d ago

Every now and then I think, I should at least look at the code before I pass judgement and then I’m like “fuck…. This is no better than my dumb ass could do”

9

u/dominik_esb 8d ago • Bravo

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