Issue credentials once.
Verify in seconds.
Modernize issuance without changing academic workflows. Provide instant verification for employers, embassies, banks, and partner institutions, backed by cryptographic proofs and lifecycle controls.
Manual verification is a hidden cost center.
Every year, universities receive hundreds or thousands of verification requests from employers, embassies, banks, and partner institutions. Each request triggers a manual process, phone calls, emails, letters, internal lookups, that consumes staff time and creates delays for everyone involved.
Employers, embassies, and banks wait days or weeks for manual confirmation from registrars.
Dedicated staff handle phone calls, emails, and letters, a hidden cost center that scales with graduates.
Counterfeit diplomas are increasingly difficult to detect. Universities bear reputational risk when fakes circulate.
No consistent way for international institutions to verify credentials across borders.
Who it serves.
Every institutional stakeholder in the credential verification chain, from issuance to final employment or accreditation decision.
Problem: Drowning in manual verification requests
Issue credentials once with cryptographic proof. Verifiers check independently, no registrar involvement needed.
Problem: Waiting days or weeks for diploma confirmation
Instant verification via PDF upload or TDOC scan. Clear pass/fail verdict with issuer, field, and status details.
Problem: Relying on institutional trust for foreign credentials
Verify authenticity independently without contacting the issuing university. Evidence is defensible across jurisdictions.
Problem: No standard way to validate transfer credentials
Machine-readable verification for academic partnerships. Trust credentials from partner universities programmatically.
Problem: KYC requires education verification for certain products
Integrate credential checks into onboarding workflows via API. Automated verification without manual document review.
Problem: Stuck waiting for verification responses
Share verifiable credentials directly. Employers and institutions verify without calling the university.
Three steps. Cryptographic certainty.
No changes to academic workflows. ANANKE integrates with existing issuance processes and adds a trust layer that makes every credential independently verifiable.
The university issues diplomas, transcripts, or certificates through the ANANKE console. Each credential is hashed, timestamped, and stored with cryptographic proof. Optionally, a TDOC DataMatrix code is stamped onto the physical or PDF document.
The graduate shares the PDF (by email, portal, or in person) or the physical document with the TDOC code. No special software needed to share, credentials are standard PDFs or printed documents.
An authorized verifier (employer, embassy, bank, partner institution) checks the credential using one of two methods: PDF upload or TDOC scan. They receive an immediate verdict, authentic or not, along with approved metadata fields.
Two ways to verify.
Digital or physical. Both produce the same cryptographic verdict. Verifiers choose the method that fits their workflow.
PDF Upload
Upload the credential PDF to the ANANKE verification gateway. The system rehashes the document and compares it against the stored cryptographic proof. If the file has been altered, even a single byte, the verification fails.
Digital workflows, email-based sharing, bulk verification
TDOC Scan
Scan the DataMatrix code on the physical or printed document using the ANANKE Mobile app. The TDOC code carries or points to a cryptographic payload that resolves to the full verification record. Works for in-person verification at reception desks, interviews, and embassy counters.
In-person verification, physical documents, reception desks, field verification
Clear verdicts, not cryptographic noise.
Verifiers do not need to understand cryptography. They see human-readable results that answer the questions they care about.
Document is genuine, unaltered, and currently valid. Issued by University of [Name] on [date]. Hash matches stored proof.
Document hash does not match any known credential. Either the document has been altered, or it was never issued through this system.
Trust guarantees for every credential.
Every credential issued through ANANKE carries these guarantees. They are verifiable independently, without trusting the issuer, relying on internal databases, or contacting the university.
Proof of Existence
This credential existed at or before a given moment. The timestamp is anchored and cannot be backdated.
Proof of Integrity
This exact content has not been altered since issuance. Even a single character change is detected.
Proof of Origin
This credential was issued by the claimed university. Origin is cryptographically bound to the issuing organization.
Proof of Custody
Who was responsible for this credential at each lifecycle step. Accountability is defensible.
Lifecycle Status
Is this credential currently valid, revoked, or replaced? Status is checked at verification time.
Tamper-evident Audit Trail
Every issuance, verification, revocation, and replacement is logged in a tamper-evident trail.
The bridge between physical and digital.
TCODE is a secure 2D code (DataMatrix) stamped onto physical or PDF documents. TDOC is the document-specific implementation, binding the physical credential to its cryptographic verification record.
When a verifier scans the TDOC code with the ANANKE Mobile app, it resolves to the verification record and displays the same verdict as PDF upload, authentic or not, with approved metadata.
Minimal data encoded in the DataMatrix. The code points to the verification record on the ANANKE gateway. Requires network connectivity for verification.
Protected payload encoded directly in the DataMatrix. Supports offline-capable verification for field environments. Available in later releases.
TCODE uses DataMatrix, a higher-density format with better error correction. Often called "QR code" in conversation, but technically distinct and more secure for payload protection.
Student data stays private. Always.
ANANKE is privacy-preserving by architecture, not just policy. The system is designed so that sensitive data cannot leak, even to ANANKE itself.
No personal data on-chain
Only cryptographic roots are anchored externally. Student names, grades, and PII stay private within institution-controlled infrastructure.
Policy-controlled disclosure
The university decides which metadata fields verifiers see. A verifier might see the degree title and status, but not the student's grades or personal details.
Minimal verification
Verifiers get the answer they need, authentic or not, without accessing the full student profile or academic record.
Tenant isolation
Each university operates in a separate trust domain. One institution cannot access another's credentials, proofs, or verification logs.
GDPR-aligned data handling
Designed for compliance with data protection regulations. Data minimization, purpose limitation, and access controls built in.
Pilot approach
We start small and prove value fast. Each pilot scenario tests a different verification pathway.
Scenario 1: PDF Verification
University issues a batch of credential PDFs. Verification is tested via the PDF upload gateway. Focus: hash-based integrity, lifecycle status, and verifier experience.
Scenario 2: TDOC Physical
University issues physical diplomas with TDOC DataMatrix codes stamped on the document. Verification tested via ANANKE Mobile scan. Focus: physical-digital binding, scan reliability.
Scenario 3: Employer Integration
Select employers verify candidate credentials using the ANANKE gateway. Focus: verifier onboarding friction, verdict clarity, and workflow integration.
Important: What ANANKE is and is not
ANANKE provides verifiable evidence and tamper-detection, not legally qualified electronic signatures. The university product uses ANANKE Trust and TCODE. ANANKE Sign (remote qualified electronic signatures, DGSSI/eIDAS-aligned) is a separate product line and is not included in the university solution. No qualified signature or seal claims are made by ANANKE Trust or TCODE.
Frequently asked questions.
Is ANANKE a blockchain-based solution?
No. ANANKE uses cryptographic proofs and hash-based evidence. Only cryptographic roots are optionally anchored to external trust anchors (which may include distributed ledgers). No student data, document content, or PII is ever written to any public chain.
Does ANANKE provide qualified electronic signatures?
Not in the university product. ANANKE Trust and TCODE provide verifiable evidence and tamper-detection, not legally qualified signatures. ANANKE Sign (a separate product line) will address qualified signatures when regulatory certification is obtained.
What happens if a credential needs to be revoked?
Universities can revoke or replace credentials through the ANANKE console. The lifecycle status is updated immediately and reflected in all subsequent verification attempts. Revocation events are logged in the audit trail.
Can graduates verify their own credentials?
Yes. Graduates can verify their credentials using the same methods available to any verifier, PDF upload or TDOC scan. This helps them confirm their documents are authentic before sharing with employers.
How does cross-border verification work?
Verification is not geographically restricted. Any authorized verifier with access to the verification gateway can check a credential regardless of location. The cryptographic proof does not depend on institutional trust or local infrastructure.
What if the university changes its systems or ceases to exist?
Proofs are designed to outlive the systems that created them. Cryptographic evidence is anchored independently and remains verifiable even if the issuing institution changes vendors, migrates systems, or ceases operations.
How long does integration take?
The pilot program is designed for minimal disruption. Universities do not need to change their academic workflows, ANANKE integrates with existing issuance processes. Initial setup typically involves credential template configuration and a small batch test.
What document types are supported?
Currently focused on PDF credentials: diplomas, transcripts, certificates, attestations, and official letters. The system is designed to support additional formats as institutional needs evolve.
Ready to modernize credential verification?
Interested in modernizing your credential verification? Get in touch to discuss a pilot program tailored to your institution.
