Loading video...
Video Failed to Load
Introducing (open-source) A Supabase-compatible backend in a single binary - real Postgres with RLS, no docker (with ~36mb install footprint)! It's like PocketBase, but with Postgres instead of SQLite!
46,008 views • 3 months ago •via X (Twitter)
43 Comments

A quick comparison of install footprint and memory under load, the full benchmark is available as open-source! The benchmark was run on macOS 15 on Apple Silicon with 48GB RAM.

Got a little studio UI as well with table editor, SQL editor, auth, RLS, Database, Storage, Email UI for OTPs as well.

And it works inside browsers too, in case you need it for a dev env in your browser! Go ahead and try to run your projects locally using `npx tinbase start`. Bugs are expected, happy to fix them! Cheers! 🍻

neat project, here i a visualization of it

what a lovely visualization!

you serious?

honestly, thinking of a Rust version too, to reduce the footprint

We need extensions like pgcron etc to be full compatibility

This sounds amazing @sanketsahu

Very cool :D

Sounds amazing! Love PocketBase for simple projects

You might use this one beyond simple projects :)

Glad you didn't post a link so nobody accidentally installs it 👍

Do have the link lol

Man, this is exciting!!

This is really slick. Congrats on the launch! 🚀

Thanks 🙌

This is really cool

that is so cool, nice job !!!

Nice!

This is great Sanket. Will check it out right away

Thanks broo

Supabase is quite heavy. This is interesting

One question: In pocketbase you have the option to extend it with js (with some limitations) or with Go (no limitations). With tinbase I guess you can use JS to extend it as you would for a normal app (install npm packages etc)?

So, you have supabase functions (js) that you can use, it works the same with tinbase!

>no docker wouldn't hurt to have one tbh. please?

i had to run 100 instances on one server, it was very difficult

>it was very difficult with docker? why?

memory and disk usage on macOS is over 1.5gbs

>memory and disk usage on macOS is over 1.5gbs for a 100 instances? that's cheap

For 1 instance

>For 1 instance ok that's obviously way more than the raw package but it'll still find it's use, single image supabase package is a 100% easy win. how do you create/update/run edge functions there though? or you don't?

I'm not sure if I understand your question well but edge functions are read from the Supabase/function foldse from fs. correct? the cli picks it up, right? I haven't stress tested booting multiple Supabase instances, tested on Mac only which bloats it because of docker vms I assume

Bro WTH!! Really amazing. Gonna try now.

I like the idea but can you please atleast take the time to polish your page a tiny bit before launching this.

I'll fix it as soon as I can

@niclas__4 If one is not embarassed after launching, they are not going fast enough 😂 Very useful tool btw..

@niclas__4 haha, why not

@webiyo @niclas__4 Can i help with this?

@cryptopeterg0x @webiyo @niclas__4 help with? this was fixed yesterday!

If this helps to run multiple agents on my machine with each their own supabase (impossible right now..), then this is huge!

interesting use-case, let me know how it goes. also, I am extending pg-mem to be more complete, it would be much faster to choose pg-mem over full postgres for this use-case

single binary with real Postgres instead of SQLite is the right call for anything that outlives a demo. SQLite backed tools are great until someone needs concurrent writes in production and finds out the hard way.
