We migrated from Elasticsearch to OpenSearch after the licensing changes, and it's been a seamless transition. The familiar, powerful RESTful APIs are all there, making it perfect for our internal search and analytics dashboards. Knowing it's truly open-source under Apache 2.0 gives us long-term confidence, and the active community forums have been helpful for troubleshooting.
As a developer who was concerned about licensing changes in other search platforms, OpenSearch has been a fantastic find. It's as powerful as the engine it's based on, with the crucial benefit of a genuine open-source Apache 2.0 license. The setup was straightforward, and the familiar RESTful APIs made migrating our existing search and analytics features incredibly smooth.
After migrating from Elasticsearch to OpenSearch for our internal analytics platform, we've been very satisfied. The API compatibility made the transition nearly seamless, and the Apache 2.0 licensing gives us peace of mind for future scaling. The performance has been reliable under heavy query loads, and the active community provides helpful resources when needed.
OpenSearch delivers as a powerful, scalable search and analytics engine. The open-source, Apache 2.0-licensed core is a major advantage, providing a robust and free alternative. However, the initial set up and configuration has a steep learning curve, and the early 1.x releases had some stability and documentation gaps. The move from Elastic's codebase has been a bit of a bumpy road.
We migrated from Elasticsearch to OpenSearch after licensing changes and have been pleasantly surprised. The RESTful APIs are identical to what we were using before, so our existing search applications required minimal adjustments. It handles our analytics workloads efficiently, and being Apache 2.0 licensed gives us long-term peace of mind.
As someone who migrated from Elasticsearch, I appreciate the Apache 2.0 license and the commitment to staying truly open source. The REST APIs are familiar and work well for basic search and analytics. However, the ecosystem of plugins and integrations still lags behind Elastic's, and some advanced features I relied on are missing or less polished. For new projects it's worth considering, but existing Elasticsearch users should plan their migration carefully.
As a developer migrating from Elasticsearch, OpenSearch has been a seamless and excellent choice. The familiar RESTful APIs made integration straightforward, and its Apache 2.0 license gives us the freedom to use and modify it without legal concerns. It's proven stable and performant for our application logs and product search features.
As a developer building a search-heavy application, OpenSearch has been a game-changer. It's easy to deploy via Docker and the APIs are well-documented, making integration straightforward. The fact that it's fully open source under Apache 2.0 gives us peace of mind for long-term use without vendor lock-in, and the performance has been rock-solid with our mid-sized dataset.
OpenSearch delivers on its promise as a capable open-source search and analytics engine, with the Apache 2.0 license being a major plus for our team. However, we hit several rough edges with documentation and plugin compatibility that slowed our rollout. The core search functionality is solid, but the ecosystem feels young compared to its predecessor.
As a developer, I appreciate the Apache 2.0 license and the freedom it provides, which is a huge win over Elasticsearch's recent changes. The core search and analytics APIs are solid and perform well for our basic use cases. However, finding compatible plugins and up-to-date client libraries can be a frustrating scavenger hunt compared to the mature Elastic ecosystem.
Based on 17 reviews
OpenSearch is an open source search engine software project that is based on Elasticsearch and Apache 2.0 licensed. It provides …
Back to Product