All systems operational.
Live connectivity and latency for Manav core endpoints, measured directly from your browser. Manav receipts are cryptographically signed with published Ed25519 and NIST FIPS 204 ML-DSA-87 keys, so offline verification never depends on central server uptime.
Component health.
The offline-first guarantee.
Why receipt verification does not depend on server uptime
Most identity and risk services place a proprietary API synchronously in your hot path: if their server has an outage or high latency, your application breaks. Manav is designed as an open cryptographic protocol, not a gatekeeper.
When an action is authorized, Manav produces a self-contained receipt signed with dual keys: Ed25519 and ML-DSA-87. Any system can cache our public keys published at /.well-known/manav-keys.json and verify receipts entirely offline using RFC 8785 JSON Canonicalization Scheme (JCS). Even if our origin servers were completely unreachable, your verifier continues to validate authentic receipts without disruption.
Operational history.
Subscribe to notices.
We publish cryptographic key lifecycle notices, algorithm transitions (such as FIPS 204 PQC adoption), and operational advisories. Security vulnerabilities should be reported directly via our disclosure program.