For IT departments and providers
A layer, not a replacement.
ProofLayer replaces no campus management system and no examination administration. It adds exactly what they cannot do: a credential that stays verifiable outside your systems. Containerised, with PostgreSQL and object storage — in your own data centre, at a regional provider, or with us.
Single sign-on
OIDC or SAML against your existing identity management — Shibboleth/eduGAIN, Keycloak, Entra ID. No second user directory.
REST API
Every function of the interface is available as an API: issue, revoke, query status, verify. Documented with OpenAPI.
Webhooks
ProofLayer pushes events back to you — issued, anchored, claimed, revoked. Your system does not have to poll.
Bulk issuance
A whole graduating cohort in a single run, by file import or API — not record by record.
Roles & tenants
Permissions separated by institution, faculty and role. One deployment, many universities — with no data bleeding across.
Keys stay in the backend
Private keys never leave the backend. The frontend sends no network transactions and holds no key material.
Where it runs
Your data centre, a regional provider, or ours.
Self-hosted
Pull the containers, bring a PostgreSQL instance and object storage, and run it entirely inside your own infrastructure. The source code is open, so nothing is opaque to your operations team.
Regional provider
The same containers at a hosting partner of your choice — useful where procurement requires a specific jurisdiction or an existing framework contract.
Operated by us
We run the deployment under a Support & Care agreement, with agreed response times and security updates. You can move it in-house later without reissuing a single credential.
Trust is not claimed.
It is calculated.
Let us take one degree programme and show you. Four to six weeks, on the test network, with no production data.
Motseki Khoarai
Team Lead, Open Elements
