Softwr

Databases · head to head

Meilisearch vs Turso

Meilisearch logo

Meilisearch

Databases

Fast open-source search engine built for typo tolerance

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: Meilisearch not built for log analytics or aggregation-heavy workloads, which is where Elasticsearch remains the answer; 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: Meilisearch covers Typo tolerance, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Meilisearch and Turso actually diverge.

Attributes where Meilisearch and Turso differ
AttributeMeilisearchTurso
Pricing modelOpen source, no licence fee; managed cloud billed separatelyfreemium
PlatformsLinux, macOS, Windows, Docker, Self-hostedWeb

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 Meilisearch

  • Typo tolerance
  • Search as you type
  • Faceted search
  • Simple API

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.

Meilisearch

  • Adding product or content search to an application without running Elasticsearchnot Turso
  • Search-as-you-type interfaces where latency is visible to the usernot Turso
  • Replacing SQL LIKE queries that cannot handle typos or rankingnot Turso

Turso

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

Where each one falls short

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

Meilisearch

  • Not built for log analytics or aggregation-heavy workloads, which is where Elasticsearch remains the answer
  • Scaling across many nodes is less mature than the older engines it competes with
  • Memory use grows with index size, and large datasets need real capacity planning

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

Meilisearch

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

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

  • You need typo tolerance.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Docker, Self-hosted.
  • You also want search as you type.
Meilisearch 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 Meilisearch or Turso better?
Neither clearly leads. Meilisearch 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, Meilisearch or Turso?
Meilisearch starts at Free and Turso at Free.
Does Meilisearch or Turso run on more platforms?
Meilisearch runs on Linux, macOS, Windows, Docker, Self-hosted. Turso runs on Web.
Can I use Meilisearch for free?
Both have a free tier, so you can try either at no cost before committing.
What is Meilisearch best used for?
Meilisearch is most often used for adding product or content search to an application without running elasticsearch, search-as-you-type interfaces where latency is visible to the user, replacing sql like queries that cannot handle typos or ranking. Of those, adding product or content search to an application without running elasticsearch and search-as-you-type interfaces where latency is visible to the user are not what Turso is typically brought in for.
What can Meilisearch do that Turso cannot?
Meilisearch covers Typo tolerance, Search as you type, Faceted search, Simple API. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

Meilisearch: Is Meilisearch free?

The engine is open source and free to self-host. Meilisearch Cloud is a paid 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.

Meilisearch: Meilisearch or Elasticsearch?

Meilisearch is far simpler for application search and works well by default. Elasticsearch is the choice when you also need log analytics and heavy aggregations.

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.

Meilisearch: Does it handle typos automatically?

Yes. Typo tolerance is on by default rather than something you configure.

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 Meilisearch

More on Turso

Keep looking

Other head to heads