How it is built
The decisions behind the product, stated so you can hold any tool, this one included, to them.
Verdicts
in words
what is wrong and why, with the row it names
Empty vs could-not-read
always apart
a blank panel says which it is
APIs
the product's own
NITRO, XenAPI, WUA, the Hyper-V cmdlets
Install
one VM
nothing in the cloud, nothing on the appliances
Read and manage
sold apart
start reading, add control later
Eight decisions
- A verdict, not a graph. Every pair, pool and server says what is wrong and why, in words, and the reason opens the row it names. The Analyze verdicts (why did it restart, why did it fail over, is anything climbing) come with their confidence and with what would settle them, and say when they are an estimate rather than a fact the appliance stated.
- Empty is not the same as could-not-read. Anywhere a panel can show nothing, it says whether it asked and there was nothing, or could not ask, and why. This is the defect most monitoring tools ship and the one that costs the most at 2 a.m.
- Parsers are written from captures, not from documentation. Every line that reads an appliance's output was written against verbatim output from a real one, and a shape that has not been seen is asked for, not guessed. Where the product has an API, the API is used instead: NITRO for NetScaler changes, XenAPI for pools, the Hyper-V module for hosts, the Windows Update Agent for updates.
- A pair is one thing. NetScaler HA pairs and XenServer pools are atomic units: both nodes' clocks, one verdict, one category move.
- One install, nothing in the cloud. A Windows Server VM on your network; nothing on the appliances; one small agent per Windows server. The portal is contacted when you press a button, and the one timed contact is opt-in.
- Reading and changing are sold apart, and behave apart. The reading modules never write. A management module adds specific, confirmed, audited actions, in the system's own API, as the signed-in operator, with a separate read-write account where the appliance needs one.
- Security by construction, not by setting. No operator password stored, no TLS bypass switch, certificates pinned before a credential is sent, the agent not an administrator. There is no configuration in which the product is less safe than the page describes.
- Honest words on the page. When a reading is from the last poll rather than live, the panel says so. When a feature is product knowledge rather than a tested capture, the docs say so. When something is not built, this site says so.
What to ask any vendor, us included
| Ask | Our answer |
|---|---|
| Where does my data go? | Nowhere. It stays on the VM you installed; see Security. |
| What runs on my appliances and hypervisors? | Nothing. Reads over SSH, NITRO and XenAPI; one agent per Windows server, not an administrator. |
| When a panel is blank, what does it mean? | It says: nothing found, or could not read, with the reason. |
| How are changes made, and by whom? | In the product's own API, as the signed-in operator, confirmed first, audited after; only where the management module is licensed. |
| How is it licensed? | Per module and unit, verified offline, bound to the installation; see Pricing. |
| How do updates reach it? | When an administrator asks, from the portal, SHA-256 checked, applied by a system task with backup and rollback; or by hand from the zip. |
| What does it not do? | No PSA integration, no multi-tenant instance, no fleet push of updates today; all stated on the pricing page. |