Softwr

Databases · head to head

MariaDB vs Turso

MariaDB logo

MariaDB

Databases

The open source relational database for the enterprise

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: MariaDB jSON support using text fields rather than native binary type; lacks MySQL's JSON syntax and functions; 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: MariaDB covers MySQL Compatibility, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which MariaDB and Turso actually diverge.

Attributes where MariaDB and Turso differ
AttributeMariaDBTurso
Pricing modelUnknownfreemium
PlatformsLinux, Unix, Windows, macOSWeb
Founded2009Unknown

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 MariaDB

  • MySQL Compatibility
  • Aria Storage Engine
  • ColumnStore
  • Galera Cluster
  • MaxScale
  • Spider Engine
  • Temporal Tables
  • phpMyAdmin

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.

MariaDB

  • Transaction processingnot Turso
  • Data storagenot Turso
  • Application backendnot Turso
  • Reportingnot Turso
  • Data analyticsnot Turso

Turso

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

Where each one falls short

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

MariaDB

  • JSON support using text fields rather than native binary type; lacks MySQL's JSON syntax and functions
  • Galera Cluster maximum performance limited to the slowest node in cluster
  • InnoDB tables limited to 1,017 columns and 64 secondary indexes
  • Transaction size limits in Galera (128K rows and 2GB by default)
  • Less strict SQL type checking than PostgreSQL; allows implicit conversions

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

MariaDB

Free

No published plan breakdown. See the MariaDB review.

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

  • You need mysql compatibility.
  • You want to start without paying.
  • You work on Linux, Unix, Windows, macOS.
  • You also want aria storage engine.
MariaDB 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 MariaDB or Turso better?
Neither clearly leads. MariaDB 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, MariaDB or Turso?
MariaDB starts at Free and Turso at Free.
Does MariaDB or Turso run on more platforms?
MariaDB runs on Linux, Unix, Windows, macOS. Turso runs on Web.
Can I use MariaDB for free?
Both have a free tier, so you can try either at no cost before committing.
What is MariaDB best used for?
MariaDB is most often used for transaction processing, data storage, application backend, reporting. Of those, transaction processing and data storage are not what Turso is typically brought in for.
What can MariaDB do that Turso cannot?
MariaDB covers MySQL Compatibility, Aria Storage Engine, ColumnStore, Galera Cluster. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

MariaDB: Is MariaDB completely free and open source?

Yes. MariaDB Server is licensed under GPLv2 and guaranteed to remain perpetually free and open source, independent of any commercial entities.

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.

MariaDB: Is MariaDB backward compatible with MySQL?

Yes. MariaDB was designed as a drop-in replacement for MySQL. Every application, driver, and configuration that worked with MySQL works with MariaDB without code changes.

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.

MariaDB: What are the storage engine options in MariaDB?

MariaDB supports multiple storage engines including InnoDB (transactional, default), Aria (crash-safe, good for read-heavy workloads), and MyISAM. The Aria engine is faster than InnoDB for certain read-heavy queries and full table scans.

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.

MariaDB: How much does MariaDB cost?

MariaDB Community Server is completely free to download and use. MariaDB offers paid enterprise support and managed cloud services for organizations needing professional support.

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.

MariaDB: Does MariaDB support native JSON storage?

MariaDB stores JSON using text fields (the JSON type is an alias for LONGTEXT), not as a native binary type like MySQL does. JSON support exists but is less sophisticated than MySQL's JSON functions and syntax.

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

MariaDB: What scaling options does MariaDB provide?

MariaDB supports both scaling up (more cores, memory, storage) and scaling out (read replication, Galera Cluster with multi-node replication). However, Galera Cluster performance cannot exceed the slowest node in the cluster.

Source
Share

Related pages

More on MariaDB

More on Turso

Keep looking

Other head to heads