Enable users to sign-in to your application using their Base accounts, Coinbase's Layer 2 blockchain
We’re excited to announce that Clerk has integrated Base Account. Base is an on-chain stack incubated by Coinbase that makes building, earning, and owning simple and accessible. Now, anyone can "Sign-in with Base" and their account details will follow them into Clerk.
Smart wallet technology makes sign-in fast. By combining Base’s open-internet foundation with Clerk’s developer-first authentication, we make it simple for builders and users to connect in one secure and seamless flow.
B2B applications can now enforce organization membership much more easily
Starting today for new applications, when you enable our Organizations featureset, your users will be required to create or join an organization. Previously, we defaulted to allowing a "Personal Account" which caused many of you building B2B applications to add workarounds to force organization membership. We had it backwards.
And if you're using Clerk components, this just works. Users are immediately prompted upon sign-up or sign-in.
Opt-in to Personal Accounts
If you'd still like Personal Accounts to exist alongside Organizations in for your application, thats still possible. Simply toggle "Enable Personal Account" at the moment you enable organization or in the Organization settings in the Clerk Dashboard.
Migration considerations
Due to the way this could change some of the way your application handles sessions, this functionality is only available for newly created applications. If you're running an existing application and want to adopt the new default, please contact our support team to discuss a migration strategy.
We recently shipped an updated growth chart in the Clerk Dashboard, giving better insight into your application’s growth—including detailed statuses like new, reactivated, retained, and even churned users.
Our latest upgrade goes a step further and now shows you exactly which users are part of those cohorts, enabling even more visibility into your application's growth and performance over time.
Note: The table of recent sign-ups has been replaced with user cohorts, providing a clearer and more detailed view of your users' activity.
Clerk is determined to become the best place for founders and builders to observe and understand their users. Head to the Overview section of the Clerk Dashboard to see it in action, and stay tuned for more.
Testing Tokens are now supported in production environments
Testing Tokens allow your automated tests to bypass Clerk's bot protections that might otherwise be triggered when interacting with Clerk-powered applications via automated browser agents. Previously, Testing Tokens were only for testing against Clerk development instances. With this update, Testing Tokens are now supported by Clerk production instances, allowing you to write tests against your production environment.
To make testing authenticated pages easier, the existing signIn test helper now allows authenticating a user directly by email address.
import { signIn } from'@clerk/testing/playwright'test('sign in',async ({ page }) => {awaitsignIn({ emailAddress:process.env.TEST_USER_EMAIL, page })// Navigate to a protected page for additional testingawaitpage.goto('/protected')})
To learn more about Testing Tokens, visit the documentation.
We're excited to announce that M2M tokens are now available in public beta, bringing secure authentication for communication between your backend services.
M2M tokens are designed specifically for authenticating requests between different machines within your backend infrastructure. Whether you're building microservices, background workers, or distributed systems, M2M tokens provide a secure way for your services to communicate with each other.
This is distinct from our other machine authentication offerings:
Create and configure machines directly from the Clerk Dashboard or via our API or SDKs. You have complete control over which machines can communicate with each other, allowing you to implement the principle of least privilege across your infrastructure.
Tokens can be customized with:
Custom claims to pass additional context between services
Configurable expiration times for enhanced security
Instant revocation when you need to immediately cut off access
Simple Integration
Creating and verifying M2M tokens is straightforward with our SDKs:
// Create a token on Machine Aconstm2mToken=awaitclerkClient.m2m.createToken()// Send authenticated request to Machine Bawaitfetch('<machine-b-url>', { headers: { Authorization:`Bearer ${m2mToken.token}`, },})// Verify the token on Machine Bconstverified=awaitclerkClient.m2m.verifyToken({ token })
Pricing
M2M tokens are free to use during the beta period. After general availability, they'll move to a simple usage-based pricing model. The pricing will be:
$0.001 per token creation
$0.0001 per token verification (for opaque tokens)
We'll provide usage stats, monitoring, and rate limiting in the Dashboard before the beta period ends, so you'll have complete visibility and control over your usage and costs. We're also planning to add support for JWT tokens before the beta period ends, which will only incur charges for creation, not verification.
Get Started Today
Ready to secure your backend service communication? Check out our resources to get started:
📖 M2M tokens guide - Complete walkthrough of creating machines and using tokens
💻 Example repository - See M2M tokens in action with two simple Express apps
We'd love to hear your feedback as you try out M2M tokens. Your input during the beta period will help us refine the feature and ensure it meets your needs. Have questions or suggestions? Reach out through our feedback portal or join the discussion in our Discord community.
