Skip to content

For institutions

Issue credentials that anyone can verify

Universities, institutes, training bodies, companies and certifiers issue cryptographically signed diplomas, certificates and badges, with a verifiable issuer identity and validity checkable in seconds —on open standards (W3C VC 2.0 / Open Badges 3.0).

Request a demoRequest a quoteSee a real credential →

Already issuing here

7 organization(s)
Comunidad IA LATAM12 badge(s) · 2600 issued8.8 Academy5 badge(s) · 51 issuedCISObeat Academy1 badge(s) · 50 issuedCyberIAyuda Chile1 badge(s) · 16 issuedBugsCode2 badge(s) · 9 issuedOT Security LATAM2 badge(s) · 0 issuedPurpleTeam Academy0 badge(s) · 0 issued

Real public showcases — every profile links verifiable credentials, not decorative logos.

What's included

Signed issuance

Every credential carries a dual signature (Ed25519 + ML-DSA-65) over canonical data.

Live revocation

Signed Status List: marks valid, expired or revoked and checks instantly.

Sovereign identity

Your organization publishes as did:web; verification doesn't depend on this platform.

Page, QR and badge

Every holder gets their own page, a QR and a badge for their CV or LinkedIn.

API & webhooks

Integrate issuance and events into your systems; signed deliveries with anti-replay.

Public showcase

One profile per organization with your logo, domain and credential catalog.

Getting started

  1. 1

    Request a demo

    We show you a real credential, the console and the issuance flow.

  2. 2

    We set up your organization

    With your logo, domain and public profile. You get console access.

  3. 3

    Create your first achievement and issue

    Define criteria, import holders (CSV) and issue — with page, QR and badge.

  4. 4

    Integrate if you need to

    API and webhooks to connect your LMS or CRM.

Security and standards

Built on W3C Verifiable Credentials 2.0 and the Open Badges 3.0 model. Signing keys are held in Vault and access is isolated per organization. See Security.

CapabilityStatus
W3C VC Data Model 2.0Implemented
Open Badges 3.0Compatible · in validation
JSON-LD / contextosImplemented
Firma Ed25519 (eddsa-jcs-2022)Implemented
Firma ML-DSA-65 (FIPS 204)Implemented
did:webImplemented
Status List (revocación)Implemented
Export VC (JSON)Implemented
Badge PNG (VC horneada)Implemented
Certificación 1EdTechPending

“Compatible” / “in validation” reflect the real status: we use the Open Badges 3.0 model on W3C VC 2.0; formal 1EdTech certification is pending.

Frequently asked questions

What exactly does verification check?

It confirms the issuer's signature, data integrity and status (valid/revoked). The truthfulness of the achievement depends on your institution.

Do holders need an account?

Not to verify. The wallet is optional, for gathering and managing the credentials they receive.

What if I stop using the platform?

Already-issued credentials remain independently verifiable via did:web and their JSON export.

How are signing keys protected?

They're held in Vault (never in code or the environment). See the Security page.

Ready to issue?

Founding issuers program: we're onboarding the first institutions in Latin America. Write to us and we'll walk you through the rollout.

Request a demoRequest a quote

Or leave your details and we'll reach out

A product of TTPSEC SpA ·