Clerk Changelog

Happy 2022! We have an incredible year planned and can't wait to share the updates, right here in our changelog, every Friday.

Supabase integration

We're starting this year off with a bang. Over the holidays, our cofounder Braden put together the first version of our Supabase⁠ integration.

We're excited about this integration for several reasons:

1. Supabase was our most requested integration in the fourth quarter of 2021, and we're excited to finally unlock the capability.
2. We love the integration pathway that Supabase provides, and it's generated plans for the weeks ahead that will make this integration even better.
3. Empowering frontend developers is a core part of our thesis at Clerk. Just like Clerk empowers frontend developers with authentication capabilities, Supabase empowers frontend developers with database capabilities. It's a huge productivity increase for engineering teams, which no longer need to waste engineering cycles building CRUD endpoints for frontend developers to consume - now frontend developers can safely query the database directly.

Try out our beta Supabase integration today.

New Security informational page

As an authentication company, security must be our topmost priority - it's the only priority we place higher than developer experience. Security has been in our DNA from day one, with our founding engineers having significant web security expertise.

Admittedly, we haven't shared enough about our security efforts externally. For example, did you know we conduct regular, third-party security audits?

This week, we launched a new informational page that shares more about our security practices at Clerk.

Community spotlight: Firebase + Clerk recipe app by James Perkins

James Perkins⁠ launched a new video and written tutorial this week showing how to use Clerk and Firebase to create a recipe app⁠.

You might recognize James from our own website - we are big fans of his teaching style and have contracted with him to produce our own demos. It was a pleasant surprise to see this on his own channel this week, and we recommend you check it out!

Happy holidays everyone, and welcome to our very merry changelog!

Before stepping away for the holidays, we finished up a ton of new features to help your holiday side projects and beyond.

Although much of our team is off celebrating next week, we're still closely monitoring our uptime metrics and support channels - please drop us a line if there's anything we can help with.

Custom JWT templates for third-party authentication

JWTs have become the standard for syncing sessions between third-parties.

JWTs have always been the secret behind our integration with Hasura. When a user has an authenticated session with Clerk, we enable you to generate a special JWT for authentication with Hasura.

Now we've expanded on that concept, so you can generate custom JWTs to integrate with any vendor that supports them. Read more about generating custom JWTs in our documentation.

Improved security for magic links

Magic link emails now include the device type for extra security (e.g. "Chrome, OS X"). This extra information is to help ensure that users don't click the magic link if it was requested by someone else.

Easier onboarding

We've added a quickstart to our onboarding, so you can choose your desired configuration faster.

Easier productionizing

Moving Clerk to production requires you to configure some DNS settings. We've improved our dashboard to better guide you through the process.

New homepage

We've launched a new homepage to reinforce our commitment to the Modern Web and frameworks like Next.js, Gatsby, and Expo.

As we begin the holiday season, we're happy to be releasing some of our biggest projects of the quarter. Today's launch is in response to dozens of customer requests for greater customization capabilities.

Customizable email and SMS templates

You can now customize the email and SMS communications sent as part of sign-up and sign-in. Try it from the Customization tab of your dashboard today!

This feature allows you to ensure that the styling and tone of communications is perfectly in-line with your brand. Plus, the email editor can be used in both HTML and WYSIWYG modes, to provide a seamless editing experience regardless of your preference.

Customization capabilities remain a core focus at Clerk and many more are on the roadmap. We're eager to continue making improvements throughout 2022. Have a request? Drop us a line.

Dashboard launch!

Our new dashboard is officially out of beta!

Many thanks to our customers who participated in the beta and helped us iron out the last few wrinkles. Besides the updated design, we're thrilled with our new technology stack that will enable even faster innovation.

<SignInButton> and <SignUpButton> utilities

Our React and Next.js SDKs now expose <SignUpButton> and <SignInButton> utilities. They can be used to link to the sign-in and sign-up pages, or to open the sign-in and sign-up modals.

Check out our <SignInButton> documentation and our <SignUpButton> documentation.

Hopefully everyone is well-rested after all the turkey, traveling, and family this past week/end! We took a few days to recover, but we're still going strong with our mission to build the best authentication platform out there.

React Native, including Expo support

Building a mobile app? Consider Expo and React Native. Clerk + Expo is officially the easiest way to build authentication across modern Web stacks, and now Mobile apps.

Mobile applications are a big part of the world now a days, and 2022 will see even more support for Swift, Kotlin, etc.

Invitations, plus Allowlist upgrades

Big feature realease! You can now easily invite users to your application. Although seemingly small, this feature unlocks a lot of new capabilities, and is the start of our B2B feature set ;)

As part of this release, we've also made some improvements to Clerk's allowlist. You can now include regex in the list, to make it easy to onboard entire domains.

Community Highlight

Shoutout to Scott and his great application https://www.phonetoroam.com⁠, for putting this blog post together about his experience migrating Phone To Roam to Clerk, we couldn't have said it better ourselves...

And this choice quotes that stood out: "Got it thanks! Was able successfully get signup and login working, much easier than auth0 :)"

Dashboard improvements... but still in beta

A lot of folks have had a chance to play with our new dashboard, and they've helpfully uncovered some bugs and minor issues. However, we also received an overwhelming amount of positive feedback on the design and clarity! Poised to go GA sometime next week.

---

until next time space cowboy...

Happy American Thanksgiving! While our US team was off the later half of this week, our global team continued to push out some excellent improvements to Clerk.

Rolling sessions

We now have two session lifetime settings: Inactivity timeout and Maximum lifetime. You can configure your application to use either one, or both.

Inactivity timeout sets how long a user can be inactive before they are logged out, which enables you to set a "rolling" lifetime as long as the user remains active.

Maximum lifetime sets how long a session can last, regardless of activity.

New dashboard beta

We've launched the beta of our new dashboard at dashboard.clerk.com⁠.

During the redesign we put a strong emphasis on organization. Some developers were having a hard time finding the appropriate settings pages in our original dashboard, and we've worked to address those challenges in this update.

Also, our new architecture allows for more rapid development going forward, enabling us to bring new features even faster.

We're still updating screenshots in our documentation to reflect the new dashboard, but we expect to transition completely in the coming weeks.

Rename Return-Path CNAME

To deploy Clerk in production, you must set a few CNAMEs in your DNS that allow us to deliver emails with both SPF and DKIM verification. One of those CNAMEs is for the Return-Path header in the emails.

Previously, the default CNAME was for mail.yourdomain.com, which understandably hit a few collisions. Going forward, the default CNAME is clkmail.yourdomain.com. This is not a user-facing change, it just makes Clerk less likely to conflict with other services you might be using.

Existing production applications still work with mail.yourdomain.com, but please contact support if you'd like to migrate to a different subdomain.