elastic/elasticsearch

Choose this fork only if Chinese localization or a legacy frozen branch matters more than staying current. For most adopters, upstream Elasticsearch is the safer choice because this fork is stale and materially behind.

Choose this fork only if you already depend on its custom behavior and are prepared to maintain a very old, highly divergent Elasticsearch branch yourself. For most adopters, upstream Elasticsearch is the better choice because it is active, modern, and much lower risk.

Prefer this fork only if you need its specific ES|QL/vector/custom build changes and are prepared to own a stale, highly divergent Elasticsearch branch. If you want current features, active fixes, or lower operational risk, upstream is the better choice.

Prefer this fork only if you need a legacy Elasticsearch codebase and are willing to own substantial divergence. For any new search or analytics deployment, upstream Elasticsearch is the better choice.

Choose this fork only if you need its existing custom ESQL/vector/build changes or must stay on this historical snapshot. If you want current Elasticsearch capabilities, security fixes, and upstream support, upstream is the better choice.

Prefer this fork only for legacy analyzer-centric use cases, especially Chinese text analysis. For any new search platform work, upstream Elasticsearch is the better default because this fork is extremely stale and materially diverged.

Choose the fork only if grouping support on an older Elasticsearch base is the goal. For new production deployments, upstream Elasticsearch is the safer default because this fork is far behind and likely missing major modern capabilities.

Prefer this fork only if you specifically need its custom ES|QL/performance/CI work and can accept substantial upstream lag. If you want current Elasticsearch capabilities, fixes, and supportability, upstream is the better choice.

Choose this fork only if you need its downstream customizations and can absorb long-term maintenance debt. If you want current Elasticsearch features, security fixes, and low-friction upgrades, upstream is the safer default.

Choose this fork only if you need a deeply customized Elasticsearch codebase and are willing to maintain a large divergence yourself. For most adopters, upstream is the better choice because this fork is stale and likely missing many later fixes and capabilities.

Choose the fork only if you need its legacy baseline or existing custom changes. If you want current Elasticsearch features, support, and lower operational risk, upstream is the better choice.

Prefer this fork only if you are tied to its legacy behavior. For any new deployment, upstream Elasticsearch is vastly more capable, better maintained, and far lower risk.

Choose this fork only if you need legacy Elasticsearch behavior or existing downstream patches. For new deployments or feature-driven work, upstream Elastic is the safer default because this fork appears stale and materially behind current Elasticsearch.

Prefer upstream unless you specifically need this fork’s custom ES|QL/doc/test behavior and are prepared to own a large merge burden. It is not a good choice for adopters who want current Elasticsearch features, fixes, or low-maintenance upgrades.

Prefer upstream unless you specifically need this fork's ES|QL/vector/doc/build customizations and are willing to own maintenance. For most adopters, the two-year staleness and large divergence outweigh any upside.

Prefer the upstream project if you need modern search, vector, ML, or ES|QL capabilities. Prefer this fork only if your goal is to keep working on an old customized Elasticsearch line and you can absorb the maintenance cost.

Choose this fork only if you need its legacy/custom behavior. For most adopters, current upstream Elasticsearch is the safer choice because this fork is materially behind and highly divergent.

Prefer upstream unless you specifically need legacy Elasticsearch behavior. This fork looks like a stale, highly divergent snapshot with a few targeted fixes, so it is only attractive for compatibility-bound adopters who can accept missing modern features and ongoing maintenance burden.

Choose this fork only if you specifically want its ES|QL-heavy customization, entitlement/runtime changes, or internal build workflow and can tolerate being materially behind upstream. If you want the broadest upstream feature set, freshest fixes, and lower maintenance risk, upstream Elasticsearch is the safer default.