Four credential formats
VC-JWT, W3C VC 2.0 (JWT-secured), VC 1.1 with JSON-LD Data Integrity proofs, and SD-JWT VC with selective disclosure — one template can be rendered in any of them.
VC Platform
Issue and verify Verifiable Credentials in W3C VC 1.1, VC 2.0, and SD-JWT VC — over OpenID4VCI/VP 1.0 Final or a direct REST API, with Bitstring Status List revocation and a tamper-evident audit trail.
Standard wallet protocols
OpenID4VCI 1.0 Final issuance (pre-authorized code flow) and OpenID4VP 1.0 Final presentation with DCQL, alongside a direct REST API for integrations that don’t need a wallet in the loop.
Revocation built in
Bitstring Status List v1.0 — declare a status mechanism on a template and every issued credential becomes revocable, checked fail-closed at verification time.
Multi-tenant by construction
Org-scoped everything, enforced twice: app-layer scoping plus Postgres row-level security, with private keys isolated in their own signing service.
Questions and issues
Section titled “Questions and issues”This documentation is meant to be a conversation, not a monologue — ask questions in GitHub Discussions and report problems via GitHub Issues.