Repo Compare › Search engines

Elasticsearch vs OpenSearch vs Meilisearch

A side-by-side look at how actively Elasticsearch, OpenSearch and Meilisearch are developed on GitHub — popularity, contributor base, commit activity and how quickly issues and pull requests move.

What the numbers say

Head-to-head

Snapshot taken 30 September 2026.

MetricElasticsearch
Active
OpenSearch
Slowing
Meilisearch
Active
Stars78k14k59k
Forks26k3.0k2.7k
Contributors2.6k2.2k259
Commits, last 52 weeks14k1.5k2.0k
Open issues4.8k2.5k244
Open pull requests1.3k68274
Closed / merged PRs111k14k3.1k
Watchers2.6k186299
Last push30 Sep 202630 Sep 202630 Sep 2026
Latest releasev9.5.4 (Sep 2026)3.9.0 (Sep 2026)v1.54.2 (Sep 2026)
Main languageJavaJavaRust
LicenceNot detected by GitHubApache-2.0Not detected by GitHub
CreatedFeb 2010Jan 2021Apr 2018

The wide bar is that repository’s share of the largest value in its own row — half the length means half the number. The thin gauge beneath it is the same row rescaled from its smallest value to its largest, which makes a close gap such as 61k against 59k visible; on that gauge the row’s lowest value always sits at zero however big it is, so read it as a spread and never as a quantity. Bars compare repositories with each other and never one metric against another. Colour identifies the repository, matching the dot beside its name. On the two issue rows a longer bar means more open work, which is usually the opposite of better. The highlighted cell is the highest value in a row. “Active / Slowing / Dormant” is a simple heuristic from how recently code was pushed and open issues per star — a starting point, not a verdict. Stars measure popularity, not quality.

Open these in the live comparer →

Related comparisons