Evaluation
Thirty days, read-only, your real estate
Install it, point it at what you already run, and see what your current tools have not been telling you. Nothing is changed and nothing is required of your clients.
What it does
Full platform, every module, on your hardware, against your real clients. It reads — it does not act, does not remediate, does not touch a configuration and does not open a ticket in anything you already run.
Read-only means read-only. Every write path is closed at the chokepoint, not by a setting somebody could change. The evaluation cannot alter your estate even if you ask it to.
What you will see in the first week
- Patches your tool reports deployed that are not on the machine
- Backups reported successful that have never been restore-tested
- Agreement quantities that stopped matching the live count, in dollars
- Assets under management that nobody is billing for
- Machines that drifted from your own standard
- Coverage gaps — what you think is monitored and what is actually reporting
Most evaluations find unbilled work inside a fortnight. We do not promise a figure, because we do not know your estate — but we can tell you it is the finding MSPs mention first.
What happens at day thirty
It freezes. It does not delete, does not wipe, and does not hold your data hostage.
| At expiry | |
|---|---|
| Your data | Stays where it is, on your hardware, readable |
| Findings | Remain visible |
| Collection | Stops |
| Converting | A licence state change — no reinstall, no migration, no re-discovery |
| Walking away | Uninstall. Nothing phones home, nothing lingers, nothing to cancel |
An extension is a conversation, not a self-service loop. If thirty days was not enough, tell us why and we will usually extend it.
What we receive during the evaluation
Ten fields and a signature. No client names, no hostnames, no addresses, no telemetry, no usage analytics.
You can read the record before it is sent. The full field contract is published.
What we ask of you
- A host that meets the sizing requirements
- Read credentials for what you want assessed
- About an hour to install and point it at a client
- Nothing from your clients — they never see it and are never contacted
No card required. You are not enrolled in anything and there is nothing to cancel.
What your account gives you — a bill you can recompute, support that has read your version, and ten fields is all we receive. Your account.
And one thing comes back to us, once, at the end
When the evaluation finishes, a summary of what was found is sent to us. Not the report — a summary. It happens once, automatically, and never again. We are telling you before you start rather than in a document you would have to go looking for.
What goes: how many findings there were and of what kind, the consequence figures, your asset count and how much of it we could see, and the dates.
What never goes: any of your clients. Not a name, not a hostname, not an address, not a serial, not which client any count belongs to. You asked for this evaluation. Your clients did not ask for anything — and the fact that you evaluated a platform is not their consent to be in our database. There is no field in what we receive that a client could live in.
You can read exactly what was sent, byte for byte, on your own console afterwards. Not to approve it — to check it.
This is not the same as the ten fields. Those are what a paying deployment sends continuously to be billed. Both are set out here, and we keep them apart on purpose — reading one as the other would mislead you either way.
Why thirty days, and who the findings go to
Thirty days is not a sales window. It is how long it takes to see a patch cycle, a billing period and enough telemetry for a trend to mean anything. A fortnight would find fewer things and prove less, and we would rather show you more.
The findings go to whoever asked for it, and to the owner. Not because we want a second reader — because the person who installs a platform and the person who decides whether to keep it are usually not the same person, and a report that reaches only the first one dies there.
You choose the second name at signup. Leave it blank and only you get it.
The findings are dated and they expire. A gap we found in September is a gap as it was in September — we will not let a stale report be quoted as a current one.
What comes back to us at the end, and what does not
When the evaluation ends, a summary of what was found is sent to us. Once, and never again. We are telling you here rather than in a document you would have to go and read, because it is the sort of thing that ought to be on the page you start from.
It carries counts — how many findings, of what kind, the figures beside them, how many assets were observed and how many were not, and the dates. That is the whole of it.
It carries no client name, no hostname, no address, no serial and no content of any document. Not because we filtered them out — there is no field in the message they could sit in.
The reason is not your privacy. It is your clients'. Northwind Manufacturing never signed up to have their name in a vendor's database, and the fact that you evaluated a platform is not their consent.
You can see exactly what was sent, byte for byte, on your own console afterwards. Not to approve it — to check it, which is the standard we hold everywhere else.
The full report — the one with your clients, your machines and the evidence behind every figure — stays on your deployment and is never transmitted. We could not write it. We do not have the data.
See what it costs
$6 USD per managed asset, every module included, and the AI is never metered. Or rent the appliance from $650 USD a month.