Open source · Open Badges 3.0

Issue verifiable credentials your people truly own.

Built on open standards and anchored to your own domain, so 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

Already issuing with Hikbit, plus 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 credential is only as durable as the company holding it.

Run a university, bootcamp, association, or training team?
You've hit at least one of these issues:

  • 01

    The Canvas Badges sunset.

    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.

  • 02

    Volume-based 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.

  • 03

    Proprietary formats.

    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 holds your credentials, not you.

How a credential earns trust.

Three parties, one open standard. You only handle the first two steps; the rest runs on the standards, 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 credential 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.

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.

  • Standards-native.

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

  • No blockchain.

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

  • Native revocation.

    Revoke or suspend any credential with the Bitstring Status List.

  • Flat pricing.

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

  • Yours to export.

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

Self-host in one command

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

Or issue with one API call

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

Leave your vendor. Keep your history.

All 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 coming.

  • Verifier widget.

    Embed an iframe or script so partners verify in their own interface, with no redirect.

See the migration guide ↗

Self-host 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-tenant, white-label, or an SLA? Talk to us →

No credit card. Cancel anytime. Self-host free, forever.

Common questions.

Cost

Trust

Switching

Support

Issue credentials 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 to start.