Launching today
tinbase
Local Supabase without Docker one process, real Postgres
29 followers
Local Supabase without Docker one process, real Postgres
29 followers
A full Supabase-compatible backend shouldn't require a 12-container stack. tinbase serves the same APIs from one process: real Postgres 17 with RLS, Auth, Storage, and Realtime. Open source under MIT. supabase-js works unchanged, and the entire backend can run in a browser tab.
RapidNative
Hey Product Hunt! 👋
Sanket here, maker of tinbase.
tinbase started with an issue many of you will recognize: Supabase's local stack is a 12-container, 2.3 GB Docker install. All I wanted was to run my app locally. So we built the same APIs REST, Auth, Storage, Realtime, Edge Functions into a single 58 MB executable that boots in about 2 seconds.
npx tinbase start
A few things I'm proud of:
🐘 It's real Postgres 17 RLS policies, auth.uid(), jsonb, triggers, and foreign keys behave exactly like hosted Supabase
🔌 supabase-js works unchanged verified by running the official SDK against it: 168/168 integration tests pass
🌐 The whole backend runs in a browser tab every service is a pure fetch handler, so the database included runs in-process, no server. Try it at tinbase.dev/browser
🔁 Nothing is a dead end it reads supabase/migrations/*.sql exactly like the Supabase CLI. Outgrow tinbase? Push the same files to hosted Supabase.
📊 Studio included a table editor, SQL, auth, RLS policies, storage, and live logs at /_/
Honest note: we're in alpha (v0.11.1) built for local dev, prototypes, and embedded/browser use, not production yet. It's MIT-licensed and the repo is open: github.com/tinbase/tinbase
Fun origin story: tinbase came out of trying to run an entire dev stack database, auth, storage, realtime in the browser and on phones, with no VMs and no cloud behind it, for our other projects (lifo, RapidNative).
I'll be here all day what would you build if your whole backend fit in a browser tab? 🚀
@sanketsahu congrats on the launch!
when you say this is for running the app locally, does that mean not fit for production? Or how should I read this?
RapidNative
@quantumwhisker since this is early, I haven't battle-tested it for production (scale and security)! Although it could work well, I just don't want to claim until we have it on prod.
RapidNative
@quantumwhisker happy to help, just run npx tinbase start and see what happens.
ran tinbase in a browser tab and was surprised my existing supabase client code just worked without any changes. huge win for local dev.
RapidNative
@ceydaotman awesome!!
Interesting approach. Reducing the local setup from multiple containers to a single process could make onboarding much smoother. Curious to see how it performs on larger projects. Congrats on the launch!