HVPane was not designed for a market. It was built because the morning walk around a Hyper-V estate — thirty-five sites, seventy-three hosts, four hundred and twenty-five machines — had stopped fitting into a morning.
Where it came from
Open a console. Pick a host. Look at the checkpoints. Close it. Pick the next host. Somewhere around the fortieth one you stop being thorough, and the thing you stopped being thorough about is the thing that wakes you at two in the morning.
None of the individual checks are clever. Checkpoint age. Whether a cluster still fits if you lose a node. Which host somebody set up differently in 2023. The difficulty was never knowing what to look at — it was that looking at all of it, everywhere, every day, is not work a person can do reliably. So it got written down, then scripted, then it became this.
The estate in that first paragraph is a real one, and it is where HVPane still runs every day. It is proof, not a ceiling — there is no host limit on reading, on Community or on any paid edition.
That origin is also the reason for the shape of the thing. It answers the question an operator actually asks — what, across everything I run, needs me today? — rather than the question a dashboard usually answers, which is how is this one host doing right now? What it does covers that in full.
Somewhere around the fortieth host you stop being thorough. That is the one that wakes you at two in the morning.
Why it got written
Who we are
There is no venture round behind this and no sales organisation in front of it. You are reading the website of a company you can look up.
Being small is a fact about us, not a claim about our quality. It buys you a short line to the person who wrote the thing, and it costs you the reassurance of a large name on the invoice. You should weigh both, and the next section is the part you would otherwise have to ask about in a meeting.
The fair question
It is the right thing to ask a young company before you put it near your infrastructure. Three answers, and none of them require you to trust us.
Hyper-V runs your virtual machines. HVPane reads them and, on a paid edition, acts on them. It is not in the path of anything running. Remove it tomorrow and your estate carries on exactly as it is.
It is self-hosted. No cloud account, no tenant, no licence server phoning anywhere, no telemetry. We could not degrade your installation from here even if we wanted to, because we are not connected to it.
Every run writes plain files — the page you read, the underlying tables, the history the forecasts are drawn from. They sit on your server, in formats anything can open, whether or not this company exists.
The security page is where that boundary is written out properly, including what a lapsed licence does and does not take away from you.
How we write
They exist because we are selling to people who have been sold to badly, by vendors whose datasheets win every row.
The longest-standing of these is the comparison itself. Why HVPane exists exists to make the argument in public, with the losing rows left in.
HVPane is in development and there is no public download yet. We are looking for a small number of people who run real Hyper-V estates to use it early and tell us where it falls short — particularly the parts that only break at a size we cannot reproduce.
If that is you, the estate you run is worth more to us than anything we could write here.
Tell us what you run. We read every one of these.
The security page says what to include and what happens next.
Formed 5 September 2026. A registered Texas company, not a side project with a landing page.