Softwr

Databases · head to head

OpenSearch vs Turso

OpenSearch logo

OpenSearch

Databases

Open-source search and analytics suite forked from Elasticsearch

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: OpenSearch diverged from Elasticsearch since 7.10, so clients, plugins and features no longer map one to one; 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: OpenSearch covers Full-text search, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which OpenSearch and Turso actually diverge.

Attributes where OpenSearch and Turso differ
AttributeOpenSearchTurso
Pricing modelOpen source, no licence fee; managed services billed separatelyfreemium
PlatformsLinux, Docker, Kubernetes, 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 OpenSearch

  • Full-text search
  • OpenSearch Dashboards
  • Log analytics
  • Vector search

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.

OpenSearch

  • Log and observability storage where an Apache-2.0 licence is a requirementnot Turso
  • Replacing Elasticsearch after the licence change without changing architecturenot Turso
  • Search plus analytics on one cluster rather than two systemsnot Turso

Turso

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

Where each one falls short

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

OpenSearch

  • Diverged from Elasticsearch since 7.10, so clients, plugins and features no longer map one to one
  • Operationally heavy in the way Elasticsearch is: cluster sizing, shard strategy and JVM tuning are ongoing work
  • Smaller ecosystem of third-party tooling than Elasticsearch, which most integrations still target first
  • Overkill for plain application search, where a dedicated search engine is far simpler

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

OpenSearch

Free
  • OpenSearchFree
    • 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 OpenSearch if

  • You need full-text search.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Self-hosted.
  • You also want opensearch dashboards.
OpenSearch 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 OpenSearch or Turso better?
Neither clearly leads. OpenSearch 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, OpenSearch or Turso?
OpenSearch starts at Free and Turso at Free.
Does OpenSearch or Turso run on more platforms?
OpenSearch runs on Linux, Docker, Kubernetes, Self-hosted. Turso runs on Web.
Can I use OpenSearch for free?
Both have a free tier, so you can try either at no cost before committing.
What is OpenSearch best used for?
OpenSearch is most often used for log and observability storage where an apache-2.0 licence is a requirement, replacing elasticsearch after the licence change without changing architecture, search plus analytics on one cluster rather than two systems. Of those, log and observability storage where an apache-2.0 licence is a requirement and replacing elasticsearch after the licence change without changing architecture are not what Turso is typically brought in for.
What can OpenSearch do that Turso cannot?
OpenSearch covers Full-text search, OpenSearch Dashboards, Log analytics, Vector search. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

OpenSearch: Is OpenSearch free?

Yes, Apache 2.0 licensed under the Linux Foundation. Amazon OpenSearch Service is a paid managed option.

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.

OpenSearch: Why does OpenSearch exist?

Elastic moved Elasticsearch off the Apache 2.0 licence in 2021. AWS forked the last Apache-licensed version, and the project now sits under the Linux Foundation.

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.

OpenSearch: Is OpenSearch compatible with Elasticsearch?

It was at the 7.10 fork point. Both have developed independently since, so compatibility weakens with every release and should be verified for the features you use.

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 OpenSearch

More on Turso

Keep looking

Other head to heads