Clerk
Drop-in authentication and user management for web apps
Clerk handles sign-up, sign-in and everything after it, as components you drop into an application rather than an auth service you wire up yourself. SignUp, SignIn, UserButton and UserProfile render prebuilt flows including social login, multi-factor authentication and account switching, and they restyle with any CSS library and deploy on your own domain. The same set covers multi-tenancy, with components for creating organizations, switching between them and managing members, roles, permissions and invitations, plus a PricingTable component for subscription billing. Machine authentication issues API keys and machine-to-machine tokens for service calls. Plans are metered per application in MRU: the free Hobby plan caps each application at 50,000, Pro includes the same 50,000 and charges two cents a month for each user beyond it, and enterprise SSO connections, satellite domains and longer log retention are priced per connection or per plan.
- Drop-in sign-up, sign-in and user profile components
- Restyle with any CSS library and run on your own domain
- Multi-factor authentication and custom session lifetimes
- Organizations, roles, permissions and invitations for B2B
- Enterprise SSO connections, one included on the Pro plan
- Machine authentication with API keys and M2M tokens
- PricingTable component for subscription billing in-app
- Application and admin logs, with retention by plan
What people are saying about Clerk
62% neutral“Auth? Clerk. Email?”
“thank you @stripe @clerk for filling in most of the gaps”
“just had astra/codex set up my entire clerk social login workflow for google and facebook in about 30 minutes”
“just delete the prompt soup and plug in supabase, clerk, or bubble's native auth. stop trying to build custom security layers from scratch when perfectly safe tools already exist.”
“- Clerk — managed auth and user management”
“clerk is free up to a million active users”
“This almost always comes down to an environment key mix-up between Clerk's Development and Production instances. Clerk keeps dev and prod environments completely separate.”
“i bet your VM is running the development keys instead of production. I did this exact thing on a project last year and lost users for days. Log into your server, cat your env file, and check if the clerk keys start with pk\_test or pk\_live.”
“This feels like you might have multiple Clerk environments (development vs production) and users are being created in the wrong one. Check that your environment variables in production are pointing to your production Clerk instance, not the development one. Users in dev and prod are completely separate in Clerk.”
“I’ve been having an issue while using clerk, every once in a while one of the users contacts me that their user can’t be found. I go online and look at all the users on clerk only to find that they’ve disappearing, I look at the logs on my VM and the user was not deleted and he is in my db.”
“I was working with Clerk and a Go backend and had a hard time finding a proper example of how to handle Clerk webhooks in Go.”
“is it a must to use Clerk which i have worked with before as it handles OTP and which is the main issue for me , and if i do would i need to have the pro plan , and it would take a place in my projects in Clerk”
“Stack: React Native, Expo, @clerk for Auth, Resend for Email, Convex for DB & Cloudflare for image management.”
“- Positive experience with Clerk for 'painless integration' and developer experience.”
“Clerk leans heavily on the interface itself. You see authentication components, organization switching, user management, and other parts of the actual product.”
“I have Connected clerk for sign up. I’m testing the app with expo go on my iOS device and just also Connected post hog for Analytics and using supabase in the back end for storing user chat sessions, etc..”
“For auth stuff, tools like Clerk also have testing support now, so you can run proper E2E tests without using real users. Tbh the useful part of what you’re doing is making the agent actually execute those failure cases instead of just reviewing the code.”
“I am using Clerk on a small project”
“Clerk, Authentik, Zitadel are good alternatives.”
“clerk gives you auth, Strpe gives you payments, but if the database policies aren't right, it's like locking the front door and leaving everything else wide open..”
“Right now I'm running integrations against sandbox twins of the APIs (Stripe, Twilio, Clerk, etc.) directly from the agent, so it can run the failure scenarios before anything ships. No real keys, no prod risk, receipt URL I can check after.”
“Right now our stack is Rollfi for payroll, PostHog for product analytics, Sentry for monitoring and Clerk for auth. We still own the product experience but Im trying to be deliberate about how much of the payroll operation sits with us vs outside the team”
“You have redis, mongo, an RDBMS container, an analytics db, kafka, all the kafka tooling like bookkeeper, then you have outsourced auth liek clerk or supabase (when the whole thing is not just some supabase chimera with edge functions and whatever else supabase is supposed to run outside your infra).”
“I use Clerk but not the Replit-managed Clerk account! I use my own Clerk account!”
“React, convex, vercel, clerk”