// the take
MaxKey is a Java-based SSO/IAM platform from the Dromara ecosystem, covering OAuth2/OIDC, SAML2, CAS, JWT, and SCIM2 in one box. It's aimed at enterprises and institutions that need a self-hosted identity broker instead of paying for Okta or Azure AD, and judging by the README's sprawling adopter list, that's exactly who's using it, mostly Chinese government, education, and manufacturing orgs.
Genuinely broad protocol coverage in one codebase: OAuth2/OIDC, SAML2, CAS, JWT, SCIM2, Kerberos/SPNEGO domain auth, and WebAuthn/passkey are all there rather than bolted on later. It plugs into infrastructure most Java shops already run (Spring, MySQL, Redis, Tomcat), so there's no new storage engine to operate. The adopter list, even discounted for self-reporting, is long enough and spans enough industries to suggest this has survived real production use, not just demo deployments. Active release cadence (v4.2.0, pushes within the last week).
The English README is almost entirely marketing copy and a download link table; there's no architecture overview, no config walkthrough, no API reference in English, so non-Chinese-speaking teams are stuck reverse-engineering from source or Chinese docs. Primary issue tracking lives on Gitee, not GitHub, so GitHub issues/PRs are a secondary channel with likely slower turnaround. Kubernetes support is a placeholder (deployment/k8s/helm/helm.txt, not actual charts), so anyone wanting to run this on k8s is on their own. For a product whose entire job is identity and access control, the README leans on a GVP award and a customer logo wall instead of discussing audit history, pen-test results, or a real security disclosure process beyond a SECURITY.md pointer — that's a thin signal for something you're trusting with SSO across your org.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →