- Home
- Pilot
Proof in thirty days, against your own audit.
One building, one floor, or a single cluster of rooms. The inventory, the drift baseline and an audit-defensible evidence pack, all delivered before the pilot closes. No multi-year commitment and no long sales cycle.
Every phase ends with something you keep.
Stop on day fourteen and you keep everything delivered up to day fourteen.
- Day 1
Scope and stage - A 30-minute session to fix the scope: one building, one floor, one cluster of rooms, or a mix. Then you or your integrator install the scan engine to the supplied spec. That usually happens inside the first working week.
- Week 1
First inventory - By day seven you have the initial inventory, the count of devices that did not match your asset register, and the first drift events flagged for review. The gap between those two numbers is usually the moment the room goes quiet.
- Weeks 2 and 3
Drift baseline - Continuous validation runs while your operations team triages what it finds. Alert thresholds are tuned against your real change cadence, so what reaches the security team is worth their attention.
- Day 30
Evidence pack - An evidence pack scoped to the pilot environment and mapped to whichever framework you are audited against. This is the artifact your audit team takes into the next cycle.
What you walk away with.
Per device, per port. The fingerprint travels with it, and so does the first thirty days of drift, dated.
Thresholds set against your own change cadence. The integration patterns come ready to hand off.
Mapped to your framework of record before the pilot starts. An auditor can take it at face value, and it is dated to the window it covers.
For scale: on one hospital campus, six weeks of audit preparation became four days. That engagement, in full.
Whether the pilot becomes a deployment is your decision on day thirty, and the three things above are yours whatever you decide, because each one is useful without the others.
Which part of the network.
- A high-stakes building. Headquarters, an executive floor, or the campus carrying most of the audit risk.
- A pre-audit window. A floor or cluster already scheduled into fieldwork, so the evidence pack feeds the audit directly.
- A partner reference site. For integrators running a pilot with their own customer. You own the relationship; we run alongside.
What it costs, and what it needs.
There is no fee for the pilot. We provide the license, the scoped deployment work and the three deliverables. The scope, meaning the room, building and port counts, is agreed in the scoping session.
You supply and install the scan engine on your own compute, and your network team issues the read-only credentials it uses. Nothing changes on the switches. The whole thing backs out in minutes.
Bring the building you would least like to be surprised by.
That is the one worth thirty days.