The Verita family is five products that share a single cryptographic foundation: Ed25519 identity keys, hash-chained transparency logs, and exportable receipt bundles that anyone can verify offline from public keys alone. Each product owns one verb and one object; each hands off cleanly to the next. VeritaBase is the front door and the substrate.
Each product owns a distinct verb and object. The shapes compose: a VeritaPad conversation is a VeritaPath trail; its receipts can be notarized by VeritaCrypt and preserved by VeritaLink; its session keys can be stored under VeritaVault.
Point-in-time integrity for any file or event. Emit a signed proof; verify offline forever.
How did we get here? An append-only trail of decisions and state transitions, checkpointed and auditable.
This URL still means what it meant. Preserved destinations with a cryptographic record of what was there.
Client-side-encrypted secrets storage with a transparency-log-grade audit trail. Prove every access.
End-to-end encrypted P2P messenger with an exportable, offline-verifiable transcript. Signal-class confidentiality plus a provable chain.
The shared foundation. This page and — in time — the developer reference, shared SDKs, and spec docs that tie the five together.
Each product is its own app, but they all stand on the same crypto-discipline substrate. The shapes rhyme because the primitives are the same.
Every actor — user, device, or service — holds an Ed25519 signing keypair. Fingerprints are short, human-verifiable, and the same everywhere in the family.
Every signed event links to the hash of the one before it. Insertion, deletion, or silent edit breaks the chain visibly. Checkpoints published at cadence.
Any slice of any log exports to a self-contained JSON bundle — signatures, chain, checkpoints — verifiable from public keys alone, no server, no trust.
The command names differ, but the verbs, exit codes, and receipt format are consistent — so if you learn one product, you're halfway through the next.
$ veritacrypt sign contract.pdf signed ed25519:4a9c54…be12 notarized crypt-chain leaf #00094 OK receipt: contract-0094.vc-receipt.json $ veritapath record deploy.v2.1 --parent deploy.v2.0 appended trail leaf #00312 parent deploy.v2.0 (verified) OK lineage extended $ veritapad send alice "contract terms look good" encrypted to alice signed ed25519:4a9c54…be12 chained conv leaf #00184 OK delivered and countersigned $ veritavault get stripe.api_key --reason deploy unsealed locally (client-side) audit vault-chain leaf #00041 OK access logged, provable on request $ verita verify ./any-bundle.json product veritapad signatures all valid (2 peers) chain intact RESULT: verifiable offline
The near-term work on this site is a developer reference: the shared signature + chain + receipt spec, a verification library that works against any product's receipt bundle, and a CLI that wraps the common operations. If you want to build on top of the Verita family — or verify its receipts without touching the client apps — this is the page you'll come back to.
verita-verify CLI — verify any product's receipt bundle offline, no network.Occasional, technical. Release notes, spec updates, interop tests.