Clerk

Hosted user management with drop-in sign-in UI components, sessions and organizations.

Works with AI agents:llms.txtMCPCLIBuilt into Replit
Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Clerk is a hosted user-management service. Instead of writing sign-up, sign-in, password reset, MFA and profile screens yourself, you add Clerk's components to your app and Clerk stores the users, runs the flows and keeps the sessions.

Each Clerk application gets its own Frontend API instance, located through your publishable key, plus a Backend API you call with a secret key for admin work like listing or banning users. Sessions use a hybrid model: a long-lived client token sits on Clerk's domain, while your app receives a session JWT that lives only 60 seconds and that the frontend SDK refreshes in the background, so your server just verifies a signature on each request. Official SDKs cover Next.js, React, Expo, Astro, Nuxt, Vue, React Router, TanStack Start, native iOS and Android, with backend SDKs for Express, Fastify, Go, Python, Ruby and others.

For a small team the useful pieces are the prebuilt components (styleable with CSS, though their markup and flow order are fixed), Organizations with roles for B2B apps, enterprise SSO over SAML or OIDC with directory sync, and built-in bot protection, breached-password checks and account lockout. Clerk is cloud-only and runs in the US.

It is a poor fit if you need user data held in a specific region (Clerk does not offer data residency) or want users in your own database; you sync what you need through webhooks or the Backend API. Once or twice a year a maintenance window blocks new sign-ins while signed-in users keep access.

Where it fits

How Clerk itself is built

4 tools, from its own code, website and Product Hunt page.

Who uses it

307 makers' products, each linked to the source that shows it, and 11 open-source projects that declare it in their code.

The maker says so 101Subprocessor list 13Seen on the website 277Declared in code 26How evidence is collected →
Outlit AIAI Agents for your SaaS Deals

“Clerk makes it super easy to handle auth state in our app, handle user roles and permissions, and add the latest sign-in methods.”

AuthenticationMaker says so +2 · source ↗
BrewDesigns and sends marketing emails and email automations from a plain-English descriptio…

“Auth done right. Drop it in, configure, move on. We never think about login flows.”

AuthenticationMaker says so +2 · source ↗
KatalystThe AI agent that works your Salesforce Pipeline

“Auth is one of those things you cannot get wrong when you're plugged into a team's Salesforce and their data. Clerk let us get secure sign in and user management right from day one, without building it ourselves.”

AuthenticationMaker says so +2 · source ↗
GroThe best way to prospect and sell with AI

“We needed production-ready authentication without slowing the team down. Clerk let us ship securely from day one and stay focused on core product work. Setup was fast, UX is polished out of the box, and it scales cleanly without us constantly revisiting edge cases.”

AuthenticationMaker says so +2 · source ↗
IgnitionRAGMultimodal RAG platform, from POC to production in minutes

“We needed auth that handles both individual users and multi-tenant organizations out of the box. Clerk gave us JWT-based auth, org management, RBAC, and webhook sync — all with a clean React SDK and middleware for Next.js. We evaluated Auth0 (too complex for our stage), Supabase Auth (no native org support), and NextAuth (too much DIY). Clerk let us ship secure multi-tenant auth in days instead of weeks, so we could focus on the RAG pipeline instead of reinventing session management.”

