Define your database schema, server actions, and auth in a typebase/ folder inside your app. One command deploys a fully typed server your frontend calls like local functions.
Ships with first-class guides for
Next.js·SvelteKit
·
Nuxt·Expo
Idiomatic clients for each one: Server Components, SvelteKit load functions, Nuxt plugins, Expo SecureStore.
How it works
Everything happens inside your codebase. The CLI handles codegen, schema pushes, and deployment.
One command creates a typebase/ folder in your existing app, with a database schema, example actions, and optional auth or realtime publishing. No separate repo, no dashboard.
$ npx typebase-io-cli initDefine tables in db/schema.ts, export actions from actions/, drop in auth.ts, env.ts, and publisher.ts for realtime. Every export is typechecked end to end.
Ships your folder as a server on Vercel, Cloudflare Workers, or Deno Deploy, with Postgres on Neon. Or generate the server code and host it anywhere. Typebase owns zero servers.
$ npx typebase-io-cli deployRLS is implicit and lives in a SQL dialect your editor doesn’t typecheck. One UPDATE policy gives write access to every column, including the ones you add tomorrow. The overly permissive clause an agent slipped in at 2am sails through review, because no compiler is going to flag it.
vs.
With Typebase, authorization is explicit. Your action declares the columns it accepts and your auth check runs in code before any of them reach the database. Add a column, the compiler tells you who can write to it. The same code your agent writes is the code your compiler checks.
Insecure policypolicy #2
auth.role() = 'authenticated' lets every signed-in user update every column of every row.
Typebase exists because we wanted both and couldn’t find it: backend functions that live in your code, backed by a database you actually own.
Storage isn’t there yet; it’s next on the roadmap. Read the full comparison
* None of these people exist. We checked. Twice. Legal is chill.
“I deleted 40,000 lines of REST plumbing last quarter. My tech lead cried. I think they were happy tears. I have stopped asking.”
MV
Mariel Vonnegut
Principal Eng, AI unicorn you’ve heard of
“Before Typebase I had three acronyms in my pipeline: REST, gRPC, and WHY. Now I have one: fn(). I have never been happier and my Oura ring agrees.”
DD
Dave Dave
Senior Fullstack, maybe
“I’ve told four separate therapists about Typebase. Two stopped taking me as a client. The other two are now shipping an app with it.”
CR
Clementine Ryu
Engineer, between therapists
“My co-founder asked where the auth lives. I said “a file called auth.ts.” He hasn’t spoken to me since. I assume he’s impressed.”
TL
Tomás Lindberg
Indie hacker, possibly single
“We replaced 14 microservices with one folder. The DevOps team threw me a party. The party was a meeting. The meeting was about layoffs.”
A
Anonymous
For obvious reasons
“10/10 would make my backend a folder again.”
HP
Hannah Pollard
Senior Folder Engineer, self-appointed
Do you have a real, non-fabricated quote? We will happily replace one of these humans with you.
It takes about ninety seconds. Most of that is npm install.
$ npm i typebase-io && npm i -D typebase-io-cli