Prompt
I’m unhappy with Clerk for a larger SaaS app
Latest observation
Oct 6, 2026
OpenAI APIWeb search: off
Totally fair — Clerk is great for getting started fast, but once a SaaS app gets bigger, people often run into limits around flexibility, pricing, tenancy, advanced auth flows, and vendor lock-in.
If you want, I can help in a few ways:
-
Diagnose what’s bothering you about Clerk
- pricing?
- multi-tenancy / orgs?
- SSO/SAML?
- custom auth flows?
- UI customization?
- session/user management?
- performance or reliability?
-
Suggest better alternatives for a larger SaaS
- Auth.js / NextAuth: more control, self-managed, good if you want to own the stack
- WorkOS: strong for enterprise auth, SSO, SCIM, org management
- Auth0: mature and flexible, but can get expensive
- FusionAuth: self-hostable, good control and enterprise features
- Keycloak: powerful, open source, heavier ops burden
- Supabase Auth: solid if you’re already in Supabase/Postgres world
- Descope / Stytch: modern auth platform options with different tradeoffs
-
Help you migrate off Clerk
- map your current auth setup
- design the replacement architecture
- estimate migration risk
- outline a phased cutover plan
If you tell me:
- your stack,
- what Clerk features you rely on,
- and what you dislike most,
…I can recommend the best replacement and a migration strategy.