Skip to content

For universities, institutes, companies and certifiers

Digital certificates anyone can verify

Issue cryptographically signed diplomas, certificates and badges — with a verifiable issuer identity and validity you can check in seconds, without calling the institution.

Did someone share a chapita with you? Check it here:

OpenChapitas — verifiable credentials, in motionLive
eddsa-jcs-2022mldsa65-jcs-2025

Trusted by

Organizations already crediting their people here

Every logo links to its public showcase: real, verifiable credentials — not decorative seals.

See all organizations

What is a chapita

A diploma that proves itself on its own

It's a diploma, certificate or badge in digital form, signed with the cryptographic identity of its issuer. The recipient shares it with a link or a QR code, and anyone can instantly check who issued it, to whom, and whether it's still valid.

A regular PDF

  • Edited in two minutes with any editor.
  • Confirming it means calling the institution.
  • If it expires or is revoked, nobody finds out.

A chapita

  • Signed: altering a single field invalidates it.
  • Verifies itself, without calling anyone.
  • Shows live whether it's valid or revoked.

A closer look

Anatomy of a chapita

This is what the person receives and what anyone can check. Every part is backed by a cryptographic guarantee, not by our word.

  1. 01

    Verified issuer

    Resolved through the institution's own did:web, not through us.

  2. 02

    Dual cryptographic signature

    Ed25519 and ML-DSA-65: one resistant to quantum computers.

  3. 03

    Live status

    Valid, expired or revoked — checked instantly.

  4. 04

    Its own link and QR

    The person shares it anywhere; they keep their page, link and QR.

The process, in three steps

How it works

01

Your institution issues it

From the console, you sign the certificate with your organization's digital identity. It's sealed: no one can alter it.

02

The person receives it

They get their chapita with its own page, a QR and a badge for their CV or LinkedIn. They can keep and export it, no account required.

03

Anyone verifies it

An employer, another institution or anyone else confirms in seconds that it's real, who issued it and whether it's still valid. No sign-up.

Who it's for

Use cases

Any organization that hands out PDF certificates today can issue verifiable chapitas.

Universities and institutes

Degrees and diplomas graduates share and any employer verifies without calling the registrar.

Bootcamps and training centers

Course and program certificates, with the skills acquired and their framework of reference.

Boards and certifiers

Professional accreditations and recertifications with live validity and revocation.

Companies

Internal training and compliance: who completed what, when, and auditable.

Workforce and public bodies

Certification of job skills the person carries with them, verifiable by anyone.

Events and communities

Participation badges, talks and achievements shared with pride — and impossible to fake.

Why it's trustworthy

Mathematical proof, not promises

Every chapita carries a dual cryptographic signature —Ed25519 and ML-DSA-65, the latter standardized by NIST (FIPS 204)—. Altering a single field invalidates both. And you don't depend only on us: verification resolves your own institution's identity, so it can be checked independently of this platform.

Verification chainquantum_safe: true
  1. eddsa-jcs-2022

    Ed25519

  2. mldsa65-jcs-2025

    ML-DSA-65 · FIPS 204

  3. did:web

    sovereign trust root

  4. BitstringStatusList

    not revoked · valid

verifiable offline via did:web · no account

Digital mint

Minted, signed and verifiable

Every chapita is issued as a unique piece: sealed with your institution's identity and a quantum-resistant dual signature. Collect them — each one counts, until you become a legend.

The OpenChapitas king, covered in badges — expert level

Every chapita counts — until you become a legend

The OpenChapitas seal, in 3D

Does your institution want to issue?

Open standard Open Badges 3.0 on W3C VC 2.0, with your own trust root did:web. No platform lock-in.

Enter the console →