Softwr

Databases · head to head

Turso vs Valkey

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
Valkey logo

Valkey

Databases

Open-source in-memory data store forked from Redis

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Valkey younger project, so its track record is short even though the codebase is not
  • They diverge on capability: Turso covers Per-tenant databases, Valkey covers Redis-compatible.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Turso and Valkey actually diverge.

Attributes where Turso and Valkey differ
AttributeTursoValkey
Pricing modelfreemiumOpen source, no licence fee; managed cloud billed separately
PlatformsWebLinux, macOS, Docker, Self-hosted

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 Turso

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

Only in Valkey

  • Redis-compatible
  • BSD licensed
  • Rich data structures
  • Replication and persistence

What people use each for

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

Turso

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

Valkey

  • Continuing on a permissively licensed in-memory store after the Redis licence changenot Turso
  • Caching and session storage where a foundation-governed project is a procurement requirementnot Turso
  • Migrating from Redis without rewriting application codenot Turso

Where each one falls short

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

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.

Valkey

  • Younger project, so its track record is short even though the codebase is not
  • Divergence from Redis grows over time, so compatibility is strongest near the fork point and weakens as both evolve
  • Ecosystem tooling and documentation still frequently assume Redis, leaving translation work

Pricing, plan by plan

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

Valkey

Free
  • ValkeyFree
    • Full functionality
    • Self-hosted
    • No usage limits

Which should you pick?

Choose Turso if

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

Choose Valkey if

  • You need redis-compatible.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Self-hosted.
  • You also want bsd licensed.
Valkey review

Questions people ask

Is Turso or Valkey better?
Neither clearly leads. Turso starts at Free and Valkey at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Turso or Valkey?
Turso starts at Free and Valkey at Free.
Does Turso or Valkey run on more platforms?
Turso runs on Web. Valkey runs on Linux, macOS, Docker, Self-hosted.
Can I use Turso for free?
Both have a free tier, so you can try either at no cost before committing.
What is Turso best used for?
Turso is most often used for multi-tenant saas where each customer gets their own database for real isolation, per-tenant restore and clean deletion, agent or session infrastructure that creates a throwaway database per task and destroys it afterwards, local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returns, embedding a sqlite-compatible engine in a product where the public domain original's closed contribution model is a problem. Of those, multi-tenant saas where each customer gets their own database for real isolation, per-tenant restore and clean deletion and agent or session infrastructure that creates a throwaway database per task and destroys it afterwards are not what Valkey is typically brought in for.
What can Turso do that Valkey cannot?
Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility. Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence.

Answered from the vendors’ own pages

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.

Valkey: Is Valkey free?

Yes, BSD-licensed open source under the Linux Foundation.

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.

Valkey: Why does Valkey exist?

Redis changed its licence away from BSD in 2024. Valkey is the community fork continuing under permissive terms, backed by AWS, Google Cloud and Oracle among others.

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.

Valkey: Can I switch from Redis to Valkey?

At the fork point it is drop-in compatible with existing clients and data. The further both projects move from that point, the more you should verify the specific features you use.

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 Turso

More on Valkey

Keep looking

Other head to heads