Softwr

Databases · head to head

OpenSearch vs Valkey

OpenSearch logo

OpenSearch

Databases

Open-source search and analytics suite forked from Elasticsearch

From
Free
Rated
-
Valkey logo

Valkey

Databases

Open-source in-memory data store forked from Redis

From
Free
Rated
-

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; Valkey younger project, so its track record is short even though the codebase is not
  • They diverge on capability: OpenSearch covers Full-text search, Valkey covers Redis-compatible.

Where they differ

Only the attributes on which OpenSearch and Valkey actually diverge.

Attributes where OpenSearch and Valkey differ
AttributeOpenSearchValkey
Pricing modelOpen source, no licence fee; managed services billed separatelyOpen source, no licence fee; managed cloud billed separately
PlatformsLinux, Docker, Kubernetes, Self-hostedLinux, macOS, Docker, Self-hosted

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 Valkey

  • Redis-compatible
  • BSD licensed
  • Rich data structures
  • Replication and persistence

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 Valkey
  • Replacing Elasticsearch after the licence change without changing architecturenot Valkey
  • Search plus analytics on one cluster rather than two systemsnot Valkey

Valkey

  • Continuing on a permissively licensed in-memory store after the Redis licence changenot OpenSearch
  • Caching and session storage where a foundation-governed project is a procurement requirementnot OpenSearch
  • Migrating from Redis without rewriting application codenot 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

Valkey

  • Younger project, so its track record is short even though the codebase is not
  • Divergence from Redis grows over time, so compatibility is strongest near the fork point and weakens as both evolve
  • Ecosystem tooling and documentation still frequently assume Redis, leaving translation work

Pricing, plan by plan

OpenSearch

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

Valkey

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

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.

Choose Valkey if

  • You need redis-compatible.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Self-hosted.
  • You also want bsd licensed.

Questions people ask

Is OpenSearch or Valkey better?
Neither clearly leads. OpenSearch starts at Free and Valkey at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, OpenSearch or Valkey?
OpenSearch starts at Free and Valkey at Free.
Does OpenSearch or Valkey run on more platforms?
OpenSearch runs on Linux, Docker, Kubernetes, Self-hosted. Valkey runs on Linux, macOS, Docker, Self-hosted.
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 Valkey is typically brought in for.
What can OpenSearch do that Valkey cannot?
OpenSearch covers Full-text search, OpenSearch Dashboards, Log analytics, Vector search. Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence.

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.

Valkey: Is Valkey free?

Yes, BSD-licensed open source under the Linux Foundation.

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.

Valkey: Why does Valkey exist?

Redis changed its licence away from BSD in 2024. Valkey is the community fork continuing under permissive terms, backed by AWS, Google Cloud and Oracle among others.

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.

Valkey: Can I switch from Redis to Valkey?

At the fork point it is drop-in compatible with existing clients and data. The further both projects move from that point, the more you should verify the specific features you use.

Share

Related pages

Other head to heads