Softwr

Databases · head to head

NATS vs Turso

NATS logo

NATS

Databases

High-performance messaging system for cloud-native applications

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: NATS core NATS has no persistence at all, so messages are lost if no subscriber is listening; 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: NATS covers Very low latency, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which NATS and Turso actually diverge.

Attributes where NATS and Turso differ
AttributeNATSTurso
Pricing modelOpen source, no licence feefreemium
PlatformsLinux, macOS, Windows, Docker, KubernetesWeb

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 NATS

  • Very low latency
  • JetStream
  • Single binary
  • Request-reply

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.

NATS

  • Service-to-service messaging where latency is the binding constraintnot Turso
  • Edge and IoT messaging where a lightweight broker mattersnot Turso
  • Replacing a heavier broker when the workload does not need its guaranteesnot Turso

Turso

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

Where each one falls short

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

NATS

  • Core NATS has no persistence at all, so messages are lost if no subscriber is listening
  • JetStream adds the durability but also the operational complexity NATS is chosen to avoid
  • A much smaller ecosystem than Kafka or RabbitMQ, with fewer connectors and integrations
  • Fewer people know it, so hiring and existing organisational knowledge favour the alternatives

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

NATS

Free
  • NATSFree
    • Full functionality
    • No usage limits
    • Community support

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

  • You need very low latency.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Docker, Kubernetes.
  • You also want jetstream.
NATS 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 NATS or Turso better?
Neither clearly leads. NATS 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, NATS or Turso?
NATS starts at Free and Turso at Free.
Does NATS or Turso run on more platforms?
NATS runs on Linux, macOS, Windows, Docker, Kubernetes. Turso runs on Web.
Can I use NATS for free?
Both have a free tier, so you can try either at no cost before committing.
What is NATS best used for?
NATS is most often used for service-to-service messaging where latency is the binding constraint, edge and iot messaging where a lightweight broker matters, replacing a heavier broker when the workload does not need its guarantees. Of those, service-to-service messaging where latency is the binding constraint and edge and iot messaging where a lightweight broker matters are not what Turso is typically brought in for.
What can NATS do that Turso cannot?
NATS covers Very low latency, JetStream, Single binary, Request-reply. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

NATS: Is NATS free?

Yes, open source and CNCF-graduated. Synadia sells a managed service.

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.

NATS: Does NATS persist messages?

Core NATS does not — it is fire-and-forget. JetStream adds persistence, streaming and replay when you need them.

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.

NATS: NATS or Kafka?

NATS is far lighter and lower latency, and much simpler to run. Kafka is the answer when you need a durable replayable log and a large connector ecosystem.

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 NATS

More on Turso

Keep looking

Other head to heads