Roadmap
CapchaCloud is a portfolio of evidence products — identity, consent, signatures, screening, KYC/AML, and institutional payment evidence — sharing one account and one evidence chain. This page states plainly what's live, what's in development, and what's planned. Detailed engineering planning stays internal; this is the customer view. Status words mean exactly what they say: live (shipped, in production), in development (being built now), planned (on the list, not started).
Live today
- CapchaID — live. Owned sign-in (email + Google), sessions, bot defense, and a consent certificate minted on every signup.
- Lead & Consent Evidence — live. TCPA-grade consent certificates with 5-year retention, one-line install.
- CapchaSign — live. E-signature with publicly verifiable seals; video-of-signing is a live add-on.
- CapchaVerify — live. Per-transaction screening evidence — real OFAC sanctions checks, video presence, face match, device intel. This is screening evidence, not certified KYC.
- CapchaShield — live; native sanctions screening ships today. The certified tier requires your own vendor account (Sumsub, Jumio, Veriff, or similar) — CapchaShield orchestrates and seals the result, it does not replace the vendor relationship.
- CapchaBanking + ISO 20022 — live; institutional preview. Reads and seals payment evidence only — CapchaCloud never custodies, settles, or moves funds.
- MCP gateway — live. An AI agent can provision tenants, verify records, and call the product APIs directly.
- Public evidence chain & transparency API — live. Tamper-evident, independently verifiable — anyone can check a record without your dashboard.
- ConsentWallet — live. End users can look up, verify, and manage their own consent records.
- API, webhooks, and offline verifier — live. Full reference on the API reference.
- Self-serve billing (Free → Business) and Enterprise plans, one credit system across every product — see Pricing.
In development
- Public chain explorer UI — a browsable, human-readable view of the evidence chain (the transparency API is live; the explorer UI is not built yet).
- npm SDK for the API
- Full OpenAPI coverage across every product, not just the core trust API
- SSO/SAML completion for CapchaID enterprise sign-in
- CapchaVerify launch hardening — rate limits, edge-case handling, and documentation depth beyond the initial release
- Team / multi-user workspaces
Planned
- SOC 2 Type I engagement — not started; no compliance certification exists today, on any product
- More sign-in providers for CapchaID (Microsoft, GitHub, and others on request)
- Additional compliance attestations as customer demand confirms them
- Deeper reporting for agencies managing multiple clients
Questions about timing for your use case? Ask the assistant · ← Home