Roadmap
19 of 19 shipped- Phased P0 / P1 / P2 plan with the algorithm choice for each asset
- DST and NQM deadlines, harmonised with global ones
- Budget model and vendor-blocked tasks
- Push to Jira and ServiceNow, with two-way status sync from Jira
Migrate turns findings into a dated plan, then makes the change with a named approver and a tested way back.
Plan the move, then make it — with your approval. Migrate turns Discover's findings into a dated plan, then makes the change with a named approver and a tested way back.
Scope today: Migrate changes TLS terminators (nginx, HAProxy, Apache, ACME). It does not rewrite application code or touch OT.
Counts are capabilities in KavachQ's capability register (30 October 2026). An Envoy change generator is planned and not built yet.
P0, P1 and P2 work with the replacement algorithm for each asset, set against your DST and NQM deadlines and the global ones.
A budget model in engineer-days, with the tasks that are waiting on a vendor called out.
By default you receive the change pack and your team applies it. KavachQ can also apply it over SSH, after a named approver signs off and with a rollback tested first.
After a change, the endpoint is probed again to confirm hybrid post-quantum TLS is actually in effect.
In the console: Kavach Copilot — ask the regulation or explain a finding. Answers come from the verbatim text of Indian regulators (RBI, SEBI, CERT-In, DST/NQM, IRDAI, TEC), and each claim is checked before it is shown. See the whole platform →
Scope a pilot: inventory a slice of your estate, then get the phased plan for it.