Softwr

Databases · head to head

MotherDuck vs Turso

MotherDuck logo

MotherDuck

Databases

Serverless analytics data warehouse built on DuckDB

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: MotherDuck the free Lite plan caps compute at 10 hours per month, which limits it to light or hobbyist workloads.; 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: MotherDuck covers Serverless DuckDB instances, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which MotherDuck and Turso actually diverge.

Attributes where MotherDuck and Turso differ
AttributeMotherDuckTurso
Pricing modelusage-basedfreemium
Platformsweb, apiWeb
Founded2022Unknown

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 MotherDuck

  • Serverless DuckDB instances
  • Cloud storage querying
  • MCP server
  • Dives
  • Flights
  • Read-scaling replicas

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.

MotherDuck

  • Ad-hoc analytics on gigabyte-to-terabyte datasetsnot Turso
  • Querying data lake files in S3/GCS/Azure without ingestionnot Turso
  • AI agent data analysis via MCPnot Turso
  • Scheduled data pipeline transformationsnot Turso

Turso

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

Where each one falls short

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

MotherDuck

  • The free Lite plan caps compute at 10 hours per month, which limits it to light or hobbyist workloads.
  • Business plan usage charges on top of the $250/month base can make costs less predictable than flat-rate competitors.
  • There are no academic or non-profit discounts, unlike some competing data platforms.
  • Annual billing requires going through a sales conversation rather than a self-serve toggle.

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

MotherDuck

Free
  • LiteFree
    • Up to 3 internal active users
    • 2 service accounts
    • 10GB free storage
  • Business$250/month
    • Up to 10 internal active users
    • Unlimited service accounts
    • 5 instance types with read-scaling replicas
  • Enterprise$undefined/month
    • Unlimited internal users and service accounts
    • Fixed-cost capacity pricing
    • AWS PrivateLink, IP allowlisting

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 MotherDuck if

  • You need serverless duckdb instances.
  • You want to start without paying.
  • You work on web, api.
  • You also want cloud storage querying.
MotherDuck 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 MotherDuck or Turso better?
Neither clearly leads. MotherDuck 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, MotherDuck or Turso?
MotherDuck starts at Free and Turso at Free.
Does MotherDuck or Turso run on more platforms?
MotherDuck runs on web, api. Turso runs on Web.
Can I use MotherDuck for free?
Both have a free tier, so you can try either at no cost before committing.
What is MotherDuck best used for?
MotherDuck is most often used for ad-hoc analytics on gigabyte-to-terabyte datasets, querying data lake files in s3/gcs/azure without ingestion, ai agent data analysis via mcp, scheduled data pipeline transformations. Of those, ad-hoc analytics on gigabyte-to-terabyte datasets and querying data lake files in s3/gcs/azure without ingestion are not what Turso is typically brought in for.
What can MotherDuck do that Turso cannot?
MotherDuck covers Serverless DuckDB instances, Cloud storage querying, MCP server, Dives. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

MotherDuck: What does MotherDuck cost?

The Lite plan is free (up to 3 users, 10GB storage, 10 hours of Pulse compute/month). Business is $250/organization/month plus usage, with Enterprise available at custom fixed-cost pricing.

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.

MotherDuck: Is there a free plan and what are its limits?

Yes, the Lite plan is free for up to 3 internal active users and 2 service accounts, with 10GB of storage and 10 hours of Pulse compute per month.

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.

MotherDuck: How is usage metered?

Compute instances (Pulse, Standard, Jumbo, Mega, Giga) are billed per second at hourly rates from $0.60 to $24.00/hour, storage is $0.04/GB-month, and AI Functions cost $1.00 per AI Unit.

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 MotherDuck

More on Turso

Keep looking

Other head to heads