Talk to an engineer, not a sales rep.
Bring the system you want to gate and the decision you need to prove. We will tell you whether this fits (including when it does not) and what it would take to ship.
What happens next
- Within one business day: an engineer replies with a fit assessment: the statement schema for your action, the assurance level it needs, where the verifier sits, and an honest note if Manav is the wrong tool.
- 20-minute deployment review: we walk the flow on your architecture: who signs, on what device, where verification happens, whether it must work offline.
- Evaluation key the same day: test keys that return valid, tampered, replayed and expired receipts, working from localhost, so your team can integrate before any contract.
- Security review, on request: 45 minutes for your CISO’s team: threat model, key handling, failure modes, and what happens to you if we disappear. You get the conformance suite and the questionnaire.
For your security reviewer
Ask for the evidence pack on the call, or say so in the form. It contains:
Conformance suite
Adversarial receipt vectors and cross-language canonicalisation vectors for Ed25519 (RFC 8032) receipts, verifiable with standard libraries. Every command comes with its expected output, so the reviewer runs it rather than reads about it.
Questionnaire + policies
Completed CAIQ Lite, the DPA, the subprocessor list, the vulnerability-disclosure policy and the current, plainly stated compliance status.
Architecture walkthrough
Key custody, rotation and revocation; the offline verifier; the limits: what the system does not prove (a deceived approver, a compromised phone OS, re-enrollment, the callback fallback, and Manav's signing key), as listed in the bank architecture limits.
Prefer email?
[email protected] for deployments and pricing · [email protected] for security · everything else on the contact page.