Identity infrastructure without hidden shortcuts.
OpenProof keeps proof, identity, sessions and authorization distinct while giving applications one consistent account surface.
Quickstart
Choose the proof method
Password, passkey, social provider, wallet signature or enterprise federation starts a protocol-specific ceremony.
Verify the proof
OpenProof validates signatures, state, nonce, PKCE, issuer/audience and replay protections where the protocol requires them.
Resolve one canonical identity
A verified provider subject maps to an explicit linked identity. Email is not used as a silent account-merge key.
Issue controlled access
Sessions and OAuth/OIDC tokens carry the assurance and authorization context required by the relying application.
Self-hosting model
Run OpenProof inside your own trust boundary. Put it behind your HTTPS entry point, keep provider credentials in your secret manager, and choose the datastore and service layout that fit your environment.
public origin https://auth.example.com application your web or API service identity core OpenProof state your PostgreSQL-compatible datastore secrets your secret manager / environment
Examples in this documentation are intentionally generic. Do not copy a filesystem path, port, hostname or callback URI unless it matches your deployment.
API surface
| Method | Path | Purpose |
|---|---|---|
| GET | /health/ready | Readiness check |
| GET | /auth/providers | Advertised authentication providers |
| POST | /auth/passkey/options | Start a WebAuthn ceremony |
| GET | /.well-known/openid-configuration | OIDC discovery |
curl https://auth.example.com/health/ready
{"status":"ok"}The Developer Portal includes an isolated browser sandbox, identity workbench and API Explorer generated from OpenProof's OpenAPI 3.1 contract, currently covering 87 paths and 111 operations.
Next steps
Install OpenProof
Package installation, PostgreSQL, providers, email delivery, Nginx and TLS.
↗{ }API Reference
Search the complete OpenAPI contract and copy integration examples.
↗+Configure providers
Redirect URIs, credentials and provider-specific integration rules.
↗</>Inspect source
Build instructions, deployment templates and implementation details.