What is Turso?
Turso is a database platform built on libSQL — an open-source fork of SQLite. It takes SQLite, the world's most widely deployed database (it runs in every iPhone, Android device, and web browser), and makes it network-accessible with built-in edge replication.
The result is a database that is dead simple to reason about (it is just SQLite), available via HTTP from any runtime (including edge functions), and capable of serving reads from servers physically close to your users worldwide — meaning faster response times without any extra effort.
Why use it?
Three things make Turso worth knowing about.
The free tier is exceptional. 500 databases, 9GB of storage, and 1 billion row reads per month — all free. For context, most side projects never come close to these limits. You can run a hundred different projects for free, or give every user in your app their own isolated database without paying anything until you are genuinely at scale.
The multi-tenant pattern is a killer use case. Because databases are so cheap and lightweight in Turso, a common architecture is to create one database per customer or user. Each customer's data is completely isolated by default — no risk of one customer seeing another's data, no need for row-level security policies. Create a database via the Platform API when a user signs up, store the connection string against their account, and connect to their specific database on each request.
It pairs perfectly with Drizzle ORM. Drizzle is a lightweight TypeScript ORM that has first-class Turso support. The combination gives you type-safe SQL queries, schema migrations, and a clean developer experience without the overhead of heavier ORMs.
Where to be careful: SQLite is optimised for reads. Concurrent writes — multiple requests modifying the same data simultaneously — can cause locking issues at high scale. If your app is write-heavy (a chat app, real-time counters, high-frequency logging), a database like Supabase (PostgreSQL) or PlanetScale (MySQL) handles that pattern better.
Free vs Paid
| Feature | Free (Starter) | Scaler ($29/mo) | Pro ($59/mo) |
|---|---|---|---|
| Databases | 500 | Unlimited | Unlimited |
| Storage | 9GB total | 24GB | 100GB+ |
| Row reads | 1B/month | 100B/month | Unlimited |
| Row writes | 25M/month | 100M/month | Unlimited |
| Locations (edge) | 3 | 6 | All regions |
| Support | Community | Priority |
The free tier is genuinely usable for real applications, not just demos.
Step-by-step setup
- Go to turso.tech and create a free account
- Install the Turso CLI:
brew install tursodatabase/tap/turso(macOS) or follow the instructions for your OS - Log in:
turso auth login - Create your first database:
turso db create my-app-db - Get your database URL:
turso db show my-app-db --url - Create an auth token:
turso db tokens create my-app-db - Add both values to your
.envfile:TURSO_DATABASE_URL=libsql://your-db.turso.io TURSO_AUTH_TOKEN=your-token-here - In your Next.js or Node app, install the client:
npm install @libsql/client - Connect and run your first query — or set up Drizzle ORM for a typed schema and migrations
Total setup time is around 10 minutes, and there is nothing to configure on the server side.
Common questions
How does Turso compare to Supabase? Supabase uses PostgreSQL, which handles concurrent writes better and has a richer feature set (realtime subscriptions, Auth, Storage, Edge Functions). Turso is simpler, has a more generous free tier, and is faster for read-heavy workloads at the edge. For a personal project or read-heavy app, Turso is often the better fit. For a full-stack app with auth, real-time features, and complex queries, Supabase is more complete.
Can I use Turso with Prisma? There is experimental Prisma support for libSQL, but it is not as mature as the Drizzle integration. If you are starting fresh, Drizzle with Turso is the recommended combination and has the most documentation and community support.
What happens when I exceed the free tier limits? Turso will prompt you to upgrade rather than silently failing. At 500 databases or 9GB of storage, you have likely built something worth paying for — the Scaler plan at $29/month covers most growing projects.
Is Turso suitable for production? Yes, with caveats. It is a newer product (founded 2022) and the ecosystem is smaller than PostgreSQL or MySQL. Many teams run it in production successfully, particularly for read-heavy workloads and multi-tenant architectures. Check the Turso status page and community Discord before committing it to a high-stakes production system.