Customer identity (CIAM)
What is Clerk? An introduction to Clerk Inc.'s hosted authentication platform
Clerk is a hosted authentication and user management platform for modern web and mobile apps. It provides SDKs, APIs and prebuilt components that handle sign-up, sign-in, user profiles and session management. It is aimed at developers, B2B SaaS teams and teams that use coding agents.
- Tool
- Clerk
- Made by
- Clerk Inc.
- Official site
- clerk.com
- Category
- Customer identity (CIAM)
Who makes Clerk
Clerk is made by Clerk Inc. The company develops the platform, its SDKs and APIs, and the prebuilt components that developers add to their applications.
The official website is linked below. It is the place to confirm current product details directly with the vendor.
Official website: clerk.com
What Clerk is for
Clerk provides authentication and user management that is purpose-built for modern web frameworks. Instead of writing the account system for an application from scratch, a development team uses Clerk to handle the common identity tasks: sign-up, sign-in, user profiles and session management. These are delivered through SDKs, APIs and prebuilt components, so teams can choose how much of the interface they build themselves.
For teams that would rather not build account pages at all, Clerk includes an Account Portal. It provides hosted sign-in, sign-up and profile management pages, which means the screens users see for those tasks can be served by Clerk rather than by the application.
Who Clerk is for
The vendor describes its audience as developers building web and mobile apps, B2B SaaS teams, and teams using coding agents. Clerk is a developer-facing product: it is integrated into an application's code and configured by the people who build that application.
B2B SaaS teams are a particular focus because customers of such products usually belong to companies rather than acting as isolated individuals. Clerk's workspace and membership features address that structure. For teams working with coding agents, Clerk offers a CLI and an MCP server, so developers and agents can configure Clerk from their development tools.
Notable capabilities
Clerk covers sign-in methods, account security, session handling and multi-tenant features. The capabilities below are the ones the vendor documents.
- Social sign-on: Clerk offers more than 20 social sign-on options, so users can sign in with accounts they already have.
- One-time passcodes: email and SMS one-time passcodes are supported, with brute force prevention built in.
- Session lifecycle: Clerk manages sessions from start to finish, including device monitoring and revocation.
- Organizations: workspaces, memberships, invitations, roles and permissions give B2B SaaS products a ready-made way to model customer companies and their members.
- Enterprise SSO and Directory Sync: these are included alongside Organizations for business customers.
- Application-wide MFA: multi-factor authentication can be enforced across an application with a single Dashboard toggle.
- Attack protection: Clerk includes bot protection, account lockout, rate limiting and user-enumeration protection.
- Password screening: passwords are checked against HaveIBeenPwned's compromised credentials database.
How Clerk fits customer identity (CIAM)
Customer identity, often shortened to CIAM, covers how the end users of an application register, sign in and manage their accounts. Clerk sits in this category as a hosted service that a development team adds to its product. It is distinct from tools that manage a company's own employees, because the people it signs in are the customers or members of the application being built.
Clerk also touches several of the areas Lockhelm covers more broadly. Its enterprise SSO and Directory Sync relate to single sign-on and identity, its MFA enforcement relates to multi-factor authentication, and its roles and permissions relate to access control. It does not position itself as a password manager.
On compliance, Clerk has been SOC 2 Type 2 certified since May 2022, and it complies with GDPR through the EU-U.S. Data Privacy Framework. One point to weigh during evaluation: Clerk does not offer regional data residency, and data is hosted on US infrastructure.
Frequently asked questions
What is Clerk used for?
Clerk is used to add authentication and user management to web and mobile apps. It handles sign-up, sign-in, user profiles and session management through SDKs, APIs and prebuilt components.
Who develops Clerk?
Clerk is developed by Clerk Inc. Its official website is https://clerk.com.
Does Clerk support SSO and multi-factor authentication?
Yes. Clerk includes enterprise SSO and Directory Sync, and MFA can be enforced application-wide with a single Dashboard toggle.
Does Clerk offer regional data residency?
No. Clerk does not offer regional data residency, and its data is hosted on US infrastructure.
Can Clerk be configured from development tools?
Yes. Clerk offers a CLI and an MCP server so developers and agents can configure Clerk from their development tools.
Lockhelm is independent and is not affiliated with Clerk Inc.. Product names belong to their owners. Features change; confirm details on the official website.