Softwr

Cybersecurity · head to head

Sigstore vs ThetaRay

Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

From
Free
Rated
-
Full reviewWebsite
ThetaRay logo

ThetaRay

Cybersecurity

Unsupervised AI transaction monitoring for cross-border and correspondent banking

From
On request
Rated
-
Full reviewWebsite

The short version

  • Only Sigstore has a free tier, so it costs nothing to try first.
  • 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.; ThetaRay unsupervised models are harder to justify to an examiner than explicit rules, and some regulators still expect documented threshold logic, which can force you to run both systems.
  • They diverge on capability: Sigstore covers Fulcio, ThetaRay covers Unsupervised detection.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Sigstore and ThetaRay actually diverge.

Attributes where Sigstore and ThetaRay differ
AttributeSigstoreThetaRay
Starting priceFreeOn request
Pricing modelOpen source, public instance free to usequote
Free tierYesNo
PlatformsWeb, Linux, macOS, Windows, Self-hostedWeb

Identical on both: user rating (Not yet rated), category (Cybersecurity).

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 ThetaRay

  • Unsupervised detection
  • Cross-border focus
  • Sanctions screening
  • Alert triage
  • Customer risk scoring
  • Cloud native

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 ThetaRay
  • Organisations meeting a signed-artifact requirement without buying a signing productnot ThetaRay
  • Publishing provenance that a consumer can verify independently of younot ThetaRay
  • Self-hosting the same components where a public log is unacceptablenot ThetaRay

ThetaRay

  • A correspondent bank that cannot see the ultimate originator and needs behavioural signals rather than counterparty listsnot Sigstore
  • A cross-border payments fintech whose rules engine produces more alerts than its compliance team can clearnot Sigstore
  • A bank under a regulatory consent order needing demonstrable improvement in detection within a fixed periodnot Sigstore
  • A payment institution entering a high-risk corridor where existing thresholds were calibrated on domestic trafficnot 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.

ThetaRay

  • Unsupervised models are harder to justify to an examiner than explicit rules, and some regulators still expect documented threshold logic, which can force you to run both systems.
  • The alert reduction claim depends heavily on your data, so a parallel run is essential and adds months and cost before you can decommission the incumbent.
  • Coverage is strongest in cross-border and correspondent flows; institutions whose risk is domestic retail fraud will find the fit weaker than a general-purpose monitoring platform.
  • It is a smaller vendor than the incumbents, so integration connectors into legacy core banking systems are often bespoke work rather than a supported adapter.
  • Model retraining and tuning are vendor-led, which means changing detection behaviour is a support conversation rather than something your own analysts can do that afternoon.

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

ThetaRay

On request
  • ThetaRay Sonar$undefined/year
    • Priced by monitored transaction volume and number of monitored entities
    • SaaS on Azure with regional data residency options
    • Parallel run and model tuning included in onboarding

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

  • You need unsupervised detection.
  • You also want cross-border focus.
ThetaRay review

Questions people ask

Is Sigstore or ThetaRay better?
Neither clearly leads. Sigstore starts at Free and ThetaRay at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Sigstore or ThetaRay?
Sigstore has a free tier; the other does not. Paid plans start at Free for Sigstore and On request for ThetaRay.
Does Sigstore or ThetaRay run on more platforms?
Sigstore runs on Web, Linux, macOS, Windows, Self-hosted. ThetaRay runs on Web.
Can I use Sigstore for free?
Yes. Sigstore has a free tier, so you can try it without paying. ThetaRay starts at On request.
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 ThetaRay is typically brought in for.
What can Sigstore do that ThetaRay cannot?
Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients. ThetaRay covers Unsupervised detection, Cross-border focus, Sanctions screening, Alert triage.

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.

ThetaRay: Does it replace a rules engine entirely?

Rarely on day one. Most institutions run it alongside existing rules during a parallel period, and some keep specific regulator-mandated rules permanently.

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.

ThetaRay: Where is the data processed?

SaaS runs on Microsoft Azure with regional deployment options, which is the mechanism for meeting data residency conditions in regulated markets.

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.

ThetaRay: Is sanctions screening included?

Screening is available on the same platform but licensed as part of the commercial package rather than bundled by default. Confirm it is in your quote.

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 Sigstore

More on ThetaRay

Keep looking

Other head to heads