Pilot engagements are open. A pilot runs KavachQ against a defined slice of your estate — inside your own environment, on the customer-installed appliance — so you can see the discovery, the risk picture, and the migration plan on your own systems before committing to a wider rollout.
We agree the slice of your estate to cover, then work through the first three stages of the lifecycle on it. The scope is set with you up front, not open-ended.
Build the cryptographic inventory for the systems in scope — from certificate stores and CBOM uploads (CycloneDX 1.6) — into a single asset repository.
Flag harvest-now-decrypt-later exposure and apply Mosca-inequality prioritisation against the DST Persona framework (Urgent / Regular / Vendor).
Turn the graded inventory into a phased migration plan, broken down by system, owner, dependency, and supplier, and aligned to the DST milestones.
Each one is a real deliverable from the pilot, mapped to the slice of estate in scope.
A cryptographic bill of materials for the systems in scope, signed with ML-DSA so the inventory you receive is verifiable.
The in-scope assets ranked by Mosca-inequality exposure, so the most urgent migrations are clearly the first ones to move.
A phased plan aligned to the DST milestones — CII 2027 / 2028 / 2029, Enterprise 2028 / 2030 / 2033 — sequenced by system, owner, and dependency.
Critical Information Infrastructure teams working to the compressed CII timeline — foundations by 2027, high-priority migration by 2028, full PQC by 2029. Air-gap-compatible deployment.
Government, financial services, healthcare, insurance, and IT-services teams on the standard timeline — foundations by 2028, high-priority by 2030, full PQC by 2033.
Share a little about the systems you'd want in scope and we'll come back to scope a pilot with you. The more concrete the estate context, the faster we can size it.
Prefer email? Write to demo@kavachq.in.