// the take
OpenSearch is the Elasticsearch fork maintained by AWS and the Linux Foundation, a distributed search and analytics engine written in Java. It's for teams that need a self-hosted or AWS-managed search/log-analytics backend without Elastic's licensing terms.
Genuinely Apache 2.0 licensed with no surprise license changes, backed by real infrastructure (Jenkins gradle-check, BWC version testing, benchmark suite with JMH harnesses for internals like translog and routing allocation). The build tooling (custom Gradle plugins for distribution, JDK download, Docker) shows a mature, battle-tested release pipeline, not a toy project. Active fork with its own roadmap features like segment replication and searchable snapshots diverging from upstream ES.
Massive monorepo with a build system that's a project in itself (buildSrc alone has dozens of custom Gradle plugins) — expect a slow, resource-heavy local dev setup. README is pure boilerplate with zero technical content, you have to go digging through docs.opensearch.org for anything useful. As a fork it will always lag behind Elasticsearch on newer Lucene features and faces the perpetual question of whether AWS's governance model attracts outside contributors versus just AWS employees doing their day jobs.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →