$0
Core license
Apache 2.0, self-hosted
Report
Should I Use OpenSearch?
OpenSearch is a community-driven, Apache 2.0-licensed open source search and analytics suite that makes it easy to ingest, search, visualize, and analyze data.
Depends
DependsBuy it if you run high-volume log analytics or want a self-hosted, open-source Elasticsearch alternative.
Powerful open-source search/analytics for high-volume workloads — overkill and pricey for simple search needs.
Confidence: Medium
$19/mo
Managed price floor
DigitalOcean single node
14,100
Companies using it
per TheirStack data
Linux Foundation
Governance
AWS donated it in Sept 2024
Value for money
2
Managed costs draw repeated user complaints
Ease of use
4
G2 users praise ease of use
Feature depth
5
Search, analytics, dashboards, security, ML in one suite
Security posture
3
Active CVE flow, transparent patching process
Pros
Cons
Gotchas
- highAWS Serverless bills a 2-OCU minimum around the clock; small workloads report ~$350+/month⁶
- highSecurity plugin ships demo certificates — replace them before production
- mediumScanners kept flagging Log4j CVEs even after upgrading to 3.6.012
- mediumG2 reviewers note hosted OpenSearch can cost more than competitors⁵
Best for
- High-volume log analytics
- Teams wanting an open-source Elasticsearch alternative
- AWS-centric search workloads
- Security analytics / SIEM builders
Not for
- Small apps needing simple site search — badly overkill
- Teams with no ops bandwidth to run clusters
- Budget buyers on AWS Serverless with spiky, small workloads
- Latency-critical search where Elastic claims a 40–140% speed edge
Companies that use it
- LINE
- Adaptavist
Pricing
Self-hosted
$0
- Apache 2.0, full feature set
- You run and scale the cluster
DigitalOcean managed
from $19/mo
- Single-node start
- Managed ops
AWS Serverless
OCU-based; small workloads often $350+/mo
- Pay per OCU-hour
- Storage ~$0.02/GB-month
Security
Active open-source project with published CVEs and a clear disclosure process; recurring Log4j scanner flags and a recent DoS and SSRF issue, both patched.
- CVE-2025-9624 — Denial of ServiceVulnerability allows attackers to cause denial of service in OpenSearch.11
- CVE-2026-18952 — SSRF in Security AnalyticsServer-side request forgery vulnerability in OpenSearch Security Analytics.
- Recurring Log4j scanner flagsClusters on 3.6.0 still flagged for Log4j vulnerability CVE-2026-34478 by scanners.12
What users say
Users praise its scale and ease of use but frequently complain about managed-hosting costs and polish versus Elasticsearch.
“opensearch can handle way more than 100K per min”
“Everything in OpenSearch just feels more half-bak”
“OpenSearch is notoriously expensive.”
Alternatives
Compare OpenSearch with each alternative.
Elasticsearch
Original project; vendor claims 40–140% better performance
OpenSearch vs ElasticsearchMeilisearch
Simpler, lighter site search for small apps
OpenSearch vs MeilisearchApache Solr
Mature Apache search, common alongside Solr stacks
OpenSearch vs Apache SolrSematext
Hosted logging and search with less ops
OpenSearch vs SematextFull analysis
Based on 30+ public sources including Reddit, G2, HN, AWS docs, vendor pages, and security trackers.
Sources
review
- OpenSearch is notoriously expensive (Hacker News)news.ycombinator.comreview
- OpenSearch Reviews — G2g2.comreview
review
review
- OpenSearch official siteopensearch.orgofficial
- OpenSearch vs Elasticsearch (Elastic)elastic.coofficial
- DigitalOcean Managed OpenSearch Pricingdocs.digitalocean.comofficial
- Linux Foundation Announces OpenSearch Software Foundationlinuxfoundation.orgnews
- CVE-2025-9624 (NVD)nvd.nist.govsecurity
- OpenSearch 3.6.0 Log4j flag (forum)forum.opensearch.orgsecurity
Rate this review
Anonymous. You can change your vote.
Loading votes…
Ask a follow-up
Ask if a use case fits. Answers stay inside this report and its sources.
Comments
One queue. No replies. Give a display name first. Limit: 7 comments per day.
No comments yet.