Try the HVPane demo

What you are looking at

The product, pointed at a company that does not exist.

The demo is HVPane with a synthetic estate where yours would be. The views, the actions, the roles and the editions are the ones a real installation has; only the estate is invented. Every host, cluster, site and person in it is fictional.

It is yours alone while you use it. Changes stay in your browser and reset when you reload — so drain a node, delete a checkpoint, patch a cluster. Reload, and the estate is back the way you found it.

The companyVellmoor Ltd (demo) — fictional
The estate36 hosts · 9 clusters · 11 sites
The dataSynthetic — nothing here is a real customer’s data
Your changesStay in your browser — and reset when you reload
Signing inDemo accounts — listed below, one shared password

What you can try

Start with the question you would ask on a Monday.

Grouped by the question each one answers, the same way the product page is. Every one of these is on the demo’s own menus, reached the way a customer would reach it.

What needs you now

Where the demo opens, and where to start.

Overview

Every issue across the estate, ranked, each with its next step. Look for the machine sharing a node with its anti‑affinity partner.

What changed since the last run

New and resolved issues, machines added and removed, migrations, hosts rebuilt.

Diagnostics

What could not be read this run, and why — stated, not quietly left out of the totals.

The demo's Overview: seventy issues across thirty-six hosts and nine clusters, ranked by severity, each with its next step. — **The first screen you will see after signing in.** The severity tiles filter the list; every row links to where you can act on it.Demo estate · synthetic data, not a customer’s

Will it hold

Somewhere in the demo is a cluster that would not survive losing a node. Find it.

Capacity, with N‑1 headroom

Not what is used — what still fits when you lose a node, for every cluster.

Trends and forecasts

Days until a cluster crosses 90% memory or a volume fills. The demo comes with synthetic history; trends are built from history, and a new installation starts empty and fills in over its first days.

Placement

Anti‑affinity, preferred owners, and clusters out of balance.

The things that rot quietly

Nothing alerts on these. In the demo, as in life, they are already there.

Checkpoints nobody deleted

Age, data held, and who created each one — or unattributed, where nobody can prove it.

Configuration drift

The node‑by‑node matrix per cluster, and the host set up differently.

Storage, to the VHD chain

Volumes, ownership, and the differencing disks hanging off forgotten machines.

The demo's Checkpoints view: sixty-three checkpoints with age, size and the account that created each one. — **Sixty‑three checkpoints, the oldest 198 days.** Pick a few and delete them as a group — the reason you give lands in the audit log.Demo estate · synthetic data, not a customer’s

Then act on it

The actions run against the demo estate, and the page updates when they finish.

Run an action

Start, stop, migrate, drain a node, patch a node or a cluster — from the row where you found the problem.

Schedule it

Set a disruptive action to run at a time of your choosing and watch it wait in the queue.

Read the audit

Who ran what, where, and why — including everything you just did.

Who may do what

Two demo controls that show what the real product enforces.

Try a role

Sign in as operator, support, OT, security or a site‑scoped role, and see the menus, actions and downloads change with it.

Try an edition

Switch between Community, Standard, Professional and Enterprise to see what each one unlocks. Community is read‑only. Free to read every host you own.

Signing in

Five demo accounts. One password.

The demo opens on a sign‑in screen. Click an account to go straight in, or type it. These are demo accounts — any visitor can use them, and they protect nothing. A real installation signs you in with your Windows account.

Account	Role	What it shows
`demo.operator`	Operator	Everything: every view, every action, and the administration pages.
`demo.support`	Support	Virtual machine control and checkpoints — the day‑to‑day support desk.
`demo.ot`	OT	Three views and basic virtual machine control. No downloads.
`demo.security`	Security	Every view, read‑only. Nothing can be run.
`demo.ashcombe`	Site‑scoped	One site, Ashcombe — a custom role that sees and acts on that site alone.

Password for every account HVPane-demo

Sign out to return to the sign‑in screen and try another role. The edition control stays available after you sign in.

Where the demo stops

The data is invented. The features are not.

Everything you can click is something the product does. A few things need your own machines, and the demo says so rather than pretending.

No console sessionThe console connects to your machines in a real installation; it is not available in this demo.
Not your estateThe demo shows Vellmoor, not your hosts. Seeing your own estate takes an installation — ask us about early access.
History is suppliedTrends are built from history; a new installation starts empty and fills in over its first days.
Nothing is keptChanges stay in your browser and reset when you reload. Close the tab and it is gone.

An estate you are allowed to break.