ProductProtect it.

KavachQ Gateway

A proxy you run in front of an application. It negotiates hybrid post-quantum key exchange with every client that supports it, so traffic recorded today cannot be decrypted later. The application is not touched.

How KavachQ Gateway works
  1. PlaceRun the container in your network, in front of the application.
  2. RouteOne routes file names each hostname, its certificate and the application behind it.
  3. NegotiateClients that support X25519MLKEM768 get it. Older clients still connect with classical key exchange.
  4. CheckKavachQ probes the public endpoint from outside and signs a record of what it actually negotiated.
What it does

Hybrid key exchange, no application change

For the systems a migration plan cannot reach yet. Core applications, vendor products and old middleware often cannot be upgraded on your timeline. The gateway terminates TLS in front of them and forwards the traffic unchanged.

Gateway

  • Hybrid key exchange (X25519MLKEM768) first, for any client that offers it
  • Classical fallback (X25519, P-256) for clients that cannot do ML-KEM, so nothing stops connecting
  • nginx on OpenSSL 3.5; the image refuses to build on an older OpenSSL
  • A routes change that fails the configuration test is not applied
  • Runs in your network; your certificates and keys stay on your host

Fleet view

  • Every gateway in one list in the KavachQ console, with connection status
  • The hybrid badge comes from an outside probe, not from what the gateway says about itself
  • A gateway that reports hybrid but is observed classical is flagged
  • If the public endpoint changes, the badge returns to “Not verified”
  • Each check is kept as a record signed with ML-DSA-65 (FIPS 204), which you can download and verify offline

Scope today: HTTPS applications behind a public endpoint on port 443 or 8443. The outside check is run on demand.

What you get

Protection now, checked from outside

01 · Protect

Recorded traffic stays private

With hybrid key exchange, a session captured today cannot be decrypted by a future quantum computer.

02 · Keep

No client is cut off

Clients without ML-KEM connect as they do now. Turning the gateway on is not a compatibility event.

03 · Control

It runs on your side

The gateway sends KavachQ a status heartbeat only. That heartbeat carries no application addresses and no certificate or key material, and a KavachQ outage does not affect your traffic.

04 · Check

Observed, signed, yours to keep

Only a hybrid handshake that KavachQ observed on the wire counts as protected. Each check leaves a signed record an auditor can verify without access to KavachQ.

What this does not claim

  • It protects the key exchange. The certificate stays RSA or ECDSA, so authentication is a separate migration step.
  • The signed record covers the key exchange on the public endpoint at the time of the check, and nothing else.
  • It covers the hop from the client to the gateway. The hop from the gateway to the application uses whatever the application speaks.
  • The outside check works on public endpoints. A gateway on a private address cannot be checked from KavachQ today.
  • It is not a VPN, a CDN or a web application firewall.
The products

Four products, one job each

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 →

KavachQ Gateway

Start with one application

Scope a pilot: put the gateway in front of one system and check the result from outside.