Verifiable credentials, anchored to a public blockchain

Certificates people can actually trust.

Issue tamper-evident credentials anchored to a public blockchain — verifiable by anyone in seconds, and still verifiable even if ChainAnchor disappears.

Verify a credential → · Already have an account? Log in

Using it solo or for a small team? →

⛓ Anchored on Base 🔓 Open-source verifier 🔁 No vendor lock-in 🇬🇧 UK-based

Why a certificate needs more than a PDF

📄

Trivially forgeable

A PDF takes minutes to fake and a logo seconds to copy. Employers can't tell a real certificate from a counterfeit.

🐌

Slow to verify

“Did this person really graduate?” turns into emails to a registrar and days of staff time — multiplied across every request.

🔒

Locked to a vendor

Badge platforms verify by phoning home to their own servers. If they change terms or shut down, your “verifiable” credentials quietly stop working.

How it works

1

Verify your domain

Prove you control your institution's domain once. Your credentials then carry a verified-issuer badge.

2

Issue

One credential, or a whole cohort from a CSV — anchored to the blockchain in a single transaction. Files are hashed in your browser, never uploaded.

3

Share & verify

Recipients share a link, QR, or add it to LinkedIn. Anyone can verify it in seconds — no account needed.

Tamper-evident

Every credential is fingerprinted with SHA-256 and anchored on Base. Any change to the file is detectable — recompute the hash and compare.

Independently verifiable — no lock-in

Verification resolves against a public blockchain and an open-source verifier we don't control. If ChainAnchor vanished tomorrow, every credential we ever issued still verifies.

Trusted issuer & lifecycle

Credentials are tied to a domain-verified issuer, so a copied badge fails verification. Set expiry dates, and revoke single or in bulk when a qualification lapses.

Don't take our word for it

The whole point is that you don't have to trust us. Check any credential yourself, read the contract on-chain, or run the verifier offline.

Transparency & anchoring stats · Verified issuer directory

For institutions

Built for the way universities and certification bodies actually work

Single sign-on, automated joiner/leaver provisioning, your branding on every credential, and bulk issuance for whole cohorts — with the controls procurement asks about.

Book a demo
  • Single sign-on (OpenID Connect) — Google Workspace, Microsoft Entra, Okta
  • SCIM provisioning with automatic deprovisioning
  • Your logo & colours on every credential and proof page
  • Bulk issuance, revocation & expiry from a CSV
  • Org roles, pooled storage & an audit log
  • REST API & webhooks for your systems

For individuals & teams

Not just for institutions — prove anything is yours

You don't need to be a university to use ChainAnchor. Anchor any file or capture a web page to prove it existed, unaltered, at a point in time — and start free.

🎨

Protect your work

Timestamp designs, manuscripts, code, or research so you can prove you had it first — tamper-evident, on a public chain.

📄

Timestamp documents

Contracts, agreements, and records — anchor the file (it's hashed in your browser, never uploaded) and share a verifiable proof.

🌐

Capture a web page

Freeze what a page said at a moment in time as tamper-evident evidence — for disputes, compliance, or your own records.

Simple, tiered pricing

Compare all plans →

Free · £0

Get started anchoring files and credentials. Anchored in regular Merkle batches.

Pro · £12/mo

Instant anchoring, unlimited archive storage, page monitoring, API & webhooks.

See Pro →

Institutional · from £1,200/yr

SSO & SCIM, branding, bulk issuance, org management and support.

Talk to us →

Issue once. Verifiable forever.

Tamper-evident credentials your recipients can prove, and anyone can check.

ChainAnchor

Immutable Proof of File Authenticity

Anchor or Verify a Local File

Select a file. If it's new, it will be anchored. If it exists, its proof will be displayed.