TL;DR: Managed auth often wins over self-hosted and custom builds because it bundles uptime, patching, security response, compliance, and broad feature coverage, according to Clerk's guide. Identity governance and recovery still move into the vendor relationship, so the auth stack becomes a long-term governance choice.
Editorial analysis by NHI Mgmt Group, based on content published by Clerk: “What Is Auth-as-a-Service? The Complete Guide - Part 2”.
By the numbers:
- The guide says basic custom authentication takes about 300 hours and $45,000, while enterprise SSO can take 3 to 6 developer-months and $250,000 to $500,000.
- The Keycloak HA sizing docs say 1 vCPU handles roughly 15 logins per second, and 100,000 active sessions consume about 500 MB of RAM per pod.
- The guide says 53% of consumers have enabled passkeys on at least one account, according to FIDO Alliance research cited by Clerk.
Key questions
Q: Why do custom authentication builds create long-term security risk?
A: Custom auth becomes risky because it must continuously get hashing, session handling, recovery, federation, and audit logging right under active attack.
Q: How should organisations evaluate lock-in in authentication platforms?
A: Assess whether identity data, session state, entitlements, and user records can be exported and reconstituted without a redesign.
Q: When should teams choose managed auth-as-a-service instead of self-hosting?
A: Choose managed auth when the team needs fast delivery, standard login patterns, broad feature coverage, and a lower operational burden than running authentication internally.
Practitioner guidance
- Define the operating model for authentication first Map who owns uptime, patching, incident response, and audit evidence before selecting a managed or self-hosted path.
- Separate identity portability from feature selection Document how user records, memberships, session claims, and recovery data can move if the provider or platform changes.
- Use workload and customer scale as decision gates Set explicit thresholds for MAUs, SSO requirements, and compliance deadlines so the auth choice matches operational reality.
Bottom line: Managed authentication reduces operational burden, but it also shifts identity governance, auditability, and recovery responsibilities into the vendor relationship.
Glossary terms: Auth-as-a-Service, Self-Hosted Authorization, Identity Portability, Custom Authentication Backend
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Authentication has become a lifecycle governance problem, not a code choice. The managed versus self-hosted decision changes who owns patching, auditability, abuse response, and data portability for the full life of the product. That means IAM teams should evaluate auth platforms as governed identity services, not as interchangeable implementation shortcuts.
A question worth separating out:
Q: What should IAM teams compare when weighing managed versus self-hosted auth?
A: Compare who carries security operations, compliance evidence, incident response, and scale management, not just price or feature lists. The right choice is the one that matches the organisation's ability to run authentication as a governed service over time, not just at go-live.
👉 Read our full editorial: Managed vs self-hosted authentication: where AaaS fits best