Softwr

Databases · head to head

Turso vs VerneMQ

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

VerneMQ

Databases

Erlang MQTT broker whose source is Apache 2.0 but whose official binaries need a paid subscription

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.; VerneMQ the official binaries and Docker images are not Apache 2.0 but sit under a EULA requiring a yearly commercial subscription, a distinction easy to miss and awkward to discover during a licence audit.
  • They diverge on capability: Turso covers Per-tenant databases, VerneMQ covers Erlang/OTP clustering.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Turso and VerneMQ actually diverge.

Attributes where Turso and VerneMQ differ
AttributeTursoVerneMQ
Pricing modelfreemiumquote
PlatformsWebLinux, Docker, macOS, Kubernetes

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 VerneMQ

  • Erlang/OTP clustering
  • MQTT 5.0 support
  • Plugin system
  • Backpressure handling
  • Bridge support
  • Metrics export
  • MQTT over WebSockets
  • Pluggable auth backends

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 VerneMQ
  • Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot VerneMQ
  • Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot VerneMQ
  • Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot VerneMQ

VerneMQ

  • An industrial operator that wants an MQTT broker with predictable memory behaviour and no data integration features it will not usenot Turso
  • A team building from source to stay strictly under Apache 2.0 terms with no vendor licence entanglementnot Turso
  • A deployment needing custom authentication logic implemented as a plugin in Lua or over a webhooknot Turso
  • An organisation that wants a broker maintained by a small European company rather than by a vendor that keeps changing licencesnot 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.

VerneMQ

  • The official binaries and Docker images are not Apache 2.0 but sit under a EULA requiring a yearly commercial subscription, a distinction easy to miss and awkward to discover during a licence audit.
  • Octavo Labs is a very small company, so support depth, response times and the bus factor on the codebase are materially thinner than at HiveMQ or EMQ.
  • There is no data integration or rule engine layer, so routing messages into a database means writing and operating your own consumer service.
  • Operating an Erlang cluster requires runtime knowledge that most teams do not have and will use for nothing else in their stack.
  • There is no vendor-managed cloud offering, so every deployment is self-operated with the infrastructure and on-call cost that implies.

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

VerneMQ

Free
  • Source buildFree
    • Apache 2.0 licensed source from GitHub
    • Full clustering and plugin capability
    • You compile and package it yourself
  • Binary packages and Docker images$undefined/year
    • Covered by the VerneMQ EULA, not Apache 2.0
    • Yearly usage subscription expected for commercial use
    • Official builds and Docker images
  • Commercial support$undefined/year
    • Evaluation, customisation and operations assistance
    • Custom development
    • Long-term maintenance agreements

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

  • You need erlang/otp clustering.
  • You want to start without paying.
  • You work on Linux, Docker, macOS, Kubernetes.
  • You also want mqtt 5.0 support.
VerneMQ review

Questions people ask

Is Turso or VerneMQ better?
Neither clearly leads. Turso starts at Free and VerneMQ at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Turso or VerneMQ?
Turso starts at Free and VerneMQ at Free.
Does Turso or VerneMQ run on more platforms?
Turso runs on Web. VerneMQ runs on Linux, Docker, macOS, Kubernetes.
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 VerneMQ is typically brought in for.
What can Turso do that VerneMQ cannot?
Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility. VerneMQ covers Erlang/OTP clustering, MQTT 5.0 support, Plugin system, Backpressure handling.

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.

VerneMQ: Is VerneMQ free?

The source is Apache 2.0 and free. The official binary packages and Docker images are covered by a separate EULA that expects a yearly fee for commercial use.

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.

VerneMQ: Is the project still maintained?

Yes. Octavo Labs AG in Zurich continues to publish 2.x releases, most recently in 2026.

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.

VerneMQ: Does it have a managed cloud?

No. Every deployment is self-hosted, with commercial support available from Octavo Labs.

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.

VerneMQ: How does it compare to EMQX?

Narrower in features and without a rule engine, but with a simpler licence story for source builds after EMQX moved to BSL.

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 VerneMQ

Keep looking

Other head to heads