Softwr

Cloud · head to head

Infracost vs OpenSearch

Infracost logo

Infracost

Cloud

Cloud cost estimates in pull requests, with governance in the paid tier

From
Free
Rated
-
Full reviewWebsite
OpenSearch logo

OpenSearch

Databases

Open-source search and analytics suite forked from Elasticsearch

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Infracost usage-based resources such as object storage, serverless functions and data transfer have no cost without monthly usage figures supplied by hand, and the documentation warns plainly that engineers otherwise read them as free.; OpenSearch diverged from Elasticsearch since 7.10, so clients, plugins and features no longer map one to one
  • They diverge on capability: Infracost covers Pull request cost diffs, OpenSearch covers Full-text search.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Infracost and OpenSearch actually diverge.

Attributes where Infracost and OpenSearch differ
AttributeInfracostOpenSearch
Pricing modelFree open source tool, then per month by run volumeOpen source, no licence fee; managed services billed separately
PlatformsWeb, macOS, Linux, Windows, DockerLinux, Docker, Kubernetes, Self-hosted
CategoryCloudDatabases

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Infracost

  • Pull request cost diffs
  • Multi-format parsing
  • Apache-2.0 CLI
  • FinOps policies
  • Automated remediation
  • IDE integration

Only in OpenSearch

  • Full-text search
  • OpenSearch Dashboards
  • Log analytics
  • Vector search

What people use each for

The jobs each tool is most often brought in to do.

Infracost

  • Teams that want an expensive infrastructure change questioned at review rather than discovered on an invoicenot OpenSearch
  • Platform groups enforcing tagging so cloud spend can be attributed to a team at allnot OpenSearch
  • Organisations adopting FinOps practice without buying a full cloud management platformnot OpenSearch
  • Engineers who want a cost figure in the editor while writing the Terraformnot OpenSearch

OpenSearch

  • Log and observability storage where an Apache-2.0 licence is a requirementnot Infracost
  • Replacing Elasticsearch after the licence change without changing architecturenot Infracost
  • Search plus analytics on one cluster rather than two systemsnot Infracost

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Infracost

  • Usage-based resources such as object storage, serverless functions and data transfer have no cost without monthly usage figures supplied by hand, and the documentation warns plainly that engineers otherwise read them as free.
  • Splitting production from non-production usage assumptions is not supported in the free usage file, which the docs attribute to a missing project filter, so that separation requires the paid product.
  • The step from 250 to 1,000 dollars a month is large and the Cloud tier includes only ten admin seats, with developer seats charged at a figure that is not published, so the cost for a large organisation cannot be computed from the pricing page.
  • Estimates are list price. Negotiated agreements, committed use discounts and reserved instance economics require SKU-level overrides available only on Enterprise, so the number in the pull request is not the number on the bill.
  • The share of the product covered by the Apache-2.0 licence is shrinking. Checks, automated fixes, policies and agent integrations are all hosted-only, so the permissive licence increasingly protects the estimation engine rather than the product.

OpenSearch

  • Diverged from Elasticsearch since 7.10, so clients, plugins and features no longer map one to one
  • Operationally heavy in the way Elasticsearch is: cluster sizing, shard strategy and JVM tuning are ongoing work
  • Smaller ecosystem of third-party tooling than Elasticsearch, which most integrations still target first
  • Overkill for plain application search, where a dedicated search engine is far simpler

Pricing, plan by plan

Infracost

Free
  • FreeFree
    • 1,000 runs a month
    • Terraform, CloudFormation and CDK estimates
    • Community support
  • Starter$250/month
    • 10,000 runs a month
    • Email support
  • Cloud$1000/month
    • Ten admin seats, developer seats charged separately
    • FinOps policies and cost guardrails
    • Dashboards and audit trails
  • Enterprise$undefined/year
    • SKU-level price overrides for negotiated rates
    • Business unit reporting
    • SSO with SAML group mapping

OpenSearch

Free
  • OpenSearchFree
    • Full functionality
    • Self-hosted
    • No usage limits

Which should you pick?

Choose Infracost if

  • You need pull request cost diffs.
  • You want to start without paying.
  • You work on Web, macOS, Linux, Windows, Docker.
  • You also want multi-format parsing.
Infracost review

Choose OpenSearch if

  • You need full-text search.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Self-hosted.
  • You also want opensearch dashboards.
OpenSearch review

Questions people ask

Is Infracost or OpenSearch better?
Neither clearly leads. Infracost starts at Free and OpenSearch at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Infracost or OpenSearch?
Infracost starts at Free and OpenSearch at Free.
Does Infracost or OpenSearch run on more platforms?
Infracost runs on Web, macOS, Linux, Windows, Docker. OpenSearch runs on Linux, Docker, Kubernetes, Self-hosted.
Can I use Infracost for free?
Both have a free tier, so you can try either at no cost before committing.
What is Infracost best used for?
Infracost is most often used for teams that want an expensive infrastructure change questioned at review rather than discovered on an invoice, platform groups enforcing tagging so cloud spend can be attributed to a team at all, organisations adopting finops practice without buying a full cloud management platform, engineers who want a cost figure in the editor while writing the terraform. Of those, teams that want an expensive infrastructure change questioned at review rather than discovered on an invoice and platform groups enforcing tagging so cloud spend can be attributed to a team at all are not what OpenSearch is typically brought in for.
What can Infracost do that OpenSearch cannot?
Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies. OpenSearch covers Full-text search, OpenSearch Dashboards, Log analytics, Vector search.

Answered from the vendors’ own pages

Infracost: Is the open source version genuinely useful on its own?

Yes, for estimation. It parses your definitions and produces breakdowns and diffs locally. What it does not do is comment on pull requests, enforce policy or report across an organisation, all of which are hosted-only.

OpenSearch: Is OpenSearch free?

Yes, Apache 2.0 licensed under the Linux Foundation. Amazon OpenSearch Service is a paid managed option.

Infracost: Will the estimate match my cloud bill?

No. It is list price. Committed use discounts, enterprise agreements and reserved instances need SKU-level overrides that sit in the Enterprise tier.

OpenSearch: Why does OpenSearch exist?

Elastic moved Elasticsearch off the Apache 2.0 licence in 2021. AWS forked the last Apache-licensed version, and the project now sits under the Linux Foundation.

Infracost: Why do my S3 and Lambda resources show no cost?

Usage-based resources need monthly usage values supplied in a usage file or defined centrally. Without them they estimate at zero, which is the documented behaviour and the most common way the tool misleads.

OpenSearch: Is OpenSearch compatible with Elasticsearch?

It was at the 7.10 fork point. Both have developed independently since, so compatibility weakens with every release and should be verified for the features you use.

Infracost: Has the licence ever changed?

No. The command line tool has been Apache 2.0 throughout, with no Business Source or AGPL episode, which is unusual in this category.

Infracost: What is a run?

Not defined on the public pricing page, and the run allowance is what separates the free and Starter tiers, so establish the definition before choosing between them.

Share

Related pages

More on Infracost

More on OpenSearch

Keep looking

Other head to heads