--- title: Turso is building a Postgres-compatible database in Rust description: Turso, the team behind the Rust-based SQLite rewrite (libSQL), is building a Postgres-compatible database on the same core engine. The architecture uses a... canonical: https://daily.dev/posts/turso-is-building-a-postgres-compatible-database-in-rust-inidui3cg twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Turso is building a Postgres-compatible database in Rust | daily.dev og:description: Turso, the team behind the Rust-based SQLite rewrite (libSQL), is building a Postgres-compatible database on the same core engine. The architecture uses a... og:url: https://daily.dev/posts/turso-is-building-a-postgres-compatible-database-in-rust-inidui3cg og:image: https://api.daily.dev/og/posts/iNiDUI3cG.png og:image:alt: Turso is building a Postgres-compatible database in Rust og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Turso is building a Postgres-compatible database in Rust **[Collections](https://daily.dev/sources/collections)** · 2 min read · 20 upvotes · 3 comments ## Summary Turso, the team behind the Rust-based SQLite rewrite (libSQL), is building a Postgres-compatible database on the same core engine. The architecture uses a single Rust VDBE bytecode VM with multiple SQL frontends — SQLite first, Postgres next. Notable design choices include auto-updating materialized views, MVCC concurrent writes, full async support with WASM (enabling browser execution), and deterministic simulation testing inspired by FoundationDB. The Postgres frontend is already runnable from source but is early-stage. The project is MIT-licensed, open to contributions, and explicitly prioritizes correctness over performance as a multi-year effort. Extensions may eventually be supported via WASM containers. ## Content The team behind libSQL — Turso's Rust rewrite of SQLite — is now working on a Postgres-compatible database built on the same core engine. The architecture is what they're calling the "LLVM of databases": a single Rust core using a VDBE bytecode VM, with multiple SQL frontends sitting on top. SQLite came first. Postgres is next. The idea is that the underlying engine stays the same; only the dialect layer changes. A few things stand out about the design: - **Auto-updating materialized views** — kept current automatically rather than requiring manual refreshes - **MVCC concurrent writes** — proper multi-version concurrency control - **Full async support** — including WASM, which means it can run in a browser - **Deterministic simulation testing** — the same approach that's made libSQL unusually reliable The Postgres frontend is already runnable from source. The team is aiming for broad Postgres compatibility rather than 100% parity, which is an honest framing — full parity with Postgres is a moving target nobody has actually hit. Extensions may be supported via WASM containers. It's MIT-licensed and open to contributions. They're framing this as a multi-year effort with correctness prioritized over raw performance, which is probably the right call at this stage. For context: Turso already pulled this off once with SQLite, turning it into an embeddable, async-capable, cloud-friendly engine without losing what made SQLite good. Doing the same for Postgres is a bigger lift, but the architectural groundwork is already there. ## Community discussion Top comments from developers on daily.dev. **@alwaisy** · 0 upvotes > it's new sensation in tech industry. turos was sucessful. only reason decision makers avoid is it has concurrent write issues. sqlite conventions. but pg has no such thing. it's a good move for this turso as a company itself. > > meet big players. neon. xata. planetscale. vercel. supabase. **@coderkini** · 0 upvotes > interesting, how is this different from [https://github.com/malisper/pgrust](https://github.com/malisper/pgrust)? While the SQLite rewrite had a defensible reason of ability for community to contribute new features, I wonder what's the word on the Postgres rewrite. > > Another day, another Rust rewrite. It's like become fashionable to rewrite battle-tested software. Sometimes for "memory safety" or "hey because it's C/C++, we HAVE to rewrite it in Rust" or "hey we did/will do it with Claude/Copilot/". Seldom do we get to hear projects going the rewrite path for... **@vitaminncpp** · 0 upvotes > shall we have Nodejs rewrite in Rust ATP. ## Similar posts on daily.dev - [Deep dive into Turso, the "SQLite rewrite in Rust"](https://daily.dev/posts/deep-dive-into-turso-the-sqlite-rewrite-in-rust--kn9wn7dsd) · Hacker News · 58 upvotes · 6 comments --- Tags: [#rust](https://daily.dev/tags/rust), [#postgresql](https://daily.dev/tags/postgresql), [#sqlite](https://daily.dev/tags/sqlite) [View this post on daily.dev](https://daily.dev/posts/turso-is-building-a-postgres-compatible-database-in-rust-inidui3cg) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Turso is building a Postgres-compatible database in Rust","url":"https://daily.dev/posts/turso-is-building-a-postgres-compatible-database-in-rust-inidui3cg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/turso-is-building-a-postgres-compatible-database-in-rust-inidui3cg"},"datePublished":"2026-07-18T19:44:32.733Z","dateModified":"2026-07-22T16:06:06.910Z","description":"Turso, the team behind the Rust-based SQLite rewrite (libSQL), is building a Postgres-compatible database on the same core engine. The architecture uses a...","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":3,"discussionUrl":"https://daily.dev/posts/turso-is-building-a-postgres-compatible-database-in-rust-inidui3cg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":20},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":3}],"keywords":"rust,postgresql,sqlite","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Turso is building a Postgres-compatible database in Rust"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/turso-is-building-a-postgres-compatible-database-in-rust-inidui3cg","comment":[{"@type":"Comment","text":"it’s new sensation in tech industry. turos was sucessful. only reason decision makers avoid is it has concurrent write issues. sqlite conventions. but pg has no such thing. it’s a good move for this turso as a company itself.\nmeet big players. neon. xata. planetscale. vercel. supabase.","datePublished":"2026-07-19T11:26:07.442Z","dateModified":"2026-07-19T11:26:40.834Z","url":"https://daily.dev/posts/iNiDUI3cG#c-mZsA6OW9G","author":{"@type":"Person","name":"Awais Alwaisy","url":"https://daily.dev/alwaisy","image":"https://avatars.githubusercontent.com/u/102944304?v=4"}},{"@type":"Comment","text":"interesting, how is this different from https://github.com/malisper/pgrust? While the SQLite rewrite had a defensible reason of ability for community to contribute new features, I wonder what’s the word on the Postgres rewrite.\nAnother day, another Rust rewrite. It’s like become fashionable to rewrite battle-tested software. Sometimes for “memory safety” or “hey because it’s C/C++, we HAVE to rewrite it in Rust” or “hey we did/will do it with Claude/Copilot/<some other coding agent>”. Seldom do we get to hear projects going the rewrite path for legitimate functional or technical reasons.\nWhile Rust’s tooling, compiler and borrow-checker are attractive features, IMHO we must not use those alone as escape-hatches to throw away good, stable and widely adopted code written in whatever language it was written it.","datePublished":"2026-07-20T04:20:48.200Z","dateModified":"2026-07-20T04:21:43.471Z","url":"https://daily.dev/posts/iNiDUI3cG#c-8R1ZMhDWA","author":{"@type":"Person","name":"Ranganath Kini","url":"https://daily.dev/coderkini","image":"https://avatars.githubusercontent.com/u/117920663?v=4"}},{"@type":"Comment","text":"shall we have Nodejs rewrite in Rust ATP.","datePublished":"2026-07-22T14:05:44.758Z","url":"https://daily.dev/posts/iNiDUI3cG#c-XWMC20SLN","author":{"@type":"Person","name":"Akshay","url":"https://daily.dev/vitaminncpp"}}]} ```