Softwr

Cybersecurity · head to head

Sigstore vs Umami

Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

From
Free
Rated
-
Full reviewWebsite
Umami logo

Umami

Marketing

Open source, cookie-free web analytics you can self-host for the cost of a database

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Umami there is no cohort analysis, retention curve, session replay or multi-touch attribution, so a marketing team that needs to justify channel spend will still buy a second tool and Umami becomes a supplementary dashboard.
  • They diverge on capability: Sigstore covers Fulcio, Umami covers Cookie-free tracking.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Sigstore and Umami actually diverge.

Attributes where Sigstore and Umami differ
AttributeSigstoreUmami
Pricing modelOpen source, public instance free to usePer month by event count
PlatformsWeb, Linux, macOS, Windows, Self-hostedWeb, Linux
CategoryCybersecurityMarketing

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 Sigstore

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

Only in Umami

  • Cookie-free tracking
  • Self-hosting
  • Small tracking script
  • Custom events
  • Funnels and goals
  • Multi-site and teams
  • Public dashboards
  • API access

What people use each for

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

Sigstore

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

Umami

  • A developer who wants traffic numbers on a personal or client site without adding a consent bannernot Sigstore
  • An organisation whose legal or procurement team has ruled out sending visitor data to a US advertising companynot Sigstore
  • A high-traffic site where hosted analytics priced by pageview band has become expensive and self-hosting removes the ceiling entirelynot Sigstore
  • A team that wants analytics data in a database they already control so they can query and join it themselvesnot Sigstore

Where each one falls short

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

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.

Umami

  • There is no cohort analysis, retention curve, session replay or multi-touch attribution, so a marketing team that needs to justify channel spend will still buy a second tool and Umami becomes a supplementary dashboard.
  • Self-hosting is only free in licence terms; you own the database, the upgrades, the backups and the query performance at scale, and a busy site's events table grows quickly enough to need real attention.
  • Because it stores no persistent identifier, it cannot follow a user across devices or sessions in any meaningful way, which makes returning-visitor and lifetime-value questions unanswerable by design rather than by omission.
  • Cloud overage is billed per event beyond the plan allowance, so a traffic spike or a badly instrumented custom event can produce a bill materially above the $20 or $200 headline before anyone notices.
  • It is maintained by a small team, so the pace of new capability is modest and enterprise expectations such as SSO, granular role permissions and formal support agreements are limited compared with commercial analytics vendors.

Pricing, plan by plan

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

Umami

Free
  • Self-hostedFree
    • MIT licensed, no licence fee
    • No event limit imposed by the software
    • Unlimited websites and users
  • Cloud HobbyFree
    • Up to 100,000 events per month
    • 3 websites
    • 6 months data retention
  • Cloud Pro$20/month
    • Up to 1,000,000 events per month
    • Unlimited websites
    • Unlimited team members
  • Cloud Business$200/month
    • Up to 10,000,000 events per month
    • All Pro features
    • Higher volume overage rate

Which should you pick?

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

Choose Umami if

  • You need cookie-free tracking.
  • You want to start without paying.
  • You work on Web, Linux.
  • You also want self-hosting.
Umami review

Questions people ask

Is Sigstore or Umami better?
Neither clearly leads. Sigstore starts at Free and Umami at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Sigstore or Umami?
Sigstore starts at Free and Umami at Free.
Does Sigstore or Umami run on more platforms?
Sigstore runs on Web, Linux, macOS, Windows, Self-hosted. Umami runs on Web, Linux.
Can I use Sigstore for free?
Both have a free tier, so you can try either at no cost before committing.
What is Sigstore best used for?
Sigstore is most often used for open source projects signing releases without running a certificate authority, organisations meeting a signed-artifact requirement without buying a signing product, publishing provenance that a consumer can verify independently of you, self-hosting the same components where a public log is unacceptable. Of those, open source projects signing releases without running a certificate authority and organisations meeting a signed-artifact requirement without buying a signing product are not what Umami is typically brought in for.
What can Sigstore do that Umami cannot?
Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients. Umami covers Cookie-free tracking, Self-hosting, Small tracking script, Custom events.

Answered from the vendors’ own pages

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.

Umami: Is Umami really free?

Self-hosted, yes; it is MIT licensed with no event cap. You pay for the server and database. Umami Cloud has a free tier at 100,000 events a month and paid tiers from $20.

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.

Umami: Do I need a cookie consent banner?

For Umami analytics specifically, generally no, because it sets no cookies and stores no personal data. Other tags on your site may still require one.

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.

Umami: Can it replace Google Analytics?

For traffic, referrers and event counts, yes. For attribution modelling, audiences and advertising integration, no.

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.

Umami: What does it need to run?

A container and a PostgreSQL or MySQL database. Most people deploy it on infrastructure they already pay for.

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 Sigstore

More on Umami

Keep looking

Other head to heads