Softwr

Accounting · head to head

Lago vs Sigstore

Lago logo

Lago

Accounting

Open-source billing infrastructure for usage-based models

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: Lago free tier limited to 10,000 entities per month with 5M event cap; 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: Lago covers Real-time usage metering, Sigstore covers Fulcio.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Lago and Sigstore actually diverge.

Attributes where Lago and Sigstore differ
AttributeLagoSigstore
Pricing modelFreemium with optional paid tiersOpen source, public instance free to use
PlatformsWeb, Cloud, Self-hosted, On-premise, VPCWeb, Linux, macOS, Windows, Self-hosted
CategoryAccountingCybersecurity

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 Lago

  • Real-time usage metering
  • Multiple pricing models
  • Automated invoicing
  • Prepaid credits
  • Entitlements
  • Multi-currency support
  • Payment orchestration
  • Revenue analytics

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.

Lago

  • Building usage-based billing for high-volume APIs and infrastructurenot Sigstore
  • Implementing metered billing for AI and tokenized servicesnot Sigstore
  • Creating subscription and hybrid pricing modelsnot Sigstore
  • Managing multi-currency billing for global companiesnot Sigstore
  • Maintaining billing infrastructure without vendor lock-innot Sigstore

Sigstore

  • Open source projects signing releases without running a certificate authoritynot Lago
  • Organisations meeting a signed-artifact requirement without buying a signing productnot Lago
  • Publishing provenance that a consumer can verify independently of younot Lago
  • Self-hosting the same components where a public log is unacceptablenot Lago

Where each one falls short

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

Lago

  • Free tier limited to 10,000 entities per month with 5M event cap
  • No specific pricing published for Pro annual plan or Scale plan
  • Self-hosted and on-premise deployments require engineering resources
  • Community support only on free tier
  • Scale plan requires annual contracts and sales engagement

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

Lago

Free
  • Build (Free)Free
    • 10,000 managed entities per month
    • 5M usage events per month
    • 1K events per second rate limit
  • Pro$399/month
    • 10,000 entities included (graduated pricing to 100K)
    • 25M usage events included (to 500M with graduated rates)
    • 10K events per second (upgradeable to 100K)
  • Scale$null/custom
    • Custom entity and event volumes
    • 50K events per second (upgradeable to 100K)
    • RBAC and SSO (SAML)

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

  • You need real-time usage metering.
  • You want to start without paying.
  • You work on Web, Cloud, Self-hosted, On-premise, VPC.
  • You also want multiple pricing models.
Lago 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 Lago or Sigstore better?
Neither clearly leads. Lago 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, Lago or Sigstore?
Lago starts at Free and Sigstore at Free.
Does Lago or Sigstore run on more platforms?
Lago runs on Web, Cloud, Self-hosted, On-premise, VPC. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use Lago for free?
Both have a free tier, so you can try either at no cost before committing.
What is Lago best used for?
Lago is most often used for building usage-based billing for high-volume apis and infrastructure, implementing metered billing for ai and tokenized services, creating subscription and hybrid pricing models, managing multi-currency billing for global companies. Of those, building usage-based billing for high-volume apis and infrastructure and implementing metered billing for ai and tokenized services are not what Sigstore is typically brought in for.
What can Lago do that Sigstore cannot?
Lago covers Real-time usage metering, Multiple pricing models, Automated invoicing, Prepaid credits. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

Lago: Can I use Lago open-source for free?

Yes, Lago is open-source under the AGPLv3 license and can be self-hosted. The cloud-based Build plan is also free with limits of 10,000 entities and 5M events per month.

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

Lago: What payment providers does Lago integrate with?

Lago integrates with Stripe and Adyen for payment processing. It is not a payment processor itself but orchestrates payments through these providers.

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

Lago: Does Lago support multiple currencies?

Yes, Lago supports multi-currency billing with automatic currency conversion for global businesses.

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

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.

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 Lago

More on Sigstore

Keep looking

Other head to heads