# Why We Transitioned to Clerk for Authentication

DevFeed: [Why We Transitioned to Clerk for Authentication](<https://devfeed.tech/articles/why-we-transitioned-to-clerk-for-authentication-6120.md>)

Original publisher: [Read original article](<https://turso.tech/blog/why-we-transitioned-to-clerk-for-authentication>)

Author: João Gris

Published: 2024-08-15T00:00:00Z

Content type: article

Language: en

Sources: [Turso Blog](<https://devfeed.tech/sources/turso-blog.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Passkeys](<https://devfeed.tech/topics/passkeys.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Turso](<https://devfeed.tech/topics/turso.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [development](<https://devfeed.tech/tags/development.md>), [mfa](<https://devfeed.tech/tags/mfa.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [security](<https://devfeed.tech/tags/security.md>), [speed](<https://devfeed.tech/tags/speed.md>), [sso](<https://devfeed.tech/tags/sso.md>), [turso](<https://devfeed.tech/tags/turso.md>)

## AI overview

Turso explains why it moved from a self-built GitHub authentication system to Clerk. The transition addressed growing needs such as MFA, SSO, additional authentication methods, account management, and support for CLI tokens.

## Source excerpt

Learn about how and why we transitioned to Clerk from our own auth system for Turso.