AeonProof Code registers a signed, timestamped proof of anteriority for any codebase — without your code ever leaving your machine. Only a cryptographic fingerprint is recorded. Verifiable by anyone, forever.
$ npx aeonproof-cli prove ./my-project Hashing 142 files locally… (your code never leaves this machine) Merkle root : 3fcc7a6df54b9823…a8e57b69 ✔ Proof registered : apc_9f2e… ✔ Signed by 6fad:44f0:9950:b95b — 2026-08-20T10:02:49Z Public verification : aeonproof.vercel.app/verify.html?id=…
A client disputes your delivery. An ex-partner walks away with the repo. An AI regurgitates your work. A due-diligence audit asks who wrote what, when. Copyright protects you automatically — but only if you can prove anteriority.
Attach a proof certificate to every client delivery. If a dispute ever comes, you hold a signed, dated, third-party-verifiable record.
Investors and acquirers ask who owns the code. Systematic proofs on every release turn a week of IP audit into a five-minute check.
Models scrape and regurgitate. A registered proof establishes that your code existed, signed by you, before any lookalike appeared.
One command. Local hashing. Public verifiability.
The CLI builds a Merkle tree of your files (SHA-256). Only paths and hashes are used — file contents never leave your machine.
The root is signed with your Ed25519 key and registered with a server timestamp. Daily batches are anchored via OpenTimestamps (Bitcoin) — verifiable without trusting us.
Yearly Merkle roots are written into a synthetic DNA capsule via AeonScript — the offline, century-scale backstop that survives any digital collapse.
Anyone can compare any directory against a registered proof — in the browser or with the CLI.
AeonProof Code is not a patent (source code is generally not patentable) and does not replace legal counsel. It produces technical evidence of anteriority and integrity: "this exact code tree was registered, signed by this key, at this time." Courts in most jurisdictions accept such records as supporting evidence; probative weight varies. We say this upfront because a proof service you can't trust to be honest is worthless.
Start free. Pay when it becomes part of how you ship.
No subscription? Pay as you go: $2 per proof (packs of 10 — $20). DNA Capsule add-on: $49/yr — your yearly roots archived in a physical DNA capsule.
$ npx aeonproof-cli keygen --name "Your Name" $ npx aeonproof-cli prove ./your-project # That's it. Keep the generated proof-*.json — it's your evidence.
Or add the GitHub Action to certify every release automatically.
No. Hashing happens on your machine. The record contains file paths and SHA-256 hashes only. Even we cannot reconstruct your code from a proof.
Neither. It's independent technical evidence of anteriority — comparable to a notarized deposit (e-Soleau style), strengthened by public Bitcoin anchoring and DNA archival. For litigation, bring it to your lawyer as part of your evidence bundle.
Your proof records are self-contained JSON files, verifiable offline with open-source code. Daily roots are anchored in Bitcoin via OpenTimestamps, and yearly roots in DNA capsules. The proof outlives us — that's the whole design.
Git timestamps are trivially forgeable (GIT_COMMITTER_DATE). AeonProof binds your tree to an independent server timestamp, a public blockchain anchor, and an Ed25519 identity — three things you can't rewrite after the fact.
Yes. aeonproof verify proof.json ./dir --offline checks the Merkle tree and signature with zero network calls. The server adds the registered timestamp and anchoring status.
Every release you don't certify is a claim you can't defend later.
Register your first proof — free