We talk to customers every day at Clerk – it's our favorite part of the job. Recently, there has been a clear change in the feature requests we receive: instead of asking for more auth features, developers are asking for more integrations.
The first integrations we launched were with database tools like Supabase, Hasura, Fauna, and Firebase. This made sense, since like auth, choosing database tooling is one of the first decisions developers make.
Usage of our database integrations picked up right away. Today, over 20% of new Clerk instances turn on a database integration in their first two weeks of development.
The success of these integrations has also amplified requests for more. Now, the requests are for tools that are needed later in a company's lifecycle:
The writing is on the wall. In service of our customer requests, it's clear a robust suite of integrations will dominate our roadmap for the foreseeable future. Clerk is not just authentication anymore, we're a Customer Identity Platform: a complete Customer Identity solution that integrates and syncs with your favorite tools.
This week we celebrated crossing 250,000 users managed on Clerk! Onward and upward.
We've launched a new homepage to reflect our roadmap of integrations. For the first time, we're also featuring some of our customers.
Our journey to in-house documentation continues. We've moved another big batch of pages to clerk.dev/docs, where we have more control to build documentation that better serves developers.
This project will continue over the next several weeks, with updated designs and organizations coming soon.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。