ternent.dev
Seal anything. Verify anywhere.
Seal turns text and files into verifiable proof artifacts directly in your browser. No accounts. No backend. Just math, keys, and integrity.
Verification passed
- Signed by
- 9f3c4a1b…d07e12af
- Algorithm
- ECDSA-P256-SHA256
- Hash
- sha256:a3f8…c9d2
- Status
- Verified
Features
Built for trust, not platforms
Seal handles the cryptography so you can focus on proving what matters.
Browser-native
Sign and verify without leaving your workspace.
Deterministic identity
Keys derived locally and never stored.
Travel-ready proofs
Self-contained artifacts you can carry anywhere.
No backend required
Everything runs client-side, from signing to verification.
Verification record
{
"version": "1",
"type": "seal-proof",
"algorithm": "ECDSA-P256-SHA256",
"createdAt": "2026-03-13T12:04:21.000Z",
"subject": {
"kind": "file",
"path": "sample.txt",
"hash": "sha256:a3f8...c9d2"
},
"signer": {
"publicKey": "BASE64-SPKI",
"keyId": "9f3c4a1b...d07e12af"
},
"signature": "BASE64-SIGNATURE"
}How it works
Three steps to seal any record
Generate your identity, sign your content, and share a signed artifact that anyone can verify.
Generate your identity
Create a deterministic keypair in one click or import one you already trust.
Sign your content
Hash any text or file in seconds and produce a signed proof artifact.
Verify anywhere
Anyone can independently verify the proof without your private key or your app.
Use cases
Trust that travels with your work
Sign once. Verify anywhere.
Blog posts
Publish authorship and integrity together.
Release artifacts
Attach proofs to builds and downloadable assets.
Legal documents
Capture exactly what was signed and when.
Research papers
Assert provenance for revisions and datasets.
Static websites
Ship verifiable proofs alongside published content.
Open data
Distribute trusted records without central gatekeepers.
Built on Concord
Identity and verification, separated from infrastructure
Seal is built on Concord identity primitives with deterministic signing and trust-minimal verification. No servers. No lock-in. Pure cryptography you control.
Prove integrity
Cryptographically assert that content is exactly as you created it.
Control identity
Your keys remain yours, with no third party holding your identity.
Audit everything
Create a verifiable record of who signed what and when.
Developer example
import { createSealProof, verifySealProofAgainstBytes } from "@ternent/seal-cli/proof"
const proof = await createSealProof({
signer: { privateKeyPem, publicKeyPem, keyId },
subject: { kind: "file", path: "sample.txt", hash: "sha256:..." }
})
const verified = await verifySealProofAgainstBytes(proof, fileBuffer)Ready to start?
Ship verifiable integrity into your workflow
Sign your first artifact in seconds and bring verifiable trust to text, files, and release pipelines.