Turso Now Includes Unlimited Active Databases for Everybody

Turso already includes unlimited databases in every paid plan. But there was a catch: we had a limit on how many could be active at once. Now, that limit is gone.

As of today, every paid user gets unlimited databases, and you can use as many as you want, whenever you want.

The reason we are doing this is simple: you asked for it. And we heard you.

#Why we had a limit in the first place

When we launched Turso Cloud, we offered 5,000 databases per account. That was the highest in the market at the time. We were proud of that number. But we weren't satisfied with stopping there.

Our mission has always been simple: remove every reason you'd hesitate before creating a database. Want to isolate each tenant in a SaaS app? Create a database. Need session state for an AI agent? Create a database. Building an app where users spin up their own environment? Create a database.

We got closer to this vision by offering unlimited databases, but we still had infrastructure costs that scaled with the number of active databases (databases that had at least one query in a given billing cycle). We added that metric to pricing and people started asking the question we never wanted them to ask: "should I add a database here?"

Unacceptable. We couldn't live with ourselves!

#The problem is real

Here's what we kept hearing: "Some of my users barely touch their databases each month, just enough to keep them active. The cost of the database starts being prohibitive as we scale."

This hit us hard. We were solving only half the problem. You could create millions of databases, but if you had low-usage tenants, you'd start doing mental math about whether it was worth giving each one their own database.

That's exactly the kind of friction we want to eliminate.

#So what changed

Over the past year, most of our engineering effort went into rewriting SQLite from scratch in Rust. We added concurrent writes through MVCC. We built a powerful sync engine. We implemented native Change Data Capture, vector search, stronger types, and more.

As we got closer to GA for the Turso Database, we finally had the resources to tackle the active database limit. We rebuilt parts of our infrastructure to handle the unlimited database world we've been building toward.

Now that work is done, and we're passing the improvements on to you.

#What this means for you

If you've been building with Turso, some of these use cases probably resonate with you:

Per agent session data: Spin up a database for each AI agent session. No shared state, no conflicts, complete isolation.
App-builder platforms: Let users create their own isolated environments without worrying about database costs piling up.
Per-user data in regulated industries: Store per-user data in separate databases for compliance and security, even if most users are low-activity.
Mobile and offline first applications: Create local databases that sync when needed, not on a schedule dictated by billing.

The pattern is the same: create databases freely, use them when you need them, and don't think about the cost of dormant databases.

#I want databases!

If you've ever caught yourself thinking: "what if I would create a database every time that…", stop asking "what if…".

And if you feel like SQLite might limit you, unlimited Turso databases in the Cloud is now in private beta. You can fill the form here to join the waiting list.

We're building database infrastructure for the agentic age. This is one more step toward making databases as easy to create as variables in your code.