“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.
Works with AI agents:llms.txtCLITurso 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.
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.
Where it fits
How Turso itself is built
4 tools, from its own code, website and Product Hunt page.
Who uses it
13 makers' products, each linked to the source that shows it, and 33 open-source projects that declare it in their code.
“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 ↗“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 ↗“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 ↗“The best developer experience for creating and managing our databases.”
DatabaseMaker says so · source ↗“super easy db and integrated with vercel well”
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 ↗Open source: a project that declares Turso as a dependency in its public code — verifiable, but not necessarily a live product.
What makers say
9 makers on why they use Turso, in their own words on Product Hunt.
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.
EmailCatcherSep 2026 ↗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.
reconfiguredSep 2026 ↗Turso is my database! Turso made it really easy to switch from local development to hosted on the cloud.
CoffeeChat BotSep 2026 ↗Lightweight, distributed SQLite that just works. Perfect for edge setups and production use cases.
VoltAgentSep 2026 ↗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.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.
- 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
- 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
Reliability and open issues
- Rust Diesel Support 👍 28 · opened Mar 2024 · active Mar 2026
Who switches
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. Open a row to see the pull requests.
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 → PostgreSQL10 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
- feat(api): move the database from Turso to Neon Postgres (JEF-342)mankatcheung/trakwyn · 2026-09-18
- Migrate database layer from Turso to Supabase PostgresEllaggon/fastt · 2026-07-22
- Port DB from SQLite/Turso to Postgres on Neon (#96, #97, #98)zachradtka/nextopp · 2026-05-27
- 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
- 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
Turso → Neon7 PRs
- feat(api): move the database from Turso to Neon Postgres (JEF-342)mankatcheung/trakwyn · 2026-09-18
- Port DB from SQLite/Turso to Postgres on Neon (#96, #97, #98)zachradtka/nextopp · 2026-05-27
- 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
Alternatives to Turso
All alternatives by situation →On Product Hunt, people weigh it against: Supabase, Convex, Neon, Prisma, Upstash, PlanetScale, Xata, PocketBase, Pinecone, InstantDB.
Questions makers ask about Turso
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 33 open-source projects declare it in their code. source ↗