shouldiuse.io

Report

Should I Use Elastic?

elastic.co·Analyzed 14 hours ago··Based on 10 sources

Power insights and outcomes with The Elasticsearch Platform. See into your data and find answers that matter.

Depends

Depends

Buy if you run large-scale search, log, or security data and have engineers to operate it.

Enterprise-grade search, observability, and SIEM — powerful but pricey, opaque, and overkill without real data volume.

Confidence: Medium

4+/5

G2 rating

541 seller reviews

31,262

Companies using it

tracked by TheirStack

2012

Founded

per AWS case study

$429.6M

Funding

per Crunchbase

Value for money2

Opaque usage pricing; recurring cost complaints

Ease of use3

Easy to start; operations-heavy at scale

Feature depth5

Search, observability, SIEM, AI in one stack

Security posture3

Active CVE stream, but transparent handling; CISA-listed

Pros

  • Rated 4+ out of 5 across 541 G2 reviews¹
  • One platform spans search, observability, and security
  • Capterra reviewers call Elasticsearch easy to get started
  • Elastic SIEM is listed by CISA as a federal resource⁶
  • Open detection rules and Security Labs research publicly available

Cons

  • Left open source; license change drove the OpenSearch fork⁷
  • Recent CVE includes arbitrary code execution (CVE-2025-25014)⁵
  • Heavy operational burden; many teams move to lighter engines⁸
  • Costs scale steeply with data volume, per third-party analyses

Gotchas

  • highUsage-based pricing hides real cost; one Reddit user called getting numbers 'bloody difficult'²
  • highMisconfigured Elasticsearch clusters have leaked billions of records; harden defaults and auth
  • mediumLicense changes mean it's no longer fully open source; OpenSearch forked away⁷
  • mediumGuess: migrating off later means full reindexing; plan your exit before committing

Best for

  • Large-scale app and site search
  • Log and metrics observability
  • Security teams wanting an open SIEM
  • Organizations with dedicated ops engineers

Not for

  • Small teams needing simple search — massive overkill
  • Anyone expecting open-source pricing after the license change
  • Teams without engineers to tune and scale clusters
  • Startups that can't absorb surprise usage bills

Pricing

Elastic Cloud

Usage-based, no public flat rate

  • Serverless or classic deployments
  • Pay per resources consumed; scales with data volume

Security

Known CVEs exist (info disclosure, DoS, code execution) plus one third-party supply-chain incident; Elastic runs a transparent product-security program.

  • CVE-2025-25014 — arbitrary code executionDisclosed May 2025; arbitrary code execution vulnerability in Elastic Kibana.⁵
  • CVE-2022-23712 — denial of serviceDenial-of-service vulnerability tracked by NIST for Kibana.
  • CVE-2020-7021 — information disclosureInformation disclosure flaw in Elasticsearch.
  • Salesloft Drift supply-chain incidentElastic published an official update on its exposure to the Salesloft Drift incident.

What users say

G2 reviewers rate Elastic 4+ across 541 reviews and praise its observability and search power, while Reddit threads flag confusing pricing and operational weight.

Alternatives

Compare Elastic with each alternative.

Full analysis

Based on ~25 public sources. Several results concern unrelated firms named 'Elastic' (a credit line at elastic.com, Elastic Path, sewing elastic) and were excluded.

Sources

  1. Elastic Products | G2 seller reviewsg2.com
    review
  2. Why is it so bloody difficult to get pricing information — Redditreddit.com
    review
  3. Official Elastic Cloud pricingelastic.co
    official
  4. Product Security at Elasticelastic.co
    security
  5. Arbitrary Code Execution Vulnerability, CVE-2025-25014nsfocusglobal.com
    security
  6. Elastic SIEM — CISAcisa.gov
    official
  7. Case Study: Elastic's Abandonment of Open Sourceblog.hippoai.org
    news
  8. Elasticsearch Alternatives by Workload — Typesensetypesense.org
    review
  9. Companies that use Elastic (31,262)theirstack.com
    news
  10. How Elastic Built a Serverless Solution — AWS case studyaws.amazon.com
    official

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.

    Save a name to write a comment.

    No comments yet.