“Turso has been fantastic for us to deliver our Optimize product, helping developers improve their database performance. Thank you to the Turso team!”
DatabaseMaker says so · source ↗
Turso
Managed SQLite (libSQL) with replicas and cheap per-tenant databases.
13 makers' products we track use Turso. For database it's 12th most chosen of 23 options: 13 of the 1,263 makers' products we know the database of (1%). Among the 397 launched in 2026, 0% chose it, against 1% of those launched in 2024 or earlier. 36 open-source projects also declare it in their code. What makers like most: It keeps SQLite's simplicity while scaling for edge and serverless apps, and moving from local development to hosted is easy. Their most common complaint: The Rust rewrite is still beta, with panics, data-corrupting bugs and thin test coverage that undermine trust for production. On GitHub, 22 public pull requests moved projects to Turso from tools we list, and 12 moved them away.
Profile checked
Works with AI agents:llms.txtCLIHow makers use Turso
Makers' products we track use Turso for database (13), most often alongside Vercel (46%).
What Turso is used for
Turso vs the alternatives makers chose
For database, 13 of the 1,263 makers' products we know the choice of picked Turso (1%), behind Supabase (45%).
| Option | Makers' products | 2026 launches | Free for | At 10,000 users | Open source | |
|---|---|---|---|---|---|---|
| 573 45% | 63% | ~500 users | $25/mo · Pro | Yes | Compare → | |
| 187 15% | 9% | ~2,000 users | $9.66/mo · Blaze (pay as you go) | No | ||
| 128 10% | 5% | ~500 users | $58/mo · Atlas Dedicated M10 | No | ||
| 98 8% | 1% | — | — | Yes | Compare → | |
| 96 8% | 11% | None | $22/mo · Launch | Yes | Compare → | |
| 50 4% | 7% | ~630 users | $29/mo · Professional | Yes | ||
| 13 1% | 0% | ~5,900 users | $5.99/mo · Developer | Yes |
For database: how many of the 1,263 makers' products we know the database of chose each option, and the share among the 397 launched in 2026, since a tool that came first has products from every year, and what each costs at 10,000 users.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for.
Often paired with
Share of the 13 makers' products on Turso that show this choice.When to use Turso, and when not
Something else fits better if
- You want the database, auth and file storage in one project, and plain SQL you can take elsewhere: Supabase.
- You're building a live, collaborative app entirely in TypeScript: Convex.
- Your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much: Neon.
- You already run your own server and want a flat monthly cost: PostgreSQL.
Turso is SQLite turned into a networked, managed service. It keeps SQLite's simplicity while letting many servers reach a database over the network, and makes it practical to create thousands of small databases, such as one per tenant, through an API.
More about Turso
Turso Cloud hosts two SQLite-compatible engines. libSQL is a fork of SQLite with the same file format, used in production for years. Turso Database is a ground-up rewrite that allows concurrent writes from many clients; on Turso Cloud it is in early preview. You connect over the network with SDKs for TypeScript, Python, Go and Rust (Drizzle and Prisma run on @libsql/client) or plain SQL over HTTP, or you keep a local copy in the app.
That local copy is the distinctive part. An embedded replica keeps a database file next to your code so reads take microseconds, while writes go to the cloud primary and are synced back. The newer Turso Sync goes further, with local-first writes and explicit push() and pull(), which suits mobile and offline apps. Other features: copy a database to make a branch, point-in-time recovery, native vector search, and export to a plain SQLite file. Both engines are open source and run locally without the cloud.
Limits: it is SQLite underneath, with SQLite's SQL dialect. A few pragmas such as user_version and journal_mode are read-only or unsupported on Turso Cloud, branches never merge back automatically, and the older edge-replica feature is closed to new users.
How Turso itself is built
4 tools, from its own code, website and Product Hunt page.
Turso pros and cons
What makers like most: It keeps SQLite's simplicity while scaling for edge and serverless apps, and moving from local development to hosted is easy. Their most common complaint: The Rust rewrite is still beta, with panics, data-corrupting bugs and thin test coverage that undermine trust for production.
Pros
- It keeps SQLite's simplicity while scaling for edge and serverless apps, and moving from local development to hosted is easy. PHHN
- A database per tenant and embedded replicas make single-tenant designs and local-first or offline apps straightforward. PHPH 2HN
- The Rust rewrite adds async I/O, concurrent writes, encryption, change data capture and vector search while staying SQLite file-compatible. HNHN 2HN 3HN 4
- The engine is MIT-licensed, including a test suite, unlike SQLite's proprietary tests. HNHN 2
Cons and watch-outs
- The Rust rewrite is still beta, with panics, data-corrupting bugs and thin test coverage that undermine trust for production. HNHN 2HN 3HN 4
- The split between libSQL and the new Turso packages is confusing, and libSQL showed memory leaks on large write jobs. HNHN 2HN 3
- Compatibility with SQLite is incomplete; for example, another process cannot read a WAL database it has open. HNHN 2
- The rewrite pulls in thousands of dependencies. HNHN 2
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.
5.0★ from 15 reviews on Product Hunt ↗What Hacker News says about Turso
On Hacker News, 20% of comments about Turso recommend it and 13% criticize it: net praise +7%.
By year
| Year | Comments choosing it, per month | Net praise |
|---|---|---|
| 2023 | 0.3 | +29% |
| 2024 | 0.3 | −10% |
| 2025 | 0.5 | +6% |
| 2026 (8 mo) | 0.6 | +8% |
In their words
- “I love turso sqlite and haven't faced any issues.” HN, Jul 2026
- “We switched our main API from Postgres to Turso last month and haven't looked back.” HN, Jan 2026
- “there are a lot of people pushing sqlite above its weight as well (Turso and the likes)” HN, Jun 2026
Hacker News comments January 2023 to August 2026 that name Turso in a sentence like "I use" or "we moved to", Claude read a sample of 46 and the counts scale it to all of them; net praise is comments recommending it minus comments criticizing it, as a share of all comments about it. How it's counted, and how HN compares with makers.
Reliability and open issues
The most wanted open issue on GitHub has 28 👍.
Most wanted on GitHub
- Rust Diesel Support 👍 28 · opened Mar 2024 · active Mar 2026
Who switches
More projects move to Turso: 22 pull requests in, 12 out; the most come from Supabase and leave for Neon.
Supabase → Turso11 PRs
- Migrate from Supabase to Turso (libSQL/SQLite)profullstack/meshhook · 2026-08-11
- refactor: migrate database storage from Supabase to Turso and update …schraderweb/schraderweb · 2026-08-08
- Add a one-shot Supabase to Turso data migrationkaleinoue/For-the-boys · 2026-07-28
- Migrate backend from Supabase to Turso (libSQL)sylvaindiv/atomic-crm · 2026-07-23
- Migrate from Supabase to Turso (libSQL) + Auth.jsaruntemme/creed · 2026-06-24
- feat(etl): add Supabase to Turso data migration script with SOCKS proxy supportpkking/action-insight · 2026-06-07
- Migrate database from Supabase to Turso, fix auth/routing/state bugsxitali/emanuelw.pl · 2026-04-07
- Migration: db change from supabase to tursoff1892/communality · 2026-02-27
- Migrate from Supabase to Turso with ULID supportopenstory-so/openstory · 2025-11-17
- Migrate Watchlist Favorites/Ratings Data from Supabase to Tursocinemagoria/cinemagoria · 2025-11-15
Neon → Turso7 PRs
- Migrate from Neon PostgreSQL to Turso SQLiteharshi79/vibebin · 2026-08-29
- feat: migrate production database from Neon to Tursottizze/digital-buddhism · 2026-08-29
- feat(repo): migrate database from Neon Postgres to Turso (libSQL)johinsDev/loyalty-app · 2026-05-27
- Migrate database from Supabase/Neon to Turso (libSQL + Drizzle)heaventree/flowbase-productive-ai-app · 2026-05-21
- Claude/migrate neon to turso e ms motobipch/CubeFeed · 2026-05-13
- Claude/migrate neon to turso e ms motobipch/CubeFeed · 2026-05-13
- feat(database): migrate database from Neon to Tursophantanhoancuong/wordest · 2026-03-09
PostgreSQL → Turso4 PRs
- Migrate Payload DB from Postgres to Turso SQLitehephatech/feelings.bar · 2026-07-29
- Migrate database from Netlify (Postgres) to Turso (SQLite)smkdwiguna/dwiguna-info · 2026-06-08
- feat(repo): migrate database from Neon Postgres to Turso (libSQL)johinsDev/loyalty-app · 2026-05-27
- 133 f migrates from postgres to tursoacmutsa/ClubKit · 2025-03-03
Turso → Neon6 PRs
- feat(api): move the database from Turso to Neon Postgres (JEF-342)mankatcheung/trakwyn · 2026-09-18
- fix: migrate hosted DB from libSQL/Turso to Neon Postgresjoerickson/Wallet-Scanner · 2026-04-25
- feat: migrate database from Turso to Neon Postgresrlfarman/rej-studio · 2026-04-05
- feat(db): migrate from turso to neonkapishdima/shadcn-rss · 2026-01-19
- Migrate from Turso to Neonmetaideas/init · 2025-05-15
- Migrate from Turso to neontechulus/manage · 2025-04-05
Turso → PostgreSQL6 PRs
- web: theme votes, page views and cookbook sales move from Turso to Postgresprofullstack/hqtui · 2026-09-25
- Move the waitlist from Turso to Postgresprofullstack/opensourcelegends.com · 2026-09-25
- Migrate from Turso to Postgres (happy path)tryy3/warera-tools · 2026-09-19
- Port DB from SQLite/Turso to Postgres on Neon (#96, #97, #98)zachradtka/nextopp · 2026-05-27
- Switch from Turso to Vercel Postgres (no extra signup)AlaudaAI/google-review-skill · 2026-02-16
- change vote from turso to Postgres test using filter by label = Milodatum-cloud/datum.net · 2025-06-18
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general.
Who uses it
13 makers' products, each linked to the source that shows it, and 36 open-source projects that declare it in their code. The best known on Product Hunt: Anarlog (610 followers), reconfigured (333 followers), SF Apartment Finder (320 followers), EmailCatcher (307 followers), Haxiom (151 followers). 4 of the makers' products are gone now (domain lapsed, up for sale or taken down); they chose Turso while live.
“Lightweight, distributed SQLite that just works. Perfect for edge setups and production use cases.”
DatabaseMaker says so · source ↗“Used for database. Easy to use.”
DatabaseMaker says so · source ↗“So easy to set up and get us to MVP in no time.”
DatabaseMaker says so · source ↗“Turso is my database! Turso made it really easy to switch from local development to hosted on the cloud.”
DatabaseMaker says so · source ↗“Helped us build a great local-first database!”
DatabaseMaker says so · source ↗“We love Turso because it combines the simplicity of SQLite with the scalability we need for production. It works seamlessly for edge and serverless applications, which makes it perfect for the kind of projects we build.”
DatabaseMaker says so · source ↗“The best developer experience for creating and managing our databases.”
DatabaseMaker says so · source ↗“We wanted to build application that has single tenant databases for each organization. Turso handles that super nicely. In addition the ability to have embedded replicas is killer feature for building local RAG.”
DatabaseMaker says so · source ↗“super easy db and integrated with vercel well”
DatabaseMaker says so · source ↗“Turso is amazing for edge databases—blazing-fast reads/writes, easy dev setup, and scales globally without the usual backend headaches. Perfect for modern apps. We used it for Analytics, great experience overall.”
DatabaseMaker says so · source ↗“We chose Turso for undb because it perfectly aligns with our core values of being local-first, offline-first, and privacy-first. Turso offers a lightweight, distributed database that’s built on SQLite, making it an ideal fit for undb’s architecture. Unlike other databases, Turso provides the flexibility and scalability we need without compromising on performance or data control. Its edge-first approach ensures that our users can enjoy low-latency access and a seamless experience, whether they’re working offline or online. By integrating with Turso, we’re able to deliver a robust and efficient platform that meets the needs of both developers and no-code users.”
DatabaseMaker says so · source ↗“We like Turso cause it's edge-hosted, distributed database designed to minimize query latency for our application.”
DatabaseMaker says so · source ↗None of these in makers' own words.
Open source: a project that declares Turso as a dependency in its public code — verifiable, but not necessarily a live product.
What its projects tell coding agents
18 of the 25 open-source products built with Turso that were worked on in the last 180 days keep instruction files for coding agents — 72%, against 53% of all the projects we read. AGENTS.md is in 17, CLAUDE.md in 10.
Alternatives to Turso
All alternatives by situation →Further reading
Questions makers ask about Turso
Is Turso good for production?
13 makers' products we track run on it, and 4 of them have since gone (the product, not necessarily because of Turso). On GitHub, 22 public pull requests moved projects to Turso from tools we list, and 12 moved them away. The watch-out makers raise most: The Rust rewrite is still beta, with panics, data-corrupting bugs and thin test coverage that undermine trust for production.
What is Turso used for?
Managed SQLite (libSQL) with replicas and cheap per-tenant databases. Makers' products we track use it for database (13).
What are the pros and cons of Turso?
Pros makers name: It keeps SQLite's simplicity while scaling for edge and serverless apps, and moving from local development to hosted is easy. A database per tenant and embedded replicas make single-tenant designs and local-first or offline apps straightforward. The Rust rewrite adds async I/O, concurrent writes, encryption, change data capture and vector search while staying SQLite file-compatible. Cons: The Rust rewrite is still beta, with panics, data-corrupting bugs and thin test coverage that undermine trust for production. The split between libSQL and the new Turso packages is confusing, and libSQL showed memory leaks on large write jobs. Compatibility with SQLite is incomplete; for example, another process cannot read a WAL database it has open.
What are the alternatives to Turso?
For database, the other options makers' products we track chose most are Supabase (573), Firebase (187), MongoDB (128), PostgreSQL (98), Neon (96), Convex (50). Open source or self-hostable among them: Supabase, MongoDB, PostgreSQL, Neon, Convex. Each alternative, with the situation it fits, is on the Turso alternatives page.
How much does Turso cost per month?
At 10,000 users, Turso costs $5.99 a month on the cheapest plan that fits (Developer), from its pricing page.
Do developers switch to or away from Turso?
On GitHub, 22 public pull requests moved projects to Turso from tools we list, most from Supabase (11), Neon (7), PostgreSQL (4); 12 moved them away, most to Neon (6), PostgreSQL (6).
Which package should I use for my app?
Use the Turso packages for anything local, whether embedded, offline or synced with the cloud. For network-only access, use the serverless driver for Turso Database or the libSQL client for libSQL databases. SDKs exist for TypeScript, Python, Go and Rust. source ↗
Can I use it with Drizzle or Prisma?
Yes. In TypeScript, Drizzle and Prisma run on the @libsql/client driver. source ↗
How do embedded replicas handle writes and offline use?
Reads come from the local file, while writes go to the remote primary by default and then update the local copy, so you read your own writes. Setting offline to true allows local writes, and syncInterval controls periodic syncing. For new projects that need sync, Turso recommends Turso Sync instead. source ↗
Can I import my existing SQLite database?
Yes. Switch the file to WAL mode and checkpoint it, then run turso db import with the file, or use the Platform API. source ↗
Can I get my data out again?
Yes. turso db export writes a snapshot of a database to a local SQLite file; the snapshot may lag the newest writes, which you can then pull with an SDK sync. source ↗
What SQLite features behave differently on Turso Cloud?
PRAGMA user_version and application_id are read-only, and busy_timeout and journal_mode are not supported because Turso manages concurrency and journaling itself. Track schema versions in a table instead. source ↗
Can I develop locally without Turso Cloud?
Yes. The Turso packages open a local SQLite-compatible file in your process with no server or auth token, and the Turso CLI can also run a local libSQL server. source ↗
Is Turso free?
Yes — there is a free tier a small product can run on; paid use starts at $4.99/mo. source ↗
Is Turso open source or self-hostable?
Open source, and you can self-host it. source ↗
Can AI coding agents work with Turso?
It serves an llms.txt docs index; it has an official CLI (turso).
Who uses Turso?
13 makers' products we track, each with a source, and 36 open-source projects declare it in their code. The best known of them on Product Hunt: Anarlog (610 followers), reconfigured (333 followers), SF Apartment Finder (320 followers), EmailCatcher (307 followers), Haxiom (151 followers). source ↗