Drag-and-drop template designer.
Full bilingual support — English and Arabic, with proper RTL layout. Pre-built templates to start from, custom fields for everything specific to your organisation.
For Issuers
Issue credentials your recipients can actually use.
From a single certificate to a batch of 100,000. Designed in your browser, anchored on a public blockchain, stored permanently — without ever touching a wallet.
Issuance batch
Ready to issuerecipients.csv2,481 rows
- Sample RecipientSample Professional Cert.
- Sample RecipientSample Professional Cert.
- Sample RecipientSample Professional Cert.
- … 2,478 more
Anchor
Mainnet
Storage
Permanent
Standard
BlockCerts v3
Who this is for
Anyone whose recipients carry a credential that needs to mean something five, ten, twenty, fifty years from now.
Universities, training providers, certification bodies, professional associations, and government accreditation agencies.
If the credentials you issue are supposed to last a lifetime, they should be built on infrastructure that lasts a lifetime.
What you get
Everything you need to issue. Nothing in the way.
Bulk issuance from a CSV.
Upload a spreadsheet, hit issue, and the platform handles the cryptographic batching, the on-chain anchoring, the permanent storage uploads, and the recipient emails.
Recipient management.
Track who's been issued what, who's opened their credential, who's shared it. Resend, revoke, or reissue when needed.
Team collaboration.
Granular roles — Owner, Admin, Manager, Issuer, Viewer, Auditor. Two-factor authentication on every account.
Brand-controlled issuer identity.
Your DID is published on your own domain, not ours. Verifiers see your credentials as coming from you, not from a vendor.
Audit trail.
Every sensitive action logged, exportable, ready for compliance review.
A definition
What "blockchain-anchored" actually means here.
When we say "blockchain-anchored," we mean something specific. We don't run a private chain. We don't write to a database we own and call it a blockchain. We anchor every batch of credentials on a public proof-of-stake blockchain — the same kind of infrastructure that secures hundreds of billions of dollars of public value.
This matters for two reasons.
Permanence
A public chain run by hundreds of thousands of independent validators cannot be turned off. The anchoring transaction we write today will still be readable, by anyone, in 20 years.
Independence
Anyone — your accreditation body, a foreign employer, a recipient, a researcher — can verify the anchor without going through us. That is the property that makes the credential portable and survivable.
If a platform tells you they "use blockchain" but won't say which one, or admits the chain is private, or stores the credential itself in their own database — that's not what we mean by blockchain-anchored.
Use cases
Five scenarios where the architecture earns its keep.
Higher education
Degrees, transcripts, diplomas, micro-credentials.
The credential remains verifiable for the graduate's lifetime, across employers, countries, and decades. Cross-border admissions teams can verify in seconds without contacting your registrar.
Corporate training and L&D
Compliance training, internal certifications, vendor accreditation.
Auditable for regulators, integrable with HR systems, immune to platform churn.
Professional certification bodies
Medical councils, legal bars, engineering institutes, finance certifications.
Recurring re-certification cycles fit batch issuance. Verification by third parties is the entire value proposition — and it's the architecture.
Government and accreditation
National qualifications frameworks, professional licences, accreditation marks.
Sovereign-grade trust, full audit trail, English and Arabic UI with RTL support.
Vocational and skills training
Skills certifications, trade qualifications, course completions.
Stackable credentials that combine into pathway records.
Integrations
Plugs into the systems you already run.
LMS
Moodle, Totara
On day one. Canvas, D2L, Cornerstone on the roadmap.
SSO
Microsoft, Google, Okta, SAML
Standard identity providers, day one.
Payment
Stripe
For programmes that charge for issuance.
A note on RTL
Arabic and English. Both first-class.
We started with RTL as a first-class requirement, not an afterthought. The template designer canvas, the issuer portal, the recipient view, the public verification page — all of them work the same in Arabic and English.
This was a deliberate architectural choice driven by who we expect our customers to be.