← Retour au blog
tech 6 May 2026

From Supabase to Clerk to Better Auth: An Auth Journey

Explore why Val Town transitioned from Supabase to Clerk, and ultimately to Better Auth. A must-read experience for tech decision-makers.

Article inspired by the original source
From Supabase to Clerk to Better Auth ↗ blog.val.town

Introduction

In the ever-evolving tech landscape, choosing the right tools to build and secure applications is crucial. When it comes to user authentication, decisions can significantly impact a project's performance and scalability. Val Town, an innovative tech company, recently shared their migration journey from one authentication solution to another. From Supabase to Clerk, and finally to Better Auth, each step provided valuable learning experiences.

Why Supabase?

Supabase has gained popularity as an open-source alternative to Firebase. With a $100 million funding round and a $5 billion valuation, Supabase has become a major market player. Its appeal lies in its simplicity and integrated features, including authentication. However, for Val Town, integrating a conventional database presented more advantages tailored to their specific needs.

Transitioning to Clerk

In moving from Supabase to Clerk, Val Town aimed to leverage Clerk's advanced authentication features. With a $50 million funding and a growing user base, Clerk seemed like a promising choice. However, issues with rate limits and architectural incompatibility posed challenges. For instance, Clerk’s role as both the users and sessions table created unexpected hurdles.

Challenges with Clerk

Clerk proposed to centralize user data, but this proved problematic for Val Town. A concrete example is Clerk's API rate limit of five requests per second, which hindered the smooth functioning of Val Town's social features. This particularly affected pages displaying user content, where multiple API calls were needed.

Why Better Auth?

Ultimately, seeking more flexibility and reliability, Val Town opted for Better Auth. This solution overcame previous limitations with an architecture better suited to the company's specific needs. Better Auth offered increased customization and better integration with existing systems.

Conclusion

Val Town's journey illustrates the importance of choosing the right authentication solution to meet specific and evolving needs. Each step in their migration provided valuable lessons on evaluating trade-offs between simplicity, flexibility, and scalability.

Let's discuss your project in 15 minutes.

authentification Supabase Clerk Better Auth migration
Deepthix newsletter · 100% AI · every Monday 8am

An AI agent reads tech for you.

Our AI agent scans ~200 sources per week and ships the best articles to your inbox Monday 8am. Free. One click to unsubscribe.

Visit the newsletter page →

Want to automate your operations?

Let's talk about your project in 15 minutes.

Book a call