Softwr

Developer Tools · head to head

Helm vs Turso

H

Helm

Developer Tools

The package manager for Kubernetes

From
Free
Free plan
Yes
Visit HelmFull review
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
Free plan
Yes
Visit TursoFull review

The short version

  • Helm is a Kubernetes package manager, licensed Apache 2.
  • Helm is free; Turso starts at $4.99/mo.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Helm and Turso actually diverge.

Attributes where Helm and Turso differ
AttributeHelmTurso
Pricing modelOpen-sourceFreemium
CategoryDeveloper ToolsDatabases

Identical on both: starting price (Free), free tier (Yes), platforms (Web).

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 Helm

Nothing recorded that Turso does not also cover.

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.

Helm

  • Kubernetes package manager and deployment toolnot Turso

Turso

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

Where each one falls short

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

Helm

  • Contributors must sign commits under the Developer Certificate of Origin to have them accepted, per helm.sh, a process requirement not all Kubernetes tools impose

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

Helm

Free

No published plan breakdown. See the Helm review.

Turso

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

Which should you pick?

Choose Helm if

  • You want to start without paying.
Helm 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 Helm or Turso better?
Neither clearly leads. Helm 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, Helm or Turso?
Helm starts at Free and Turso at Free.
Does Helm or Turso run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Helm for free?
Both have a free tier, so you can try either at no cost before committing.
What is Helm best used for?
Helm is most often used for kubernetes package manager and deployment tool. Of those, kubernetes package manager and deployment tool is not what Turso is typically brought in for.
What can Helm do that Turso cannot?
Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

Helm: How much does Helm cost?

Helm is free and open-source. It is a graduated project in the Cloud Native Computing Foundation (CNCF) with no commercial pricing model.

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.

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.

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 Helm

More on Turso

Keep looking

Other head to heads