Peer Comparisons

Feature comparisons of github.com/dracory/auth against peer authentication solutions. Each document covers a high-level positioning table, a feature matrix, a branding & layout options table, and guidance on when each option is the better fit.

PeerTypeDocument
SuperTokensOpen-source auth service + SDKssupertokens.html
Auth0 (Okta)Hosted SaaS IdPauth0.md
ClerkHosted SaaS, component-firstclerk.html
Firebase AuthGoogle managed servicefirebase-auth.html
KeycloakSelf-hosted IAM serverkeycloak.html
Ory KratosOpen-source API-first identity serviceory-kratos.html
Better AuthTypeScript embedded librarybetter-auth.html
HankoOpen-source passkey-first authhanko.html
AutheliaSelf-hosted SSO portal / proxy authauthelia.html
AuthentikSelf-hosted identity providerauthentik.html
ZITADELGo-based identity platformzitadel.html
WorkOSManaged enterprise identityworkos.html

Summary Positioning

dracory/auth's niche: an embedded Go library with built-in server-rendered UI, JSON API, middleware, impersonation, and rate limiting — storing everything in your database via callbacks, with zero external services and zero per-MAU cost.

Four login methods ship today — email OTP, magic link, username/password, and delegated AuthKnight — composable behind one mux via NewMultiMethodAuth and extensible through the public types.Method interface (custom methods need no library change). Post-authentication behavior (allowlists, find-or-create, session creation, cookies, redirects) is hook-driven via types.PostAuthHooks, with remember-me session extension and per-route rate limits built in.

Its main gaps vs the field: social/OAuth login (except via AuthKnight), MFA/passkeys, enterprise SSO (SAML/OIDC), multi-tenancy/organizations, and hosted user-profile UI.