Softwr

Databases · head to head

ClickHouse vs Turso

ClickHouse logo

ClickHouse

Databases

Fast open-source column-oriented database for real-time analytics

From
Free
Rated
-
Full reviewWebsite
Turso logo

Turso

Databases

SQLite-lineage database platform for running very large numbers of small per-tenant databases, with an MIT-licensed engine.

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: ClickHouse limited multi-row atomic transactions and expensive UPDATE/DELETE operations unsuitable for transactional systems; Turso sQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option.
  • They diverge on capability: ClickHouse covers Column-oriented Storage, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which ClickHouse and Turso actually diverge.

Attributes where ClickHouse and Turso differ
AttributeClickHouseTurso
Pricing modelUnknownfreemium
PlatformsLinux, macOS, Windows (via Docker)Web
Founded2021Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in ClickHouse

  • Column-oriented Storage
  • Real-time Analytics
  • SQL Support
  • Linear Scalability
  • Data Compression
  • Vectorized Query Execution
  • Approximate Calculations
  • Kafka

Only in Turso

  • Per-tenant databases
  • MIT licence
  • Embedded replicas
  • SQLite compatibility
  • HTTP access
  • Branching
  • Point-in-time restore
  • In-process engine

What people use each for

The jobs each tool is most often brought in to do.

ClickHouse

  • Business intelligencenot Turso
  • Data warehousingnot Turso
  • Real-time analyticsnot Turso
  • Reportingnot Turso
  • Machine learningnot Turso

Turso

  • Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot ClickHouse
  • Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot ClickHouse
  • Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot ClickHouse
  • Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot ClickHouse

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

ClickHouse

  • Limited multi-row atomic transactions and expensive UPDATE/DELETE operations unsuitable for transactional systems
  • Requires upfront schema design discipline with MergeTree engine choices and sort/partition keys
  • Experimental vector search support, not production-ready for vector operations
  • Different query syntax from standard SQL requiring migration planning
  • Limited JOIN capabilities compared to traditional relational databases
  • Migration complexity with 2-4 weeks estimated for data type mapping and query translation

Turso

  • SQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option.
  • Per-tenant databases mean per-tenant migrations, so every schema change becomes a fan-out job that must be idempotent and resumable, and multi-database schemas, the feature meant to solve this, is deprecated.
  • There are no cross-database queries; ATTACH is deprecated on the cloud, so any report or analytic spanning tenants must be assembled in your application or in a separate warehouse you also operate.
  • Data Edge, the multi-region edge replication that was Turso's original positioning, is deprecated, so a large share of the tutorials and articles describing Turso as an edge database describe behaviour you can no longer rely on.
  • Three engine lineages share the name, SQLite, the libSQL fork and the Rust rewrite, and the Rust engine is still maturing, so SQLite compatibility needs verifying against your specific pragmas, extensions and query patterns; the cloud already restricts journal_mode and busy_timeout and makes user_version read-only.

Pricing, plan by plan

ClickHouse

Free

No published plan breakdown. See the ClickHouse review.

Turso

Free
  • FreeFree
    • 100 databases
    • 5 GB storage
    • 500M monthly rows read
  • Developer$4.99/month
    • Unlimited databases
    • 9 GB storage
    • 2.5B monthly rows read
  • Scaler$24.92/month
    • Unlimited databases
    • 24 GB storage
    • 100B monthly rows read
  • Pro$416.58/month
    • Unlimited databases
    • 50 GB storage
    • 250B monthly rows read

Which should you pick?

Choose ClickHouse if

  • You need column-oriented storage.
  • You want to start without paying.
  • You work on Linux, macOS, Windows (via Docker).
  • You also want real-time analytics.
ClickHouse review

Choose Turso if

  • You need per-tenant databases.
  • You want to start without paying.
  • You also want mit licence.
Turso review

Questions people ask

Is ClickHouse or Turso better?
Neither clearly leads. ClickHouse starts at Free and Turso at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, ClickHouse or Turso?
ClickHouse starts at Free and Turso at Free.
Does ClickHouse or Turso run on more platforms?
ClickHouse runs on Linux, macOS, Windows (via Docker). Turso runs on Web.
Can I use ClickHouse for free?
Both have a free tier, so you can try either at no cost before committing.
What is ClickHouse best used for?
ClickHouse is most often used for business intelligence, data warehousing, real-time analytics, reporting. Of those, business intelligence and data warehousing are not what Turso is typically brought in for.
What can ClickHouse do that Turso cannot?
ClickHouse covers Column-oriented Storage, Real-time Analytics, SQL Support, Linear Scalability. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

ClickHouse: What is ClickHouse best used for?

ClickHouse is optimized for analytical workloads on large datasets. It excels at fast aggregations and queries, being 10-100x faster than PostgreSQL on large aggregations.

Source
Turso: Is Turso just hosted SQLite?

Not exactly. It hosts databases built on the SQLite lineage: libSQL, an MIT fork of SQLite, and Turso Database, a newer Rust rewrite. The platform adds branching, backups, an HTTP API and programmatic database creation.

ClickHouse: Does ClickHouse support transactions?

ClickHouse has limited transaction support and expensive UPDATE/DELETE operations. It is not suitable for transactional workloads requiring strict ACID guarantees.

Source
Turso: Can I really run a million databases?

That is the design goal and the platform API exists to make provisioning and deletion programmatic. The practical constraints are the ones that come with it: migrations fan out, and nothing can query across databases.

ClickHouse: How does ClickHouse compare to PostgreSQL?

ClickHouse is 10-100x faster for analytics but PostgreSQL is better for transactional workloads. Many teams use both: PostgreSQL for writes via MaterializedPostgreSQL replication to ClickHouse for analytics.

Source
Turso: How do embedded replicas handle read-after-write?

Reads come from the local replica and writes go to the primary, so a read immediately after a write can return stale data unless you wait for a sync. Application code has to account for that rather than assume it.

Turso: What licence is it under?

libSQL and Turso Database are both MIT. Turso Cloud is a commercial managed service built on them, so the engine is genuinely open even though the platform is not.

Turso: Is Turso still an edge database?

No. Data Edge, the multi-region edge replication feature, is deprecated. The current positioning is per-tenant and embedded databases, and older material describing edge replication is out of date.

Share

Related pages

More on ClickHouse

More on Turso

Keep looking

Other head to heads