AuthenticationMaker says so +2 · source ↗
NovuNotification infrastructure for sending multi-channel messages (email, in-app, SMS, chat…

“Clerk helps us with handling the user and workspaces identities with beautiful components”

AuthenticationMaker says so +1 · source ↗
VC BoomHelps founders fundraise: scores pitch decks, matches them with investors and drafts out…

“Even sitting on Supabase, I reached for Clerk because its prebuilt components got sign-in, sessions, and social login working in about an hour, and they look good out of the box. Auth0 is powerful but heavier than I needed for launch speed.”

AuthenticationMaker says so +1 · source ↗
ZenVeilFind, understand and fix security issues faster

“Authentication is one of those areas where mistakes can become security problems. Clerk allowed us to implement secure sign-in, session management, and user onboarding while keeping the experience smooth for developers using ZenVeil.”

AuthenticationMaker says so +1 · source ↗
EmailTempleThe AI studio for on-brand emails and whole sequences

“Auth that took an afternoon to wire up instead of a sprint. EmailTemple's free tier means thousands of signups need to just work — Clerk handles the whole sign-up / sign-in / webhook flow, and the server-side auth() API plays clean with Next.js App Router. Worth it for the time alone.”

AuthenticationMaker says so +1 · source ↗
GraphBitGraphBit is an open-source framework for building AI agents, with a Rust core and a Pyth…

“Clerk handled auth out of the box so we could focus on building the actual product. GitHub OAuth, session management, and user management all done in a day. For a small team shipping fast, that time saving was the deciding factor.”

AuthenticationMaker says so +1 · source ↗
Indie Hacker StacksSee tech stacks of indie products

“I would ship as fast if I wasnt using Clerk. I use it for all my products, has a good free tier and it's customisation is so advanced as you want it to be, su all scenario's are achievable. Su”

AuthenticationMaker says so +1 · source ↗
DeckThe most capable AI assistant with its own inbox

“Has made our ability to manage onboarding super seamless - good out of the box functionality and ecosystem of integrations.”

AuthenticationMaker says so +1 · source ↗
Layout.devTurn ideas into applications — in seconds

“Clerk makes auth integration super simple. From magic links to social logins, it just works out of the box, saving us tons of time.”

AuthenticationMaker says so +1 · source ↗

Open source: a project that declares Clerk as a dependency in its public code — verifiable, but not necessarily a live product.

What makers say

75 makers on why they use Clerk, in their own words on Product Hunt.

Quiver is multi-tenant from the first line: a workspace IS a Clerk Organization, not a row we invented. That removed a quarter of work. We never built an invites table, a roles system, or a members screen. OrganizationProfile is the team page, and seat limits are enforced by maxAllowedMemberships, so hitting a plan cap happens inside Clerk's own invite flow instead of a custom error page nobody reads. What actually decided it: Clerk is also an OAuth authorization server, with dynamic client registration and PKCE. That is what let Claude.ai connect to a customer's Quiver workspace as a custom connector. We pointed our MCP server at Clerk and shipped. Everything else we looked at would have meant standing up our own authorization server first.
Quiver GTMSep 2026 ↗
Clerk makes authentication effortless, with a developer-friendly API and prebuilt UI components that save time. Unlike Auth0 or Firebase Auth, Clerk provides first-class support for modern frameworks like Next.js and integrates seamlessly with Supabase and Vercel. The built-in user management, multi-factor auth, and social logins simplify everything, while its flexible session management ensures security without complexity. For PullSense, it made user authentication seamless without the usual headaches.
Pull SenseSep 2026 ↗
We initially began building user management in-house but quickly realized that creating a secure and seamless user experience involved more complexity than anticipated. It was clear that continuing down this path would pull valuable engineering resources away from our core product. Clerk provided a comprehensive solution, covering everything from account life cycle to payment integration. This shift allowed us to focus on our primary goals while still ensuring a great user experience.
AgentQLSep 2026 ↗
We needed auth that handles both individual users and multi-tenant organizations out of the box. Clerk gave us JWT-based auth, org management, RBAC, and webhook sync — all with a clean React SDK and middleware for Next.js. We evaluated Auth0 (too complex for our stage), Supabase Auth (no native org support), and NextAuth (too much DIY). Clerk let us ship secure multi-tenant auth in days instead of weeks, so we could focus on the RAG pipeline instead of reinventing session management.
IgnitionRAGSep 2026 ↗
We use Clerk to handle all our user sign-ups and auth flows so we didn't have to build auth logic from scratch. It gives us straightforward role and permission management out of the box, which keeps our app's access control clean. On top of that, the built-in user impersonation is great for me (as a non technical founder) we can jump directly into a user's account to see their exact view, reproduce bugs as them and (if we have the bandwidth) fix bugs in near real time as a byproduct.
OutcomeSep 2026 ↗

Loved and watch-outs

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.

Most loved
  • Sign-up, sign-in, sessions and social login get wired in an afternoon instead of a sprint. PHPH 2
  • Organizations, roles and billing come built in, covering multi-tenant B2B apps without custom identity work. PHPH 2
  • Prebuilt UI components, including profile and settings pages, look polished out of the box. PH
  • Tight Next.js integration, with a server-side auth helper and middleware for the App Router. PH
Watch-outs
  • Outsourcing auth means a Clerk outage or account problem locks your users out, and the dependency is hard to reverse. HNHN 2HN 3HN 4
  • Costs climb with SSO, MFA, passkeys and branding removal, and some switched to cheaper open-source options. HNHN 2HN 3HN 4
On Product Hunt 5.0★ · 112 reviews
easy integration 9comprehensive solution 7free tier 5fast setup 4flexible auth 4prebuilt UI components 4developer APIs 3secure login flows 3
Read the reviews on Product Hunt ↗

Reliability and open issues

Incidents on its status page13 in the last 90 days, 1 major · 25+ in the last year
  • minor Dashboard increased latency Oct 2026
  • minor Development instances only - Apple rejecting emails Sep 2026
  • minor Delays in webhook delivery Sep 2026
From its own status page, 2026-10-02. Vendors decide what they post; one page can cover several products.

Who switches

Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general. Open a row to see the pull requests.

Supabase → Clerk54 PRs
Firebase → Clerk9 PRs
Auth0 → Clerk6 PRs
Better Auth → Clerk4 PRs
WorkOS → Clerk4 PRs
Clerk → Supabase53 PRs
Clerk → Better Auth33 PRs
Clerk → Firebase8 PRs
Clerk → WorkOS6 PRs
Clerk → Auth03 PRs

On Product Hunt, people weigh it against: PropelAuth, WorkOS, Auth0, Stytch, Kinde, Hexclave (Stack Auth), Descope, BoxyHQ, Appwrite, Logto.

Questions makers ask about Clerk

Which frameworks and languages does Clerk support?

Clerk maintains SDKs for Next.js, React, Expo, Astro, Nuxt, Vue, React Router, TanStack Start, Chrome extensions, Electron, iOS and Android, plus backend SDKs for Express, Fastify, Go, Python, Ruby on Rails, Java, PHP and C#. SvelteKit, Angular, Hono and Flutter are covered by community-maintained SDKs. source ↗

Can I export my users if I leave Clerk?

Yes. Admins can export a CSV of all users from the dashboard, and the export includes password hashes so users can keep their passwords in the next system. source ↗

Can I import users from another auth provider?

Yes. You create users through the Backend API's CreateUser endpoint, passing existing password hashes and the algorithm used, or use Clerk's open-source migration tool that reads JSON or CSV. A gradual trickle migration is also documented. Existing sessions end at cutover, and users cannot be moved from a development instance to production. source ↗

Where is user data stored, and is it GDPR compliant?

Clerk is hosted in the US and does not offer regional data residency. EU, UK and Swiss data is transferred under the EU-U.S. Data Privacy Framework, and a DPA is published. source ↗

Is Clerk SOC 2 and HIPAA compliant?

Clerk has held SOC 2 Type 2 and HIPAA since May 2022. The SOC 2 report is available on the Business plan and above, and a HIPAA BAA is signed only on the Enterprise plan. source ↗

What happens to my app during Clerk maintenance?

Once or twice a year Clerk enters maintenance mode: signed-in users stay signed in and sessions keep refreshing, but new sign-ups, sign-ins and changes to user or organization data return a 503 error until it ends. source ↗

What are Clerk's API rate limits?

The Backend API allows 1,000 requests per 10 seconds on production instances and 100 on development instances, with tighter limits on some endpoints such as invitations. Sign-in and sign-up attempts from the frontend are limited per IP address. source ↗

Does Clerk support enterprise SSO?

Yes. It supports SAML and OIDC enterprise connections with providers such as Okta, Microsoft Entra ID and Google Workspace, along with just-in-time provisioning and SCIM directory sync. source ↗

Is Clerk free?

Yes — there is a free tier a small product can run on; paid use starts at $25/mo. source ↗

Is Clerk open source or self-hostable?

Not open source, and hosted only.

Can AI coding agents work with Clerk?

It serves an llms.txt docs index; it has an official MCP server (io.github.clerk/mcp-server); it has an official CLI (clerk); Replit set it up natively.

Who uses Clerk?

307 makers' products we track, each with a source, and 11 open-source projects declare it in their code. source ↗