← Back to context

Comment by brainless

8 hours ago

Thanks but you do understand this makes it hard for folks to select Turso. With all good intentions parent companies kill acquisitions.

Supabase is hosted Postgres with wings. Turso seemed like it would be the same but using SQLite based approach.

So either Supabase now uses the Turso sync + Postgres or something that needs Turso or abandons it. Not sure and I am not asking, just sharing my thoughts.

Love what you folks have been doing.

5 comments

brainless

Reply
glommer  27 minutes ago

No, I truly don't understand that. It is true that some acquisitions fail, but most of the ones you see failing are doomed from the start and are a way for the founder to exit, acquhire, etc.

I had a never-ending host of options at my hand. Turso grew revenue > 5x this year. I had no reason to accept an offer that wouldn't have a great chance of success.

threatofrain  7 hours ago

I also have my own doubts about this acquisition, but as I explore sqlite-per-user models I'm also seeing benefits to having some central control plane. I thought they would've made a natural fit on Cloudflare.

christoff12  7 hours ago

Did you check out the post? Supabase sees Turso as the answer to workloads not well-suited for Postgres. This seems like a decent Yes, And proposition.