CapchaID
Sign-in, sessions, and identity events, each one recorded as evidence rather than only a log line. Answers who acted, on what authority, and when.
1 credit per authenticated session
Compare: CapchaID vs Clerk
Every product
One record format. Every workflow.
CapchaCloud is not a suite of separate tools that happen to share a login. Every product below writes the same object — an Evidence Record, sealed, hash-chained, independently time-anchored, and verifiable by someone who does not trust us. They also share one balance: credits are drawn from the same pool whichever product spends them, so nothing here carries a separate seat fee, platform fee, or minimum.
Capture what happened
Products that turn a real-world action into a sealed record at the moment it occurs.
CapchaConsent
Consent captured at the point of collection and sealed into a certificate — what was shown, what was agreed to, and the exact wording in front of the person at the time.
6 credits per consent certificate
Compare: CapchaConsent vs TrustedForm · Consent Wallet
CapchaSign
E-signature that produces a checkable artifact: a signature embedded in the PDF itself that Adobe Reader validates offline, plus a sealed certificate of the whole ceremony.
100 credits per completed envelope · +40 for the video add-on
Compare: CapchaSign vs DocuSign · Open Sign Studio
CapchaCloud MCP
Evidence tools for AI agents and software. When an agent takes a consequential action, the same Evidence Record is written — so an autonomous step is as reviewable as a human one.
Draws the credits of whichever action the agent performs
Check who you are dealing with
Screening and document verification, sealed so the result is reviewable later — including by someone who wants to second-guess it.
CapchaVerify
Screening and identity-document checks, including a deep visual forensics scan of a submitted ID. Screening evidence — not a certified KYC determination.
10 per native screen · 30 per media check · 100 per ID deep-scan
CapchaShield
KYC/AML case management and certified-vendor routing. Bring your own vendor — they bill you directly, and CapchaCloud never marks up or passes through their fees.
70 credits per certified check (case management and sealing only)
Prove a transaction
For institutions. CapchaCloud never moves, holds, or releases funds and never approves or blocks a payment — it produces evidence, and your people decide.
CapchaBanking
Seals the exact bytes of an ISO 20022 message, a settlement leg, or a reconciliation finding into a record your counterparty, auditor, or examiner can verify without trusting us.
10 credits per sealed message
Wire fraud & payment-detail drift
The question the rest of the stack does not ask: do the final payment details still match what was actually authorized? A confirmer re-states the recipient independently; a mismatch fails closed.
Built on CapchaBanking · start with a retrospective audit on your own historical data
Compliance Envelope
Runs a policy against a case and seals the verdict together with the reasoning, the ruleset version, and the inputs — so a decision can be re-examined years later on its own terms.
12 credits per evaluate and seal
Open Evidence Rail
Format-agnostic sealing for anything the named products do not cover. Canonicalize, validate against your schema, seal, and receipt — whatever the payload is.
10 credits per rail seal
Verify it without us
The part that makes the rest meaningful. If verification depended on CapchaCloud staying online, honest, and in business, it would not be evidence.
Public chain explorer
Every sealed record lands in an append-only, hash-linked, Merkle-batched chain with published signing keys. Walk it from genesis, recompute every block, check the signatures.
Free · public · no account
Evidence methodology
Exactly what a record proves, how the seal is computed, which timestamp authorities are used, and — just as importantly — what a record does not prove.
Read before you rely on any of it
What every product shares
| One record format | Consent, identity, signature, transaction, and agent actions all produce the same Evidence Record object, so one verification method covers everything. |
|---|---|
| One balance | Credits are drawn from a single pool regardless of which product spends them. Prices are looked up server-side at the moment an action completes, so a caller cannot assert its own price. |
| Independent verification | Published keys and a published method. A record can be checked by someone who does not trust CapchaCloud and does not have an account. |
| Retention you can audit | Consent, screening, and signed-document stores each carry an object-storage retention lock of 1,826 days across all prefixes. An auditor can request the live configuration rather than taking our word for it. |
| Stated limits | Every product page carries a “what this does not prove” section. We would rather lose a deal than win one on a claim that does not survive review. |
Where we honestly are
CapchaCloud is pre-certification: there is no SOC 2, ISO 27001, PCI DSS, or FedRAMP report today, and no third-party penetration test has been performed. There are no financial-institution customers in production and no case studies. Institutional security review, vendor onboarding, and legal approvals remain ahead of any bank deployment. We publish this on the product pages rather than in a footnote, because a company selling evidence should not need to be asked.