Turso Cloud paid plans now start at $4.99/month - with 2.5x more reads than before: turso.tech/blog/turso-c...

Turso Cloud is now on AWS, fully backed by S3: turso.tech/blog/turso-a...

I hear you.

Syncing the sqlite file is indeed only an option for non-serverless. One option we are toying with is to just provide something you can deploy to Fly.io yourself that uses our sync under the hood to give you similar functionality.

We will not have the bandwidth to maintain two cloud providers with our renewed focus, as we need to simplify our operations.

a lot of users we talk to have AWS as a requirement, and want things like BYOC.

Gris (not on bsky) was one of the stars of our backend. He knows Go very well, and was the one-man-show behind all of our data pipelines, integrations with all of our 3rd party providers, and did a lot of work on the Turso CLI, Backend, and even our frontend.

If you know Rust, it doesn’t even feel to me necessary to talk about @luciofranco.bsky.social
A star of OSS development, he is behind packages like Tonic, Hyper, and Tokio. In the company, he was always eager to jump into any issues, take initiative to get things on track. Total A-player.

We also had to part ways with @giovannibenussi.bsky.social
. He is is a great with React and JS/TS, and combines that with a dependable attitude. Even before we even hired him - he was always on our Discord server, willing to help and to jump on issues unprompted and keep users happy.

We unfortunately had to let @ludden.social go. He is the best developer marketer I have worked with in my entire career. If you run a developer-centric company, I am sure you understand how hard it is to find a professional that understands the developer mind. Michael always makes it look easy.

Unfortunately, to be able to execute on our mission, we had to let some of our people go. They were all doing a fantastic work and I am personally committed in helping them find a new home. I'd like to use some of the responses to this post to say a couple of words about them.

Read more about the amazing serendipitous story of Limbo, and my reflections on it: turso.tech/blog/we-will...
Read more about changes to Turso Cloud to allow us to take this mission head on: turso.tech/blog/upcomin...

I wrote about why we are doing this, and what changes to current Turso users. tl;dr:
* we are removing edge replicas (now), and consolidating on AWS instead of fly.io (soon)
* We are removing multi-db schema changes and database attach (now)
* We are setting the Hobby plan to $5 a month (soon).

@anilmuppalla.com FWIW, we have some people in our discord reporting the same thing. It seem to be affecting databases on fly.io only.

yes, please.

send us your username and I'll take a look.

Are you able to otherwise access it, through the CLI or API ?

SQLite is the greatest database ever, and we always knew that with a strong and vibrant open contribution community, it could be 10x more. We heard the message loud and clear that the community doesn't want an incremental step. It wants a revolution.

We shall deliver.

5/5

And I will do just that. We are making changes to our roadmap and shifting priorities so we can get Limbo (which will be renamed) the attention it deserves. I will say more as the days come. 4/5

I am more excited now than I have been in years. I kept jokingly saying that if y'all wouldn't stop starring the damn project and opening mind-blowing PRs I would be forced to review our entire company strategy for this year and beyond. 3/5

After talking to a lot of you, it is clear why: our fork was directionally correct. We knew SQLite could be more, and we learned through the fork that we were right.

But the fork also lacked the blank canvas sense of freedom, to make deep changes and rally people behind. 2/5