DCC Issuer Coordinator
DCC Issuer Coordinator is an MIT-licensed, open-source service for issuing Verifiable Credentials within another system.
What DCC Issuer Coordinator is
DCC Issuer Coordinator is an MIT-licensed, open-source service for issuing Verifiable Credentials within another system. It signs credentials and can attach status information that later supports revocation or suspension. VC-API endpoints handle credential issuance and status updates, with another endpoint returning a status list. Signing supports did:key and did:web formats. Multiple signing authorities can be configured as tenants, each with its own key and optional bearer-token protection. Optional status management uses Bitstring Status List and stores lists through database or Git services. The coordinator calls separate signing and status services, described as Express applications run with Docker Compose. Docker Compose instructions and version-tagged Docker Hub images are provided; there is no latest tag. A four-step quick start is described as taking less than five minutes. The project shows use in school credential workflows and mentions importing credentials into the Learner Credential Wallet. The shared test key is unsafe for real credentials, so production deployments require a private key.
Good
- Implements VC-API issuance and status endpoints
- Supports did:key and did:web signing formats
- Allows multiple tenant signing authorities
- Optional revocation and suspension via Bitstring Status List
- Provides Docker Compose deployment instructions
Watch out
- Shared default signing key is unsafe for real credentials
- Git-backed status storage is recommended only for light testing
- Tenant endpoints can remain unprotected if configured so
- Requires integration into a larger issuing system
Who it suits
It suits organizations such as schools integrating credential issuance into their own portals or services. Developers needing VC-API access, tenant issuers, and optional status management can use its self-hosted API architecture.
Verdict
DCC Issuer Coordinator provides a focused, self-hosted foundation for credential issuance and status handling. It offers flexible tenants and key formats, but production use requires careful key protection and endpoint security.
The facts
Each one read from DCC Issuer Coordinator's own pages, with the date it was checked.
What it does
- API
- The service implements VC-API endpoints for issuing credentials and updating credential status, plus an endpoint for returning a status list.checked 4 Oct 2026
- Architecture
- It is an Express app that coordinates calls to separate signing and status services running together in Docker Compose.checked 11 Oct 2026
- Audience
- The README presents the issuer for organizations such as schools that integrate credential issuance into their own systems and student portals.checked 11 Oct 2026
- Credential signing
- The README says the issuer supports the did:key and did:web DID formats for signing keys.checked 4 Oct 2026
- Credential status
- Its optional revocation and suspension mechanism implements Bitstring Status List and stores status lists through database or Git services.checked 11 Oct 2026
- Deployment
- The quick start runs prebuilt Docker Hub images through Docker Compose and the README says setup takes less than five minutes.checked 11 Oct 2026
- Endpoint security
- Tenant endpoints can require a Bearer token, and the README suggests IP filtering; setting a tenant token to UNPROTECTED leaves its endpoint unprotected.checked 11 Oct 2026
- Integrations
- The README describes using the issuer from a larger system that prepares a credential and posts it to the issuer, and mentions importing credentials into the Learner Credential Wallet.checked 11 Oct 2026
- Intended users
- The README describes using the issuer within a larger system, such as a school's credential issuance flow, with an API client sending credential data to be signed.checked 4 Oct 2026
- Issuing API
- It implements the VC-API POST endpoints /credentials/issue and /credentials/status.checked 11 Oct 2026
- Key support
- The issuer supports did:key and did:web key formats, and the README recommends did:web for many production deployments because keys can be rotated without updating credentials signed with old keys.checked 11 Oct 2026
- License
- The repository identifies its license as MIT License, copyright 2023 Digital Credentials Consortium.checked 11 Oct 2026
- Multiple issuers
- Tenants allow different signing keys and DIDs to be used for different credentialing purposes.checked 11 Oct 2026
- Production guidance
- The README warns that the shared default signing key is only for testing and evaluation, and says issuers must generate and keep their own signing key private for real credentials.checked 11 Oct 2026
- Purpose
- The app issues signed Verifiable Credentials and allows them to be revoked.checked 11 Oct 2026
- Revocation and suspension
- Optional status management implements Bitstring Status List and can store status lists using database or Git services.checked 4 Oct 2026
- Security guidance
- The README warns that the shared test signing key is unsafe for real credentials and recommends configuring a private key and suggests IP filtering for issuer endpoints.checked 4 Oct 2026
- Setup time
- The project says its four-step quick start should take less than five minutes.checked 4 Oct 2026
- Status storage limit
- The README recommends database-backed status storage for production and testing, and Git-backed storage only for light testing or experiments.checked 11 Oct 2026
- Support and contribution
- The README says pull requests are accepted.checked 11 Oct 2026
- Tenants
- Multiple signing authorities can be configured as tenants, each with its own key and optional bearer-token protection.checked 4 Oct 2026
- Wallet integration
- The README describes importing issued credentials into the Learner Credential Wallet and points to a separate exchange-coordinator for direct wallet exchange.checked 4 Oct 2026
The company
- Founded
- 2018checked 28 Sep 2026
- Headquarters
- United Stateschecked 28 Sep 2026
Alternatives to DCC Issuer Coordinator
- 1
Awero
Free planAndroidiOSWebAPI8.0From €110 a year - 2
Blockcerts
Free planOpen sourceAndroidiOSWebAPI7.7Free plan - 3
SimpleCert
Free planWebAPImacOSWindows7.7From $19 a month - 4
Certifier
Free planWebAPI7.4From $49 a month - 5
CanCred Factory
Free planAndroidiOSWebAPI7.3From C$495 a year - 6
CertSeal
Free planWebAPISelf-hosted7.3From $390 a year