Sorry to hear about that. That’s definitely not the norm, especially if this wasn’t on the free tier. We expect very low latency, but if it is a local isolated problem with a small group of servers our status page won't pick up. Though hard to say much more without the specifics.

Rob told me you were at Supabase now and I am STOKED to work together again, Paul!

same!!

I certainly am! A large part of the reason this happened is that I sat down with Paul, and he shared his vision with me for what he wanted to do with Turso and how that would fit the supabase story. Very exciting!

it's funny, because money is the number 1,000 or even lower thing on my priorities.

Turso has a booming OSS community with many contributors from outside the company and is fully MIT.

What you believe versus what outcomes your decisions actually lead to are two totally different things.

I hear you Josh, and I don't blame you because this does happen a lot. All I can say is that everyone is excited about this, on both sides of the aisle. From our perspective we'll have resources now to turbocharge the development of Turso, and things will only get better from here.

I wish you the best of luck in beating the odds and actually continuing to operate effectively post-acquisition for as long as possible. Turso is great, and I'm looking forward to the point where it feels like it crosses from "keep a close eye on" to "use in production with no qualms".

I shaved my head first, though.

Jarred is a copycat on that front.

We started turso way before vibe coding became a thing, king. And these days we use AI, like most people, but still review all the code ourselves before it goes in.

Very disingenuous to call turso a vibe coded project.

Write me a message to my email directly or hit me up on Discord.

We are very excited to be a part of Supabase

our cloud pays the bill just fine though.

Turso CEO here. We were doing fine.

This is a strategic acquisition and I fell in love with the vision Supabase had for how they would use Turso going forward.

More to come

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.

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.

Thanks again, I have hope.

SQLite/Turso fits my own agent/harness mental model very well but I am, as folks in the valley would say, a bit of an anti-capitalist.

I am working on my own agents that are anti-tokenmaxxers. SQLite/Turso is part of the deployed app architecture from my harness. Thanks a lot for taking the time.

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.

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.

Or Supabase starts offering "SQLite" (Turso) as they are offering PG today?

yup — we see Turso/SQLite as complementary to Postgres for specific use cases. The blog post doesn't mention it yet, but this will power our smallest instance — "Spark" https://x.com/saltcod/status/2106078176464036044