Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #581

T

Turso

Company blog · turso.tech/blogprogrammingdata

Turso is the company blog at turso.tech, writing about programming and data. Since 2023, 105 different Hacker News readers have linked it 138 times, most often “Turso – Countless (SQLite) databases embedded anywhere. Simple.”. It is still writing: the last post was on 2026-10-30, and you can follow it by feed.

Visit the blog
138mentions?
2recommend?
105HN people?
2023–2026first – last linked?
Links on Hacker News per year · peak 43 in 2024

Rarely recommended · 2 of 40 sampled comments recommend it?

Why HN links it

Turso is a SQLite-based database company and project, including a Rust rewrite of SQLite. HN readers link its posts on SQLite internals, WASM, offline sync, change data capture, and pricing.

Recommended for · 2 comments
Commenters say readers 'might like' Turso's work and that a Django SQLite production config post 'maybe could help'.12

Summarised by Claude from a sample of 40 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Turso is the SQLite-based database architecture for millions of databases. Spin up a database for every user, agent, and tenant, with embedded replication, per-database encryption, and economics that scale with you.

Most-linked posts?

  1. Turso – Countless (SQLite) databases embedded anywhere. Simple.
    20 people · 22 mentions · first linked 2023-06-15
  2. Limbo: A complete rewrite of SQLite in Rust
    11 people · 11 mentions · first linked 2024-12-10
  3. Beyond the SQLite single-writer limitation with concurrent writes
    7 people · 8 mentions · first linked 2025-10-06
  4. We will rewrite SQLite. And we are going all-in
    7 people · 7 mentions · first linked 2025-01-21
  5. /pricing
    5 people · 5 mentions · first linked 2023-05-19
  6. A deep look into our new multitenant architecture
    3 people · 3 mentions · first linked 2024-10-22
  7. /
    3 people · 3 mentions · first linked 2023-07-05
  8. The Wonders of AI: We Are Retiring Our Bug Bounty Program
    3 people · 3 mentions · first linked 2026-05-13
  9. The Missing Abstraction for AI Agents: The Agent Filesystem
    2 people · 2 mentions · first linked 2025-11-15
  10. Turso 0.8: Concurrent writes without SQLite's single-writer bottleneck
    2 people · 2 mentions · first linked 2026-09-29

