DKAM is the decentralised trust layer for registrars, partnerships teams, careers services and senior leadership. Issue source-verified credentials directly to a graduate's Bluck, evidence verified capability beyond the CV, and keep visibility on outcomes long after graduation. Built to complement the systems you already run.
Issue degrees, diplomas and micro-credentials as tamper-evident, time-stamped attestations bound to a verified individual.
Confirm alumni in bulk through a session-verified queue. No 100 logins for 100 requests.
In-flight learners can already attach verified institutional context to their Bluck while they study.
Every issuance, confirmation and access decision is logged and exportable for governance and accreditation.
Your records team authenticates once, then clears the queue. Designed around real registry and records workflows in universities, colleges and polytechnics.
Credentials are portable across participating organisations and partners. No re-verifying the same evidence from scratch.
Employability rankings, accreditation reviews and government reporting increasingly demand evidence of real capability, not self-reported skills. DKAM turns the credentials you already award into living, verifiable capability records that follow your graduates into work and stay connected to your institution.
Verified capability that hiring teams can trust, traceable back to your institution as the issuing source.
Stay connected to graduate trajectories. Use anonymised signals to inform curriculum, partnerships and careers services.
A credential issued by your institution remains verifiable wherever your graduate works, without bilateral data-sharing agreements.
Confirmed alumni become an authenticated network, not a guess. Useful for advancement, mentoring and employer partnerships.
DKAM is designed to complement, not replace, the systems your institution already depends on. In plain English: your SIS stays your system of record. DKAM becomes the trust layer that turns what you already issue into something portable, verifiable and graduate-controlled.
Student information systems (Banner, PeopleSoft, ITS, SITS, Tribal, Workday Student and similar) remain authoritative. DKAM consumes confirmed records, it does not own them.
Moodle, Canvas, Blackboard or your in-house LMS continues to run delivery and assessment. DKAM issues at the credential layer, after the institution has decided to award.
Salesforce Education Cloud, Raiser's Edge or your alumni database stays in place. DKAM adds a verified, consent-controlled affiliation signal back into it.
Start with a manual issuance console, move to CSV batch, then API or event-based integration when your team is ready. No mandatory rip-and-replace.
Designed to work with institutional SSO and federated identity (SAML, OIDC). Pilots can begin without IT integration and tighten over time.
All issuance and verification events are logged and exportable. Feed them back into your existing reporting, accreditation and audit processes.
Specific integration depth depends on your institution's systems and pilot scope. We confirm what is in place today and what is on the roadmap before any commitment.
Lawful basis, data minimisation and consent are built into the workflow, not bolted on.
Role-based access, row-level data isolation, audit logs and revocable consent for every record.
Designed against WCAG 2.2 AA principles. Accessibility statements published per release as the platform matures.
Every institutional conversation is owned by a named contact at DKAM. Use the route that fits your remit and we will respond personally, not from a generic inbox.
Registrars, vice-chancellor's office, partnerships and senior leadership.
institutions@dkam.ioCareers services, employability teams, employer engagement and outcomes reporting.
careers@dkam.ioData protection officers, information security, legal and accessibility leads.
trust@dkam.ioNamed role holders are assigned per conversation. If a role is between holders, the DKAM founding team responds directly while a permanent contact is appointed.
A simple expression-of-interest sets up a scoped conversation. We agree pilot scope, success measures and a data handling note up front, before any technical work starts.