A Clerk alternative where the users live in your own Postgres
Clerk is an auth service with polished prebuilt sign-in components. You still need a database next to it, and a webhook or a JWT template to tell that database who the user is. Scribase puts auth and Postgres in one project: the user signs in, the token carries their id, and a row level security policy reads it with auth.uid(). No sync job, no second vendor, no per-user price. You do build the sign-in form yourself. This page says plainly which of the two fits.
Last checked November 16, 2026.
The short answer
- Pick Clerk when you want drop-in sign-in, sign-up and user-profile components and do not want to design those screens.
- Pick Scribase when you want sign-in, the user table and the application data in one Postgres project, enforced by row level security, at a price that does not grow with user count.
- Using Clerk with Neon or Supabase today and tired of keeping users in sync between them: Scribase removes the sync, because there is only one place the user exists.
Clerk and Scribase Auth, side by side
| Clerk | Scribase | |
|---|---|---|
| What it is | Auth and user management service | Postgres, Auth, Storage, Realtime and Functions in one project |
| Sign-in methods | Email, social, MFA and SSO, by plan | Email and password, magic link, OAuth providers, SAML 2.0, phone OTP |
| Prebuilt sign-in UI | Yes: sign-up, sign-in and user profile components | No. You render the form and call the client. |
| Where users live | In Clerk; you copy them to your database with webhooks if you need joins | In the auth schema of your own Postgres, next to your tables |
| Authorizing a query | Verify the Clerk token in your server, or configure it for your database | A signed JWT; policies read auth.uid() and auth.jwt() directly |
| Database included | No | Yes, Postgres 17 per project |
| Free tier | Hobby: up to 50,000 monthly retained users per app, fixed 7 day session lifetime | 1 project free with no time limit (0.5 GB database, 1 GB files, no card) |
| Paid | Pro: $20 a month billed annually; 50,000 retained users included per app, then $0.02 per user a month; extra SSO connections $75 a month each | Hobby $5 a project a month, Pro $25. No plan has a per-user price. |
Sources: Clerk: Pricing, Scribase docs: Auth, Scribase: Pricing
How sign-in reaches your data
Every Scribase environment has its own auth service on the /auth/v1 path. It speaks the protocol the supabase-js auth client already uses, so there is no new SDK to learn. The token it issues carries the user id; Postgres checks it on every row.
import { createClient } from '@supabase/supabase-js';
const db = createClient(process.env.NEXT_PUBLIC_SCRIBASE_URL!, process.env.NEXT_PUBLIC_SCRIBASE_ANON_KEY!);
await db.auth.signUp({ email, password });
await db.auth.signInWithOAuth({ provider: 'github' });
await db.auth.signInWithOtp({ email }); // magic linkalter table notes enable row level security;
create policy "owner reads own notes"
on notes for select
using (user_id = auth.uid());Sources: Scribase docs: Auth
What you do not get
- Prebuilt sign-in, sign-up and user-profile components. Clerk ships them; on Scribase you build the screens.
- A hosted organizations product with invitations and role screens. On Scribase, teams are tables you design, protected by row level security.
- More than one region. Scribase runs in one region today.
Moving an app from Clerk
Existing users: every user gets a new id in Scribase, so match old rows to new users by email. Social sign-in users sign in again with the same provider. Password users reset their password on first sign-in. Write to us before you start if you have many password users.
Step 1
Create the project
One command creates Postgres and Auth and writes the URL and anon key into your .env file.
sh npx scribase initStep 2
Turn on the providers you use
Email and password is always on. Add your Google or GitHub OAuth client id and secret in the project's auth settings.
Step 3
Replace the Clerk components with your own form
Call signUp, signInWithPassword, signInWithOAuth or signInWithOtp from the form. This is the real work of the move; budget for it.
Step 4
Point your tables at auth.uid()
Replace the Clerk user id column check in your server code with a row level security policy, then delete the user-sync webhook.
Questions people ask
Is there a Clerk alternative that includes the database?
Scribase is one. Each project is Postgres with built-in auth (email and password, magic link, OAuth, SAML, phone OTP), storage, realtime and functions. Users live in the same Postgres as your data, and row level security policies read the signed-in user with auth.uid().
Does Scribase have prebuilt sign-in components like Clerk?
No. Scribase Auth is an API used through the supabase-js auth client; you render the sign-in form yourself. If drop-in components are the reason you chose Clerk, Clerk is the better fit.
How is Scribase priced compared with Clerk?
Scribase charges per project, not per user: 1 project free with no time limit, then $5 a project a month on Hobby or $25 on Pro, with auth included. As of 2026-11-16, Clerk's free Hobby plan covers up to 50,000 monthly retained users per app, and Pro is $20 a month billed annually with $0.02 per additional retained user a month.
Can I replace Clerk plus Neon or Clerk plus Supabase with one service?
Yes for the database and auth: one Scribase project covers both behind one URL and one anon key, and there is no user sync because users are rows in the same Postgres. You do need to build your own sign-in screens.
Does Scribase Auth support SSO?
It supports SAML 2.0 and OAuth providers. There is no per-connection SSO fee on Scribase plans.