What Hacker News says?

  1. FYI Turso does it with WASM https://turso.tech/blog/webassembly-functions-for-your-sqlit...

    Comment linking /blog/webassembly-functions-for-your-sqlite-compatible-database-7e1ad95a2aa7

    on “Show HN: PGlite – in-browser WASM Postgres with pgvector and live sync”
  2. Submitted Working on databases from prison as a story · 849 points

    HN discussion
  3. Local first is amazing. I have been building a local first application for Invoicing since 2020 called Upcount https://www.upcount.app/ . First I used PouchDB which is also awesome https://pouchdb.com/ but now switched to SQLite and Turso https://turso.tech/ which seems to fit my needs much better.

    Comment linking /

    on “Linear sent me down a local-first rabbit hole”
  4. Submitted Limbo: A complete rewrite of SQLite in Rust as a story · 373 points

    HN discussion
  5. So much fun streaming/sync/cdc stuff happening, all so cool. Having an underlying FUSE driver doing the Change Data Capture is really neat. This looks like such an incredibly lightweight way to remote-connect to sqlite. And to add a sort of exterior transaction management. Different use case, but makes me think of sqlite Rewrite-it-it-Rust Turso announcing AgentFS. Here the roles are flipped, sqlite is acting as a f…

    Comment linking /blog/agentfs

    on “Litestream VFS”
  6. Submitted Turso SQLite Offline Sync Public Beta as a story · 222 points

    HN discussion
  7. the sqlite RIIR is going quite well: https://turso.tech/blog/beyond-the-single-writer-limitation-... (sqlite is quite a bit smaller than DuckDB tho)

    Comment linking /blog/beyond-the-single-writer-limitation-with-tursos-concurrent-writes

    on “Notes by djb on using Fil-C”
  8. Submitted Beyond the SQLite single-writer limitation with concurrent writes as a story · 80 points

    HN discussion
  9. "SQLite could be recoded in Go or Rust, but doing so would probably introduce far more bugs than would be fixed, and it may also result in slower code." We will see. On the Rust side there is Turso which is pretty active. https://turso.tech/

    Comment linking /

    on “Why Is SQLite Coded In C”
  10. Submitted The first alpha of Turso: The next evolution of SQLite as a story · 70 points

    HN discussion
  11. fwiw there's a project doing just that: https://github.com/tursodatabase/turso they have a blog hinting at some answers as to "why": https://turso.tech/blog/introducing-limbo-a-complete-rewrite...

    Comment linking /blog/introducing-limbo-a-complete-rewrite-of-sqlite-in-rust

    on “Why Is SQLite Coded In C”
  12. Submitted An adventure in writing compatible systems as a story · 47 points

    HN discussion
  13. Turso: https://algora.io/challenges/turso "Turso is rewriting SQLite in Rust ; Find a bug to win $1,000" ------ - Dec 10, 2024 : "Introducing Limbo: A complete rewrite of SQLite in Rust" https://turso.tech/blog/introducing-limbo-a-complete-rewrite... - Jan 21, 2025 - "We will rewrite SQLite. And we are going all-in" https://turso.tech/blog/we-will-rewrite-sqlite-and-we-are-go... - Project: https://github.com/tursoda…

    Comment linking /blog/we-will-rewrite-sqlite-and-we-are-going-all-in

    on “Why Is SQLite Coded In C”
  14. Submitted The Wonders of AI: We Are Retiring Our Bug Bounty Program as a story · 44 points

    HN discussion
  15. > It's right there in “your” manifesto. https://turso.tech/libsql-manifesto Hard to believe they actually went after D. Richard Hipp--a guy I've only ever heard described as extremely warm, honest, and generous--and for his faith, no less. But then again, these are Rust people, so I guess I shouldn't be surprised, should I?

    Comment linking /libsql-manifesto

    on “In Search of a Faster SQLite”
  16. Submitted Introducing the first alpha of Turso: The next evolution of SQLite as a story · 21 points

    HN discussion
  17. > we're not going to even attempt to replicate the rigorous, arduous, and closed-source testing Almost everything you've said is wrong, but this one is trivially easy to prove wrong. You say "not even going to attempt" but they plan to take testing seriously from the get go. They say: > Since this is a reimplementation, doesn’t that mean that testing is now even harder? The reality is that it is the other way around…

    Comment linking /blog/introducing-limbo-a-complete-rewrite-of-sqlite-in-rust

    on “In Search of a Faster SQLite”
  18. Submitted Do It Yourself Database CDN with Embedded Replicas as a story · 19 points

    HN discussion
  19. > This is simply not true. Can you tell me where it is being said so? It's right there in “your” manifesto. https://turso.tech/libsql-manifesto > We take our code of conduct seriously, and unlike SQLite, we do not substitute it with an unclear alternative. We strive to foster a community that values diversity, equity, and inclusion. We encourage others to speak up if they feel uncomfortable. The word toxic clearly s…

    Comment linking /blog/fully-open-source-encryption-for-sqlite-b3858225

    on “In Search of a Faster SQLite”
  20. Submitted We will rewrite SQLite. And we are going all-in as a story · 17 points

    HN discussion
  21. Their goal is to run this on their own cloud. Despite their lofty claims about community building, their projects are very much about forwarding their use case. Given that SQLite is public domain, they're not required to give anything back. So, it's very cool that they're making parts of their tech FOSS. But I've yet to see anything coming from them that isn't “just because we need it, and SQLite wouldn't do it for…

    Comment linking /

    on “In Search of a Faster SQLite”
  22. Submitted How Turso made connections to SQLite databases 575x faster as a story · 16 points

    HN discussion
  23. That pricing is quite "less generous" than Turso: https://turso.tech/pricing I'm wondering what accounts for the difference; is Turso just bleeding money on smaller tiers, etc?

    Comment linking /pricing

    on “Neon Serverless Postgres is generally available”
  24. Submitted AgentFS with FUSE: SQLite-backed agent state as a POSIX filesystem as a story · 7 points

    HN discussion
  25. I wonder if Turso https://turso.tech/ supports that use case. They support 10k databases in the step above free pricing tier.

    Comment linking /

    on “SQLite 3.45 released with JSONB support”
  26. Submitted Replacing Kafka with SQLite? as a story · 7 points

    HN discussion
  27. > Take multi-tenancy. Using a SQLite DB per tenant is a good alternative to handle that: https://turso.tech/

    Comment linking /

    on “Full text search over Postgres: Elasticsearch vs. alternatives”
  28. Submitted Turso free tier changes and layoffs as a story · 6 points

    HN discussion
  29. endymi0n · 2025-01-09Recommends
    You folks might like the work being done at turso :D https://turso.tech/blog/introducing-limbo-a-complete-rewrite...

    Comment linking /blog/introducing-limbo-a-complete-rewrite-of-sqlite-in-rust

    on “Servo Revival: 2023-2024”
  30. Submitted I am not yet ready to switch to Zig from Rust as a story · 6 points

    HN discussion

Search all of HN for turso.tech

Linked by the same people?