Authentication for Astro: what 12 makers' products chose
Among 12 makers' products built with Astro that we know the authentication of, Clerk leads: 8 of them (67%). Next come Supabase (1) and Better Auth (1).
Hosted service or library in your own app. Hosted services give you UI, MFA and security updates for a monthly bill and some lock-in; libraries keep users in your own database for free, and you own the upkeep.
What makers on Astro chose
| Option | Astro products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 8 (67%) | 80% | ~50,000 users | $0/moHobby | |
| 1 (8%) | 3% | ~50,000 users | $0/moFree | |
| 1 (8%) | 2% | Any size | $0/moSelf-hosted (open source) | |
| 1 (8%) | 5% | ~1,000,000 users | $0/moAuthKit | |
| 1 (8%) | 0% | ~5,000 users | — |
Live makers' products with a source for both: that they're built with Astro, and what they use for authentication. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You're on Next.js or React and want sign-in, profiles and teams working today
Clerk 8 here - Your data is already in Supabase or Firebase
Supabase 1 here - You want users in your own database and no per-user bill
Better Auth 1 here - You sell to companies whose IT team will ask for SAML SSO or SCIM
WorkOS 1 here
Clerk
Hosted service8 Astro products here (67%). Free up to about 50,000 users. About $0 a month at 10,000 users (Hobby).
llms.txtMCPCLIIn ReplitBest forDropping prebuilt sign-in, profile and organization UI into a React or Next.js app.
Trade-offPer-user pricing grows with you; users live in Clerk, not your database.
“Clerk helps manage sign ups & secure authentication.”
- Sign-up, sign-in, sessions and social login get wired in an afternoon instead of a sprint. 2 sources
- Organizations, roles and billing come built in, covering multi-tenant B2B apps without custom identity work. 2 sources
- Outsourcing auth means a Clerk outage or account problem locks your users out, and the dependency is hard to reverse. 4 sources
- Costs climb with SSO, MFA, passkeys and branding removal, and some switched to cheaper open-source options. 4 sources
Which frameworks and languages does Clerk support? Clerk maintains SDKs for Next.js, React, Expo, Astro, Nuxt, Vue, React Router, TanStack Start, Chrome extensions, Electron, iOS and Android, plus backend SDKs for Express, Fastify, Go, Python, Ruby on Rails, Java, PHP and C#. SvelteKit, Angular, Hono and Flutter are covered by community-maintained SDKs. Clerk docs ↗
Status page: 9 incidents in the last 90 days (its own page, 2026-10-19).
“Clerk helps manage sign ups & secure authentication.”
AuthenticationMaker says so +1 · source ↗“Auth that took an afternoon to wire up instead of a sprint. EmailTemple's free tier means thousands of signups need to just work — Clerk handles the whole sign-up / sign-in / webhook flow, and the server-side auth() API plays clean with Next.js App Router. Worth it for the time alone.”
AuthenticationMaker says so +1 · source ↗Also chosen, and not seen yet
Fewer Astro products here: Supabase (1), Better Auth (1), WorkOS (1), SuperTokens (1).
Real options for authentication not seen among these Astro products yet: Firebase, Auth0.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Astro.
- Supabase → Clerk 54 pull requests · how they moved
- Clerk → Supabase 53 pull requests · how they moved
- Clerk → Better Auth 33 pull requests · how they moved
- Supabase → Better Auth 19 pull requests
- Clerk → WorkOS 6 pull requests
- Better Auth → Supabase 5 pull requests
Getting authentication right
Start with email + one social login (Google or GitHub). Keep the user record in your own database even when a hosted service owns sign-in, so you can switch later. Add organizations and SSO only when a paying customer asks.
- Keeping users only inside the auth provider — with no row in your own database, every query that joins users goes through their API, and moving later means a password-reset email to everyone.
- Building organizations, roles and SSO before a paying customer asks for them.
- Comparing only free tiers; per-monthly-active-user pricing is what you pay once a free product gets traffic.
The rest of the Astro stack
What makers' Astro products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 49 of 112
- Transactional Email: Resend 44 of 84
- Web Analytics: Cloudflare Web Analytics 18 of 47
- Payments: Stripe 22 of 34
- Database: Supabase 7 of 27
- LLM API: OpenAI API 17 of 27
- Product Analytics: PostHog 13 of 14
- Speech-to-Text & Text-to-Speech: ElevenLabs 7 of 12
Questions
What do most Astro apps use for authentication?
Among 12 makers' products built with Astro that we know the authentication of, Clerk leads: 8 of them (67%). Next come Supabase (1) and Better Auth (1).
What does authentication cost for an Astro app with 10,000 users?
On our usage model at 10,000 users, Clerk (Hobby), Supabase (Free), Better Auth (Self-hosted (open source)), WorkOS (AuthKit) all still cost nothing a month. Prices are from each vendor's pricing page.
Which authentication option stays free longest for an Astro app?
Better Auth: on our usage model it stays free even at 10 million users.
How this is counted: a product is on Astro when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its authentication. How evidence is collected.