Clerk review

Clerk provides authentication and user-management infrastructure for web and mobile apps. Its product materials describe APIs and UI components for sign-in, sessions, and user administration, with support for passwords, social sign-on, passcodes, magic links, and multifactor authentication. It also offers organization features for apps that need team access, including invitations, auto-join, roles, and permissions. Listed framework SDKs include Next.js, React, and Expo; Clerk also offers a CLI and MCP server for agents to configure apps.

The pricing page lists a free Hobby plan, Pro at $25 monthly or $20 per month billed annually, and Business at $300 monthly or $250 per month billed annually. Enterprise pricing is not published. The key cost variable is not just the plan price: Clerk bills for usage above some included limits, and several capabilities have separate charges. So the sensible comparison is the bill at your expected user and feature volume, not the entry price alone.

Clerk brings sign-in, session controls, user administration, and organization management into one service. That can save a team from assembling separate tools for login and multi-tenant access. Its listed sign-in options cover passwords, social providers, passcodes, magic links, and MFA. Session features include active-device monitoring and revocation; the product also lists bot detection and controls for disposable email domains and email subaddresses.

For a project getting started, the pricing page lists unlimited applications and 50,000 MRUs per app on free Hobby, plus up to three dashboard seats. That is a substantial allowance on paper, though Hobby has a seven-day fixed session lifetime and one-day application log retention. Pro costs $25 monthly, or $20 per month billed annually, and includes 50,000 MRUs per app, one SSO connection, one Directory Sync connection, MFA, and custom session lifetime. Business adds 10 dashboard seats, 30-day application and admin log retention, a SOC 2 report, and advanced protections. A Reddit commenter argues that managed auth can make economic sense when developer time and security work are factored in; that trade-off depends on the team.

The headline plan price is only a starting point if usage or enterprise features grow. The pricing page lists MRU overages above 50,000 per app at $0.02 each for 50,001–100,000, then lower per-unit rates at higher tiers. Additional SSO or Directory Sync connections cost $75 monthly each for connections 2–15, with lower rates at higher volumes; Directory Sync billing starts January 1, 2027. Business dashboard seats beyond the included 10 cost $20 monthly each. Satellite domains cost $10 monthly each.

Other line items include US and Canada SMS authentication at $0.01 per message, and billing at 0.7% of billing volume on top of Stripe's listed 2.9% plus $0.30 transaction charge. Enterprise pricing is not published, so larger teams cannot compare its total cost from the public figures alone. One Reddit thread discusses different MAU limits and overage assumptions; those figures do not match the current pricing details here, so verify the live plan definitions before using old estimates. Model MRUs and required add-ons before switching.

Clerk’s Hobby plan is free and includes 50,000 MRUs per app, up to three dashboard seats, and a seven-day fixed session lifetime. Pro costs $25 per month, or $20 per month billed annually, and includes 50,000 MRUs per app, MFA, and custom session lifetime. Business jumps to $300 monthly or $250 per month billed annually—12 times Pro’s monthly price—and adds 10 dashboard seats, 30-day log retention, a SOC 2 report, and advanced protections. Enterprise pricing is not published.

Model usage before moving beyond the included limits. Extra MRUs cost $0.02 each for the next 50,000 per app, with lower rates at higher volumes. Additional SSO or Directory Sync connections start at $75 per month; extra Business seats are $20 monthly. SMS authentication costs $0.01 per message in the US and Canada, while international rates are market rate. B2B Authentication and unlimited impersonations are separate paid add-ons. Directory Sync billing starts January 1, 2027. Annual prices are monthly equivalents billed annually, not month-to-month rates.

Treat a move to Clerk as an authentication migration, not just a UI swap. Before committing, map your existing user records, organization memberships, roles, and session rules to Clerk’s model; those are areas its product supports, but the published materials don’t specify migration tooling or the effort involved. Confirm how you’ll handle active sessions and any sign-in methods your app relies on.

The published materials also don’t publish data-export terms or describe an exit process. Get answers on exporting user and organization data, preserving identifiers, and moving passwords or other credentials before you depend on Clerk in production. Those details can determine how difficult a later move will be. We don’t have Reddit posts or comments in the published material for this review, so we can’t substantiate a claim about why users leave Clerk. For teams with unpredictable growth, model usage-based charges and add-ons before switching; for teams needing only basic sign-in, the listed organization and management features may be more than they need.