Feature Comparison: dracory/auth vs WorkOS

Comparison of github.com/dracory/auth with WorkOS, the managed enterprise-identity platform.

High-Level Differences

dracory/authWorkOS
TypeGo library embedded in your appManaged SaaS (enterprise identity)
Data ownershipYour database, your schemaVendor's platform
DeploymentNo extra infrastructureAPI dependency
PricingFree (license)Per-MAU pricing

Feature Comparison

dracory/authWorkOS
Email/password✅✅
Otp (codes/links)✅✅
Magic links✅✅
MFA / TOTP❌✅
SSO (SAML/OIDC for enterprises)❌✅ Flagship feature
SCIM / directory sync❌✅
Audit logs✅ log/slog hooks✅ Hosted
Impersonation✅ Built-in⚠️ Admin portal
Data stays in-house✅ Any DB❌ Vendor-hosted
Works offline / air-gapped✅❌
Multiple login methods simultaneously✅ Composable via NewMultiMethodAuth + types.Method (otp, magiclink, password, authknight, custom methods){mm}
Remember-me (extended sessions)✅ Built-in opt-in session extension{rm}

Legend: ✅ built-in · ⚠️ partial/conditional · ❌ not available

Branding & Layout Options

Aspectdracory/authWorkOS
Full layout control✅ FuncLayout wraps any page body in your own site shell (own <head>, nav, footer)❌ Hosted AuthKit only; layout is WorkOS-rendered
Theming / CSS✅ ThemeCSS (any hosted stylesheet / Bootlegance) + CustomCSS inline overrides⚠️ Branding editor: logo, colors, dark mode; no custom CSS/layout
Brand name / logo✅ BrandName, BrandTagline, BrandLogoURL rendered above the login card✅ Logo, colors, custom domain
Email templates✅ Per-flow FuncEmailTemplate* callbacks — full control✅ Customizable templates

When to Choose WorkOS

hosted audit trails — that's WorkOS's entire reason to exist.

When to Choose dracory/auth

impersonation — no vendor, no per-MAU pricing, data never leaves.