Clerk Changelog

Securing your user base even more just got a lot easier. You can now require multi-factor authentication (MFA) across your entire application with a single toggle.

This ensures that every user, whether they are signing up for the first time or returning to an existing account, adds a critical layer of protection before they can access your application.

What's new

The require multi-factor authentication (MFA) setting eliminates the "opt-in" gap. Previously, users had to manually choose to secure their accounts. Now you can make it a requirement for entry.

If a user signs-in or signs-up without multi-factor authentication (MFA) enabled, they’ll be guided through the setup flow before proceeding.

This works seamlessly with Clerk’s prebuilt components. Users can choose from the available application MFA methods, including Authenticator application (TOTP) and SMS verification code.

Getting started

To require multi-factor authentication (MFA) across your application:

1. Ensure your Clerk SDKs meet the minimum required versions. Refer to the setup-mfa session task guide⁠ for version requirements.
2. Navigate to Multi-factor⁠ in the Clerk Dashboard
3. Enable one or more MFA strategies (Authenticator application or SMS verification code).
4. Turn on Require multi-factor authentication

Once enabled, new users will be prompted to set up MFA during sign-up, and existing users without MFA will be prompted the next time they sign-in.

To learn more, visit the setup MFA guide⁠.

• Proactive alerts are now available. A warning icon and banner appear when Stripe reports outstanding account requirements.

• Issues can be resolved directly from the Dashboard. Clicking the warning banner opens Stripe so you can complete required items.

• Warnings are visible in key billing areas. They appear in the Billing tab and in Billing settings under the Configure section.

• Early resolution helps prevent payment interruptions for Clerk Billing.

Communicating your growth is crucial for building confidence in your product.

That's why we've added export capabilities to every chart in the Clerk dashboard, making it easier than ever to share insights with your team, stakeholders, or potential customers.

• Export any chart from your dashboard as a high-quality PNG image
• Copy charts directly to your clipboard for quick sharing
• Export any chart type: line charts, bar charts, and more

You can also customize the way your charts look when exported:

1. Set the desired date range and interval in your Clerk dashboard, including whether to show the incomplete period or not
2. Click the share button on any report to view a preview of the export
3. Toggle the y-axis display, show or hide growth rate total, include or exclude churned user data and more
4. All exports maintain your dashboard's light or dark mode theme and application branding

Clerk's iOS and Android SDKs are now at v1, focused on a better developer experience and a simplified API across both platforms. The biggest change is a unified entry point: all auth methods now live under .auth in each SDK, so everything related to authentication is in one place — with simpler, easier-to-use APIs throughout.

If you're upgrading from v0, follow the migration guides: iOS v1 migration guide and Android v1 migration guide.

What's new in iOS

Some highlights:

• Unified auth entry point: All auth flows live under clerk.auth, so sign-in, sign-up, and sign-out share one consistent surface.

  Swift

  SwiftUI

  var signIn = try await Clerk.shared.auth.signInWithEmailCode(
    emailAddress: "newuser@clerk.com"
  )

  struct ContentView: View {
    @Environment(Clerk.self) private var clerk
  
    var body: some View {
      Button("Send code") {
        Task {
          await sendEmailCode()
        }
      }
    }
  
    private func sendEmailCode() async {
      do {
        var signIn = try await clerk.auth.signInWithEmailCode(
          emailAddress: "newuser@clerk.com"
        )
      } catch {
        // Handle error
      }
    }
  }

• Import only what you need: v1 splits the iOS SDK into ClerkKit (core APIs) and ClerkKitUI (prebuilt views), so you only import what you use.

  import ClerkKit
  import ClerkKitUI

• Simpler, more flexible configuration: Configure Clerk once at launch with Clerk.configure(...).

  Clerk.configure(publishableKey: "YOUR_PUBLISHABLE_KEY")

• More modern SwiftUI wiring: Inject Clerk.shared directly into the environment instead of the old custom key, and read it with @Environment(Clerk.self).

  ContentView()
    .environment(Clerk.shared)

  @Environment(Clerk.self) private var clerk

Check out the iOS docs for full details.

What's new in Android

Some highlights:

