Softwr

Cloud · head to head

Infracost vs Sigstore

Infracost logo

Infracost

Cloud

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

From
Free
Rated
-
Full reviewWebsite
Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

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.; Sigstore the security model depends on somebody watching the log. The documentation states that compromise of an identity provider or of Fulcio itself is detectable only if third parties monitor the transparency log, the monitoring tool is a community-tier rather than core project, and almost no consumer runs one.
  • They diverge on capability: Infracost covers Pull request cost diffs, Sigstore covers Fulcio.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Infracost and Sigstore actually diverge.

Attributes where Infracost and Sigstore differ
AttributeInfracostSigstore
Pricing modelFree open source tool, then per month by run volumeOpen source, public instance free to use
PlatformsWeb, macOS, Linux, Windows, DockerWeb, Linux, macOS, Windows, Self-hosted
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 Sigstore

  • Fulcio
  • Rekor
  • Keyless signing
  • Multi-language clients
  • Timestamp authority
  • Neutral governance

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

Sigstore

  • Open source projects signing releases without running a certificate authoritynot Infracost
  • Organisations meeting a signed-artifact requirement without buying a signing productnot Infracost
  • Publishing provenance that a consumer can verify independently of younot Infracost
  • Self-hosting the same components where a public log is unacceptablenot 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.

Sigstore

  • The security model depends on somebody watching the log. The documentation states that compromise of an identity provider or of Fulcio itself is detectable only if third parties monitor the transparency log, the monitoring tool is a community-tier rather than core project, and almost no consumer runs one.
  • It is a 99.5 percent objective with no service level agreement, which permits several hours of downtime a month and offers no remedy. A pipeline that signs on every build has taken a hard dependency on a free service with no contract behind it.
  • Log scale is a live engineering problem rather than a theoretical one. The active shard holds billions of entries, the log has already been sharded twice, and sharding version 1 requires stopping traffic, which is why a replacement was built.
  • Ten-minute certificates make trust depend on log availability. Verifying an older signature relies on the log entry proving it was made inside that window, so a lost or unreachable entry can render a valid artifact unverifiable.
  • Migration debt is substantial and ongoing. Version 2 of the log is generally available but not the public default, the signing client has an announced breaking release ahead, some official clients lag the new log format, and a post-quantum migration is named as the next break after that.

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

Sigstore

Free
  • Public good instanceFree
    • Free to everyone with no contract
    • 99.5 percent availability objective, not an agreement
    • 100KB cap per attestation upload
  • Self-hostedFree
    • Apache-2.0
    • Run your own Fulcio and Rekor
    • Rekor v2 available for self-hosters

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

  • You need fulcio.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows, Self-hosted.
  • You also want rekor.
Sigstore review

Questions people ask

Is Infracost or Sigstore better?
Neither clearly leads. Infracost starts at Free and Sigstore at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Infracost or Sigstore?
Infracost starts at Free and Sigstore at Free.
Does Infracost or Sigstore run on more platforms?
Infracost runs on Web, macOS, Linux, Windows, Docker. Sigstore runs on Web, Linux, macOS, Windows, 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 Sigstore is typically brought in for.
What can Infracost do that Sigstore cannot?
Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

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.

Sigstore: Is the public instance really free?

Yes, with no contract and no paid tier. That is also the weakness: a 99.5 percent objective with no agreement, no remedy and support through Slack.

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.

Sigstore: Has the public log moved to Rekor v2?

No. Version 2 reached general availability in October 2025 and self-hosters can use it, but the public instance still defaults to version 1 and the project has said it will for the foreseeable future.

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.

Sigstore: Does Sigstore make my dependencies safe?

No, and this is a category error worth avoiding. It tells you who published something. It has no knowledge of what the artifact contains or whether it is vulnerable.

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.

Sigstore: What are the rate limits?

Not published. Only the 100KB cap per attestation upload is documented, so do not design a high-volume pipeline around assumed throughput.

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.

Sigstore: Should we self-host it?

If a public record of every signature is unacceptable, or if a free service with no agreement cannot sit in your build path, then yes. Otherwise the public instance is what most projects use.

Share

Related pages

More on Infracost

More on Sigstore

Keep looking

Other head to heads