Skip to content

Open source · Open Badges 3.0

Issue certificates from your own domain.

Built on open standards, they still verify years from now, with or without us. Self-host the core for free, or use our cloud. No per-recipient fees.

Start free Self-host on GitHub ↗

Free to self-host. No credit card for cloud.

  • Open Badges 3.0
  • W3C VC 2.0
  • did:web
  • no blockchain
  • Apache-2.0

Hikbit already issues with dijaza, alongside universities and academies.

Riverside University

Verified
did:web:credentials.riverside.edu

via did:web

Advanced Data Analysis

Awarded to Jane Doe · May 2026

dijaza.com/c/8f2a1c47-9b3e-4d22-a6f0-2e7c9a4f1b88

Ed25519 proof · signed 2026-05-12

A certificate is only as durable as the company holding it.

Run a university, bootcamp, association, or training team?
Put the old model through the checks a certificate must pass:

  • Fails: Yours to export

    The free Canvas Badges tier closed on December 31, 2025. You can no longer issue from it, and export is disabled, so your records are locked in a read-only archive.

  • Fails: Flat pricing

    Credly charges per badge and Accredible per recipient, so the more you issue, the more you pay. Setup runs into the thousands, and real pricing only comes through a sales call.

  • Fails: Verifies without the vendor

    Most older vendors still issue Open Badges 2.0, verifiable only while their platform is online. A badge that breaks once you leave the vendor was never really the earner's.

Each one has the same root cause: a vendor, not you, holds your certificates.

How a certificate earns trust.

Three parties, one open standard. You only handle the first two steps; the rest runs on the standard, with no dijaza in the loop.

  1. Define · You

    Describe the achievement once in the Open Badges 3.0 format, then reuse it.

  2. Issue · You

    Sign it into a tamper-proof W3C Verifiable Credential. One API call or a bulk CSV.

  3. Hold · Earner

    Keep the certificate and share one link: readable for people, JSON-LD for machines.

  4. Verify · Anyone

    Resolve your did:web (your domain), then check the signature. No dijaza needed.

theirs: every check passes through the vendor

yours: the check goes to your domain

Ten years on

A college issues 5,000 diplomas this spring. In 2035, after two system changes, an employer verifies one in seconds. Each diploma is a self-contained signed record that checks against the college's own domain, so it holds up on open standards alone.

Built on the standards, not on us.

  • Open and self-hostable.

    The whole engine is Apache-2.0. Run the same core we do, on your own domain, forever.

    Apache-2.0 · docker compose up

  • Standards-native.

    Built on Open Badges 3.0 and W3C VC 2.0. Any compliant verifier or wallet works.

    OB 3.0 · W3C VC 2.0

  • No blockchain.

    Trust comes from controlling your domain and signing the certificate, not from a token.

    did:web + Ed25519

  • Native revocation.

    Revoke or suspend any certificate with the Bitstring Status List.

    Bitstring Status List

  • Flat pricing.

    One price per workspace, unlimited issuance. Never per recipient.

    per workspace · unlimited

  • Yours to export.

    Export every certificate and recipient record whenever you want, in open formats.

    JSON-LD · open formats

Self-host in one command

# the full engine, on your own domain
docker compose up

Or issue with one API call

curl https://api.dijaza.com/v1/credentials \
  -H "Authorization: Bearer $KEY" \
  -d '{ "achievement": "ach_123", "recipient": "jane@example.edu" }'

Leave your vendor. Keep your history.

Everything here is part of the free core, not a paid add-on.

  • Canvas Badges importer.

    Bring your badge designs and earner records from a Badgr or Canvas Badges export.

  • Moodle plugin.

    Issue Open Badges 3.0 from Moodle, which is stuck on 2.0. Open edX is next.

  • Verifier widget.

    Embed an iframe or script so partners verify certificates inline, no redirect.

See the migration guide

Self-host for free. Cloud at a flat price.

We charge for hosting and enterprise features, never per recipient. The core stays open.

  • Self-host

    $0 forever

    The open core.

    • Unlimited issuance
    • Apache-2.0 on your own did:web
    • Community support
    Self-host on GitHub ↗

  • Cloud

    Recommended

    Flat rate per workspace · price TBD

    Everything in Self-host, plus:

    • Hosted did:web and updates
    • Email support
    • No per-recipient fees
    Start free

Need SSO, multi-tenancy, white-labeling, or an SLA? Talk to us

No credit card. Cancel anytime. Self-hosting is free, forever.

Common questions.

Cost

Trust

Your certificates keep verifying. They check against your domain, not us, and you can self-host the same core or export everything. See a sample certificate verify against its own domain.

Switching

Support

Issue certificates that outlast your vendor.

Self-hosting is free, and the cloud is free to start. No per-recipient fees.

Start free Self-host on GitHub ↗

No credit card required.