Supabase is acquiring Turso
Supabase’s acquisition of Turso, a Rust-based, SQLite-compatible database focused on better concurrency and async use, is being met with a mix of excitement and skepticism. Supporters see it as a strategic fit: Turso could power lightweight, edge and agent-driven workloads, with Supabase/Postgres taking over as applications scale, all while the core remains open source. Critics worry about Turso’s past performance issues, the risk that an acquirer might eventually sideline the technology, and the broader tension between open-source ideals and venture-backed exit dynamics.
Overall reaction to the acquisition
- Many are excited; see it as a strong strategic fit and “win-win” for Supabase, Turso, and users.
- Others are unhappy or anxious, fearing Turso may be deprecated or reshaped into an “incredible journey” story.
- Some express conditional optimism, hoping Turso will actually get more resources and become safer for production.
Business and open-source implications
- Multiple comments worry that acquisitions often kill products despite initial assurances.
- Turso’s leadership says the company was doing well, with strong revenue growth, and calls this a strategic move, not a distress sale.
- The fully MIT-licensed core is seen as a positive; some question how hosting revenue sustains when the core is free, others note managed hosting, compliance, and liability as strong value-adds.
SQLite vs Turso vs Postgres: technical angles
- Turso is framed as a SQLite-compatible Rust rewrite aiming for:
- Better concurrency and multiple writers.
- Async I/O, better search, and vector/graph features.
- An embedded database usable from “safe” languages and possibly multiple SQL dialects.
- SQLite is praised as extremely robust and battle-tested; some argue it should never be rewritten.
- Others counter that rewrites in Rust for concurrency and safety can push the field forward.
Performance, stability, and “vibe coding” concerns
- A ClickBench thread is cited where Turso was extremely slow at data ingestion; critics attribute this partly to heavy LLM/“vibe” coding.
- Turso maintainers respond that early benchmarks were premature, ingestion issues are known, and not top priority yet.
- Some users report good real-world performance (e.g., Rust async workloads); others report serious latency issues in certain regions and weak monitoring.
Supabase strategy and agentic/edge use cases
- Supabase employees describe Turso/SQLite as complementary to Postgres:
- Turso for tiny, on-demand, agent-created or edge workloads.
- Postgres for larger, scaled production workloads.
- Plan mentioned for a very small “Spark” tier powered by Turso.
- Several see SQLite/Turso plus edge networks as ideal for 0→1 projects and LLM/agent workflows.
Governance and culture debates
- Some criticize SQLite’s religiously filtered governance as “cult-like” and welcome a more open community model.
- Others defend SQLite’s governance as intentional and protective, pushing back on the “cult” characterization.