• Unified auth entry point: All auth flows live under Clerk.auth, so sign-in, sign-up, and sign-out stay in one place.

  Kotlin

  Compose

  val signIn = Clerk.auth.signInWithOtp {
    email = "newuser@clerk.com"
  }

  @Composable
  fun SignInView() {
    val scope = rememberCoroutineScope()
  
    Button(onClick = {
      scope.launch {
        sendEmailCode()
      }
    }) {
      Text("Send code")
    }
  }
  
  private suspend fun sendEmailCode() {
    Clerk.auth.signInWithOtp { email = "newuser@clerk.com" }
      .onSuccess { signIn ->
        // Continue the flow
      }
      .onFailure { error ->
        // Handle error
      }
  }

• Clearer auth state naming: signIn and signUp state are now currentSignIn and currentSignUp to avoid method-name confusion.

• Builder pattern for auth methods: Auth flows adopt builders for cleaner call sites and more explicit parameter grouping, including MFA steps.

Check out the Android docs for full details.

Get started

v1 makes it easier to build consistent native experiences across iOS and Android. Follow the platform quickstarts to get set up: iOS quickstart and Android quickstart. If you're upgrading, use the migration guides above to update imports, config, and auth flow calls.

Need help? Reach us on Clerk Discord⁠ or explore the source on GitHub: clerk-ios⁠ and clerk-android⁠.

Today, we're excited to share our first major pricing update since November 2023. As our products have evolved over the years, we've heard that our pricing no longer felt quite right. This update reflects the feedback, frustrations, and suggestions we've heard from many of you.

Our goal is simple: make authentication essentials more affordable, while focusing our fees on differentiated features and areas with real operational cost.

Let's dive into some specifics.

The vast majority of customers will pay less, or receive more features for the same price

We're improving affordability across nearly every dimension, so both our smallest and largest customers are set to benefit:

• 50,000 Monthly Retained Users are now free in every application, up from 10,000
• Unlimited applications are now included in every plan, eliminating the need to upgrade each application individually
• The Enhanced Authentication Add-on has been eliminated, and most of its features are now included in our Pro Plan (starting from $20/mo). This includes:
  • Multi-factor authentication
  • Satellite domains
  • Simultaneous sessions
• 5 impersonations per month are now free, to allow trying the feature before purchasing the Enhanced Administration Add-on
• Automatic volume discounts will now be applied as usage grows
• Annual billing is now available for an additional discount

Alongside these changes, we've also reduced the complexity of our plans to ensure you're never surprised by which features are included or omitted.

Some customers will see price increases

We're making three changes that will increase costs for a minority of our customers. Those changes are:

1. Using four or more Clerk Dashboard seats now requires a Business Plan (starting from $250/mo).

   We love building a dashboard that goes beyond authentication and helps teams operate and scale their business. This change will allow us to continue improving the dashboard for more teammates in more roles.

2. Enterprise Connections (SAML and OIDC) are now metered within the Pro Plan, instead of unlimited under the former Enhanced Authentication Add-on.

   Under the new pricing, applications with three or more Enterprise Connections will see increased costs. These costs will support continued investment in Enterprise Connections, including our upcoming support for SCIM and self-serve configuration.

3. Access to SOC 2 and HIPAA artifacts now requires a Business Plan.

   We gate access to audit artifacts because they involve ongoing third-party audits and real operational overhead. Importantly, the underlying security controls are the same for all customers, regardless of plan.

Rollout

Our new plans are available starting today, and the full details are available on our pricing page⁠. We encourage customers to switch as soon as possible.

If paid customers do not select a new plan before their billing period beginning in April, Clerk will automatically migrate them to a new plan. We hope to avoid automatic migrations, though, and will be sending multiple reminders before they occur.

If you have any questions or concerns, or if your business requires a custom plan, please don't hesitate to contact us⁠.

Thank you

We love making our pricing even more competitive, and it's only possible because tens of thousands of customers like you have entrusted Clerk as their authentication provider.

We look forward to the years ahead as we'll continue to innovate not just on authentication, but all of customer management.

See how many days a user logs in to your app over the course of a year to get an at-a-glance visualization of their activity within your product.

• Spot engagement patterns - See which users are active daily versus those who haven't returned in weeks.
• Navigate by year - Use the year selector to view activity from any year since the user was created.
• Hover for details - Tooltips on each day show the exact date and whether the user was active.

To view the activity graph, open any user's profile page from the Users⁠ list in your Clerk Dashboard.

Keep an eye out for continued improvements and higher data fidelity in this report.