Four things VLI does. Use any one — or all of them together.
Seal locks an event. Register makes it publicly provable. Verify lets anyone check it. Vault stores the evidence long-term. They work standalone or as a continuous loop.
The four primitives
Pick one. Or compose all four.
Open source, Apache 2.0. Each one stands alone. Together they're the trust loop.
Ed25519 + JCS + SHA-256 Learn more → Register Register Anchor your seal in a public, append-only Merkle log. Merkle log + inclusion proof Learn more → Verify Verify Confirm any seal — anyone, anywhere, no account. ClearKey CLI · open source Learn more → Vault Vault Preserve sealed bundles long-term and produce audit-ready exports. VAV · or self-hosted Learn more → Browser extensions
Seal what you see, where you see it.
Drop a primitive into your browser. Capture a screenshot, lock a file, browse the marketplace — every action seals locally first.
Chrome MV3 · open source Source on GitHub → Extension VLI File Seal Seal any file with Ed25519 — offline-first, verifiable evidence. No upload, no server, no account. Chrome MV3 · offline Source on GitHub → Load unpacked from the source folder while we finalise Chrome Web Store listings. The math is the same either way.
Composition
How they fit together.
Seal → Register → Verify is the trust loop. You seal an event, register it for inclusion proof, and anyone can verify both later.
Vault sits alongside the loop, preserving every sealed bundle so the loop is repeatable years later — auditors, regulators, downstream consumers can all replay it.
Use one capability or all four. The math composes.