Typebase
1 comment
Typebase
Your backend is a folder of TypeScript files
#2 of the day · 8 Sep 2026
Typebase puts the database schema, the server actions and the auth rules in a typebase/ folder inside the app that uses them. The frontend calls them the way it calls a local function, typed end to end, with no REST layer written by hand in between. One command deploys the server behind it.
From the scout
Ben Cohen
I have written the same three files — the route, the client, the type that keeps them honest — for every project I have started in five years. Typebase deletes two of them. What convinced me is that it is a folder rather than a service. The schema, the actions and the auth sit in the repository next to the code that calls them, so a change is one commit and one review, and the types break at compile time when you get it wrong. I have not run it in anger yet. I would like to hear from somebody who has taken it past a toy app.
Read it and reply
I have written the same three files — the route, the client, the type that keeps them honest — for every project I have started in five years. Typebase deletes two of them.
What convinced me is that it is a folder rather than a service. The schema, the actions and the auth sit in the repository next to the code that calls them, so a change is one commit and one review, and the types break at compile time when you get it wrong. I have not run it in anger yet. I would like to hear from somebody who has taken it past a toy app.