Developer identity · Compare
Auth0 ships identity for developers. H33 ships identity for the person.
Auth0 solves the developer problem: authenticate my users. H33 solves the user problem: govern my own identity across every surface without depending on a vendor to hold it.
Side by side
Where H33 changes the trade.
| Question | Auth0 | H33 |
|---|---|---|
| Who owns the identity | The relying-party tenant | The person |
| Storage of credentials | Auth0-managed | Not stored · cryptographic signature |
| Cross-service identity | Requires re-integration | One identity, many services |
| Recovery | Vendor-mediated | Guardian-based |
| Post-quantum | Optional / roadmap | Baseline · today |
| API surface | Auth0 SDKs | Auth1 + WebAuthn + full Vault APIs |
Trust status
Runs today. Honest about what's next.
We publish what's shipped and what's coming — the same list on every page.
Runs today
- Vault workflows running in production
- Cryptographic receipts emitted per action
- Immutable audit trail · Object-Locked
- Auth1 · Wallet · Document · Audit APIs
- Post-quantum primitives (Dilithium + Kyber)
- Benchmark v12 · 2,293,766 auth/sec
Coming next
- Public /verify/
/ receipt viewer - Public /replay/
/ decision viewer - docs.h33.you developer documentation
- SOC 2 Type II Certified
- Payment Requests + Rewards adapters
Continue exploring
Passwordless
See it working
Live proof
Switch when it makes sense. Read the receipt now.
Every claim above traces to a real artifact. Start free · or read the platform.