Proof in 30 days. On your environment, against your audit.
A scoped, time-bound pilot of CybrIQ on one of your buildings, one floor, or a single conference-room cluster. Day 1 through Day 30, with the inventory, drift baseline, and an audit-defensible evidence pack delivered before the pilot closes. No multi-year commitment. No long sales cycle. A clean answer, on a clean timeline.
What happens, day by day, week by week.
The pilot is structured so each phase ends with an artifact your team can use independently. If the pilot stops at Day 14, you keep what was delivered through Day 14.
Scope and stage.
A 30-minute working session to lock the pilot scope (one building, one floor, one room cluster, or a hybrid). The customer (or their integrator partner) provisions the appliance hardware to the supplied spec; on-site placement is typically completed within the first business week.
First inventory.
Device DNA™ runs against the pilot scope. By Day 7 you receive the initial inventory, the count of devices that did not match the asset register, and the first set of drift events flagged for review.
Drift baseline.
Continuous validation runs through the second and third weeks. Drift events are triaged with your operations team. The signal-to-noise of the alert stream is tuned against your change-management cadence so it lands cleanly inside the SOC.
Evidence pack.
An audit-defensible evidence pack is delivered, scoped to the pilot environment and mapped to your active framework (SOC 2, HIPAA, PCI 4.0, NIST CSF, or CMMC). This is the artifact your audit team can take into the next cycle.
Three deliverables, one timeline.
- A real Layer 1 inventory of the pilot scope. Per-device, per-port, with Device DNA™ fingerprints and the first thirty days of drift history dated against it.
- A drift baseline tuned to your environment. Alert thresholds set against your actual change cadence, signal-to-noise calibrated for the SOC, integration patterns ready for SIEM/XDR/ITSM hand-off when the pilot converts.
- An audit-defensible evidence pack. Pre-mapped to your framework of record, structured for the auditor to take at face value, dated to the pilot period.
Whether you convert the pilot into a paid deployment is your call at Day 30. The deliverables above are yours either way.
Who picks the pilot scope.
You do. The shape that almost always works best is one of three:
- A high-stakes building. Headquarters, executive floor, or a campus that owns most of the audit risk. The deliverables defend this environment first.
- A pre-audit window. A floor or room cluster scheduled into an audit fieldwork period. The pilot's evidence pack feeds the audit directly.
- A reference site for a partner. For AV integrator partners running their own customer pilot. The integrator owns the relationship; CybrIQ runs alongside.
What the pilot costs and what it requires.
The pilot is no fee. CybrIQ provides the platform license, the scoped deployment work, and the three deliverables described above at no charge. The pilot scope (room count, building count, port count) is confirmed during the scoping session.
The customer provides the appliance hardware in all cases. CybrIQ provisions the platform image; the customer or their integrator partner sources the underlying hardware to the supplied spec. Reference hardware specifications are documented in the deployment guide and shared during scoping.
The deliverables are yours to keep regardless of whether the pilot converts to a production deployment.
30 days, one environment, three deliverables.
Tell us which environment, and which audit window the deliverables need to land before. Scoping happens in the first 30-minute working session.