Issued on a public blockchain. Stored permanently. Verifiable on any open tool — even without us.
Verified credential
Built on the open standards that make credentials portable
W3C VC 2.0
The global specification
BlockCerts v3
MIT-originated standard
MerkleProof2019
The proof every credential carries
DID:web
Issuer identity, controlled by the issuer
CredentialStatusList2017
Open revocation
We don't claim affiliation with these bodies. We claim implementation. Verify it yourself on any third-party tool.
The architecture
Both the signed credential and the rendered PDF are stored on a decentralised network designed for permanent archival — paid for once at issuance, kept accessible for 200+ years. No subscriptions. No off-switch. No datacentre to lose.
How storage worksBuilt on open standards — W3C Verifiable Credentials 2.0 and BlockCerts v3. Recipients receive a signed credential file they actually own, verifiable on any compatible tool, anywhere in the world.
Open standards we useAnchored on a public proof-of-stake blockchain. Every credential carries a cryptographic proof anyone can verify against the public ledger — forever. We don't run the chain. We're not in the trust path.
How verification worksHow verification works
When someone needs to verify a Perpetual credential, the math doesn't go through our servers. It goes to the public blockchain and the permanent storage network directly. We're not in the trust chain — by design.
Five steps. No Perpetual involvement required.
Resolved from the issuer's own domain.
The verifier looks up the issuing organisation's published identity at their own domain — not ours. The issuer controls their own identity record.
Checked against the public blockchain.
Every credential carries a mathematical proof linking it to a transaction anchored on a public proof-of-stake blockchain. The verifier reads that transaction directly from the chain.
Retrieved from permanent storage.
The signed credential file and the rendered PDF live on a permanent decentralised storage network. The verifier fetches them straight from there.
Checked against the issuer's published list.
A separate signal, also on the issuer's own domain, indicates whether the credential has been revoked.
If all four match, the credential is proven valid.
Same flow on the public BlockCerts verifier, on any compatible mobile wallet, on any tool built against the open standard, and inside the Perpetual portal.
This same verification flow runs on the public BlockCerts universal verifier, on any compatible mobile wallet, on any tool built against the open standard, and inside the Perpetual portal. They all return the same answer because they're all reading from the same public infrastructure. If we shut down tomorrow, every one of these still works.
The wedge
Plenty of platforms claim to be blockchain-backed. What they usually mean is: when they issue your certificate, they record a hash of it on a public chain.
A hash is just a number. On its own, it proves nothing. To verify a credential against an on-chain hash, you need the original certificate to compare against — and on most platforms, that original lives in their database.
The same database that disappears when the company shuts down, gets acquired, or migrates platforms.
Both halves of the proof live on infrastructure no one can take down. Including us.
That's the difference between anchored on a blockchain and built on one.
See the architectureMost platforms
How we built it
The promise
Most digital credentials disappear when the platform shuts down. The verification URL breaks. The database migrates. The storage bill goes unpaid. The credential the recipient earned was never really theirs — it belonged to whichever vendor was keeping the lights on.
Perpetual was built to solve that. Every credential we issue is signed, anchored to a public blockchain, and stored permanently on a decentralised network we don't control. If Perpetual shut down tomorrow, every credential we ever issued would still verify.
That's the promise the name carries.
Read the full storyHow we compare
| Perpetual | Most platforms | |
|---|---|---|
| Hash anchored on a public blockchain | ● Yes | Sometimes |
| Public chain, not private/permissioned | ● Yes | Often private |
| Full signed credential on decentralised storage | ● Yes | — Vendor database |
| Rendered PDF stored permanently | ● Yes | — Vendor database |
| Verifiable on third-party tools | ● Yes | — No |
| BlockCerts v3 native | ● Yes | Partial |
| Survives vendor shutdown | ● Yes | — No |
| One-shot storage cost (no recurring fees) | ● Yes | — Recurring |
Who it's for
Degrees, transcripts, micro-credentials — verifiable globally, valid for a graduate's lifetime.
For higher educationInternal certifications, compliance training, vendor accreditation — auditable, integration-ready.
For corporate L&DNational qualifications, professional licences — sovereign-grade trust, full audit trail, English and Arabic with full RTL.
For governmentThree-second verification of any candidate credential. No phone calls to registrars. No fake-degree risk.
For employersWhere we are
We're a small team that built the credentialing platform we wished existed — one where the recipient owns their credential, the verifier doesn't depend on us, and the architecture means your credentials outlive whatever happens to our company.
We're not going to put a logo wall up before the customers are real. What we can do is show you the architecture in a real conversation, walk through real credential data, and let you verify what we built on tools we don't run.
That's the conversation worth having.
Every Perpetual deployment starts with a conversation. We'll walk through your issuance volume, your standards posture, your integration needs, and what success looks like for your team. Then we'll quote you, accurately, in writing.
