Softwr

Developer Tools · head to head

Depot vs Sigstore

Depot logo

Depot

Developer Tools

Cloud-based builds and CI runs 55x faster with less cost

From
Free
Free plan
Yes
Full reviewWebsite
Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Each has a real cost: Depot developer plan minute limits may be insufficient for active development; 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: Depot covers Depot CI, Sigstore covers Fulcio.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Depot and Sigstore actually diverge.

Attributes where Depot and Sigstore differ
AttributeDepotSigstore
Pricing modelUnknownOpen source, public instance free to use
PlatformsCloud, GitHub, CLIWeb, Linux, macOS, Windows, Self-hosted
CategoryDeveloper ToolsCybersecurity
Founded2022Unknown

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 Depot

  • Depot CI
  • Container builds
  • GitHub Actions runners
  • Distributed caching
  • Build API
  • Depot Registry
  • Cross-platform builds
  • SSH debugging

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.

Depot

  • Accelerating Docker builds for container-based developmentnot Sigstore
  • Replacing GitHub Actions runners with faster infrastructurenot Sigstore
  • Distributing cache across Monorepo buildsnot Sigstore
  • Debugging failed CI builds interactively with SSHnot Sigstore

Sigstore

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

Where each one falls short

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

Depot

  • Developer plan minute limits may be insufficient for active development
  • Startup plan at $200/mo is expensive for smaller teams
  • Business plan requires custom pricing consultation
  • macOS M2 runners not available on Developer plan

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

Depot

Free
  • Developer$20/month
    • 1 user
    • 500 Docker build minutes per month
    • 2,000 Depot CI minutes per month
  • Startup$200/month
    • Unlimited users
    • 5,000 Docker build minutes per month
    • 20,000 Depot CI minutes per month
  • Business$undefined/custom
    • Custom pricing
    • Unlimited users
    • Custom monthly compute

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

  • You need depot ci.
  • You want to start without paying.
  • You work on Cloud, GitHub, CLI.
  • You also want container builds.
Depot 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 Depot or Sigstore better?
Neither clearly leads. Depot 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, Depot or Sigstore?
Depot starts at Free and Sigstore at Free.
Does Depot or Sigstore run on more platforms?
Depot runs on Cloud, GitHub, CLI. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use Depot for free?
Both have a free tier, so you can try either at no cost before committing.
What is Depot best used for?
Depot is most often used for accelerating docker builds for container-based development, replacing github actions runners with faster infrastructure, distributing cache across monorepo builds, debugging failed ci builds interactively with ssh. Of those, accelerating docker builds for container-based development and replacing github actions runners with faster infrastructure are not what Sigstore is typically brought in for.
What can Depot do that Sigstore cannot?
Depot covers Depot CI, Container builds, GitHub Actions runners, Distributed caching. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

Depot: How much faster are Depot runners compared to GitHub Actions?

Depot runners offer 30% faster CPUs and 10x faster networking than standard GitHub-hosted runners, enabling builds to complete significantly faster.

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.

Depot: What is included in the Developer plan?

Developer plan ($20/month) includes 500 Docker build minutes, 2,000 Depot CI minutes, 2,000 GitHub Actions minutes, 25 GB storage, unlimited concurrency, and community support.

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.

Depot: Can I use Depot with my own AWS account?

Yes, Depot Managed allows deployment within customer AWS accounts. This is available to interested customers; contact sales for details.

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 Depot

More on Sigstore

Keep looking

Other head to heads