Connect your apps.
Register OIDC applications with exact redirect URIs and required PKCE. Link an upstream OIDC provider using explicit account mappings.
OIDC / AUTHORIZATION CODEA simpler way to connect people and applications. Own your OIDC identity layer, see what’s happening, and keep your keys.
No signup for the demo. No vendor account to self-host.
Start with one app. Add your people. Understand every sign-in. A small, inspectable foundation you can run yourself.
Register OIDC applications with exact redirect URIs and required PKCE. Link an upstream OIDC provider using explicit account mappings.
OIDC / AUTHORIZATION CODEInspect sign-ins and administration events. Export audit data. Read authenticated Prometheus metrics and database usage.
AUDIT / METRICS / LIMITSRun the Community server without a vendor account or per-user license. Use the same API from the console and CLI.
APACHE 2.0 / SELF-HOSTEDBeta scope: single-instance OIDC. Built-in MFA, SAML, SCIM, high availability, and hosted Cloud are on the roadmap. Read the current limits →
Create users. Register apps. Inspect logs.
Give the mouse a break.
# From a checked-out repository $ npm ci $ npm link # Your infrastructure. Your users. $ mayoauth users list $ mayoauth apps list $ mayoauth logs --export $ mayoauth doctor
Core identity belongs in the open. Managed operations are where the commercial service will earn its keep.
Your servers. Your data. Your call.
Same open foundation. Hosted for you.
For teams that want someone on call.
No security tax. OIDC, audit export, and core authentication stay in Community. Planned built-in MFA will be part of Community too.
Our open-source promise ↗Try the 20-user sample workspace. No signup.