Softwr

Databases · head to head

CosmosDB vs Turso

CosmosDB logo

CosmosDB

Databases

Globally distributed, multi-model database service from Azure

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: CosmosDB autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used; 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: CosmosDB covers Global Distribution, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which CosmosDB and Turso actually diverge.

Attributes where CosmosDB and Turso differ
AttributeCosmosDBTurso
Pricing modelusage-basedfreemium
PlatformsWeb, AzureWeb
Founded1975Unknown

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 CosmosDB

  • Global Distribution
  • Multi-model APIs
  • Elastic Scaling
  • Five Consistency Levels
  • SLA-backed Latency
  • Automatic Indexing
  • Serverless
  • Azure Functions

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.

CosmosDB

  • Running a globally distributed multi model database on Azurenot Turso
  • Serving low latency reads and writes from multiple Azure regionsnot Turso
  • Storing document, key value and graph data behind a managed servicenot Turso

Turso

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

Where each one falls short

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

CosmosDB

  • Autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used
  • Provisioned throughput is charged in every region the account is replicated to, so multi region accounts multiply the RU bill
  • Storage charges cover data, indexes and backups in each replicated region
  • Egress out of Azure and between regions is charged, though ingress is free
  • The free allowance is one account per Azure subscription, limited to 1,000 RU/s and 25 GB
  • RU/s rates vary by region and are only shown through the pricing calculator rather than a flat published rate

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

CosmosDB

Free
  • Free TierFree
    • 1000 RU/s
    • 25GB storage
    • First 12 months
  • ServerlessFree
    • Pay per request
    • Auto-scaling
    • Event-driven workloads

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

  • You need global distribution.
  • You want to start without paying.
  • You work on Web, Azure.
  • You also want multi-model apis.
CosmosDB 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 CosmosDB or Turso better?
Neither clearly leads. CosmosDB 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, CosmosDB or Turso?
CosmosDB starts at Free and Turso at Free.
Does CosmosDB or Turso run on more platforms?
CosmosDB runs on Web, Azure. Turso runs on Web.
Can I use CosmosDB for free?
Both have a free tier, so you can try either at no cost before committing.
What is CosmosDB best used for?
CosmosDB is most often used for running a globally distributed multi model database on azure, serving low latency reads and writes from multiple azure regions, storing document, key value and graph data behind a managed service. Of those, running a globally distributed multi model database on azure and serving low latency reads and writes from multiple azure regions are not what Turso is typically brought in for.
What can CosmosDB do that Turso cannot?
CosmosDB covers Global Distribution, Multi-model APIs, Elastic Scaling, Five Consistency Levels. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

CosmosDB: Is there a free tier for Azure Cosmos DB?

Yes, Cosmos DB offers a free tier with 1,000 RU/s of throughput and 25 GB of storage per month for the lifetime of the account, available to new accounts.

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.

CosmosDB: How is Cosmos DB priced after the free tier?

Cosmos DB uses three billing models: provisioned throughput billed per request unit per second, vCore pricing for certain APIs, or serverless consumption pricing where you pay only for requests processed. Reserved capacity offers 20% discount for one year or 30% for three years.

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.

CosmosDB: Can I change my pricing model after choosing one?

No. Once you select a compute pricing model and API, they cannot be changed. This choice is permanent for that database.

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.

CosmosDB: Is there a trial period for Cosmos DB beyond the free tier?

Azure offers a 30-day free trial account for all Azure services. Additionally, Azure AI customers may be eligible for a 90-day free Cosmos DB subscription through the Azure AI Advantage program.

Source
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 CosmosDB

More on Turso

Keep looking

Other head to heads