Softwr

Cloud · head to head

Infracost vs Semgrep

Infracost logo

Infracost

Cloud

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

From
Free
Rated
-
Full reviewWebsite
Semgrep logo

Semgrep

Cybersecurity

Open-source static analysis tool for finding security bugs and enforcing code standards.

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.; Semgrep free tier caps out at 10 contributors and 10 repositories.
  • They diverge on capability: Infracost covers Pull request cost diffs, Semgrep covers Static code scanning.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Infracost and Semgrep actually diverge.

Attributes where Infracost and Semgrep differ
AttributeInfracostSemgrep
Pricing modelFree open source tool, then per month by run volumefreemium
PlatformsWeb, macOS, Linux, Windows, Dockerweb, api, linux, mac, windows
CategoryCloudCybersecurity

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 Semgrep

  • Static code scanning
  • Supply chain scanning
  • Secrets detection
  • Cross-file analysis
  • AI-powered triage and remediation
  • CI/CD integration

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 Semgrep
  • Platform groups enforcing tagging so cloud spend can be attributed to a team at allnot Semgrep
  • Organisations adopting FinOps practice without buying a full cloud management platformnot Semgrep
  • Engineers who want a cost figure in the editor while writing the Terraformnot Semgrep

Semgrep

  • Scanning code for security vulnerabilities in CI/CDnot Infracost
  • Detecting vulnerable open-source dependenciesnot Infracost
  • Finding hardcoded secrets before code shipsnot Infracost
  • Enforcing custom code standards with rule setsnot Infracost
  • Prioritizing findings with AI-assisted triagenot 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.

Semgrep

  • Free tier caps out at 10 contributors and 10 repositories.
  • Secrets scanning is priced as a separate module ($15/contributor) from Code and Supply Chain.
  • Self-managed repositories and custom CI/CD require the Enterprise tier.
  • AI credits are limited per tier and additional usage requires upgrading.

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

Semgrep

Free
  • FreeFree
    • Up to 10 contributors
    • Code and Supply Chain scanning
    • 60 AI credits total
  • Teams$30/month
    • Code, Supply Chain, or Secrets scanning per contributor
    • Pro rules
    • AI-powered triage and remediation
  • Enterprise$undefined/month
    • On-prem support
    • Custom CI/CD
    • 50 AI credits per developer/month

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 Semgrep if

  • You need static code scanning.
  • You want to start without paying.
  • You work on web, api, linux, mac, windows.
  • You also want supply chain scanning.
Semgrep review

Questions people ask

Is Infracost or Semgrep better?
Neither clearly leads. Infracost starts at Free and Semgrep at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Infracost or Semgrep?
Infracost starts at Free and Semgrep at Free.
Does Infracost or Semgrep run on more platforms?
Infracost runs on Web, macOS, Linux, Windows, Docker. Semgrep runs on web, api, linux, mac, windows.
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 Semgrep is typically brought in for.
What can Infracost do that Semgrep cannot?
Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies. Semgrep covers Static code scanning, Supply chain scanning, Secrets detection, Cross-file analysis.

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.

Semgrep: What does Semgrep cost?

The Free edition covers up to 10 contributors; Teams starts at $30/contributor/month for Code scanning (Supply Chain also $30, Secrets $15); Enterprise is custom-priced.

Source
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.

Semgrep: Is there a free plan, and what are its limits?

Yes, the Free edition supports up to 10 contributors and 10 repositories with Code and Supply Chain scanning plus 60 AI credits total.

Source
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.

Semgrep: How is usage metered?

Pricing is per contributor, defined as someone who made at least one commit to a scanned private repository in the past 90 days.

Source
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.

Semgrep: Is there special pricing for startups?

Yes, Semgrep offers special startup pricing upon request for early-stage companies.

Source
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 Semgrep

Keep looking

Other head to heads