Bound the surface
Choose the decoys, tenants, networks, retention window, and systems that remain explicitly out of scope.
Design-partner pilots
Price the boundary before pricing the traffic.
HNPT is in early access. Pilot scope and pricing are designed around the protected surface, deception packs, evidence retention, response model, integrations, and verification burden—not a surprise counter after an incident.
A pilot should be easy to stop safely.
Every engagement begins with success, rollback, export, retention, and teardown criteria.
Define the response
Agree on evidence thresholds, challenge rules, quarantine blast radius, expiry, reviewers, and release policy.
Prove the integration
Test identity failures, duplicate delivery, degraded dependencies, rollback, and teardown before production exposure.
Get ready
Bring the threat model. We will bring the wrong doors.
Organization onboarding will open through the protected organization application when the service ingress is verified.