pretty opinionated in a useful way. if you already like typescript, postgres, and keeping backend rules in code instead of dashboards, this makes a strong case. if you want less convention, the one folder magic may feel a bit bossy.
Typebase
Make your backend a folder with TypeScript.
6 ratings4.17
Saves119
CategoryDeveloper Tools
PlatformWeb
PricingFree
Typebase is a developer tool that lets you add a backend to your existing app by writing your database schema, server functions, and authentication all in TypeScript within a single folder. It integrates your database and backend logic with your frontend via type-safe calls, simplifying development and deployment without managing separate backend services or dashboards.
open-source
Ratings & Reviews
Write a reviewInformation
CategoryDeveloper Tools
PlatformsWeb
PricingFree
AccountSign-in detected
ListedAugust 2026
WebVisit
Report a problem
Website checks
Mobile PageSpeed
Automated checks of the public website by Google Lighthouse 13.5.0. Scores can vary between runs.
Checked Oct 25, 2026
Test this website on PageSpeedWebsite checks refresh automatically each week.
- Performance
- 85 out of 100, Needs improvement
- Accessibility
- 100 out of 100, Good
- Best Practices
- 100 out of 100, Good
- SEO
- 100 out of 100, Good
Around the Web
Show HN119 source points · 49 comments
Very cool! Note that you can run Convex on top of your own Postgres, and we do this for our internal apps, with very nice performance (plenty for our internal use cases).
xixixao · Imported from Show HN
I’ve been curious about trying the Supabase type of RLS model for an app but haven’t yet. I like the idea of the db defined api like postgraphile and hasura but had trouble with testing and ergonomics. This looks pretty nice though, it’s cool that you’re thinking about ergonomics for working with coding agents. I feel like a hard thing with that rn is that everyone is kind of figuring out different workflows for AI coding right now so it’s hard to optimize DX. Can you talk a little about your personal agent workflow and how this fits it?
rgbrgb · Imported from Show HN
very cool. though the deploy wasnt clear if i can just run migration on some pg url. and it wasnt clear if i can bind some middleware into my existing app server (like express)
bosky101 · Imported from Show HN
This looks great. Question specifically on the Cloudflare Workers target: when you deploy there, does Typebase use D1 for the DB, or does the Postgres/Neon backend stay the same regardless of which server target you pick (Vercel/Workers/Deno) - i.e. is the DB layer decoupled from the server runtime, or does choosing Workers also mean choosing D1? I ask because I've shipped a small Workers+D1 service and the main friction I've hit isn't the server code, it's Workers' constraints around D1 (no long-running connections, HTTP-based driver quirks) - curious whether Typebase abstracts that away or whether you still feel it at the DB layer when targeting Workers specifically.
SifatAhmed · Imported from Show HN
Fake reviews are a hard no-no imo. Really weird addition, but I suppose it wasn't you who got the idea. Looks an awful lot like a orpc, just built on top of drizzle instead of raw queries. I'm sure some people want this, but it seems like gross duct tape that will bite you in three years
ramon156 · Imported from Show HN