Softwr

Cybersecurity · head to head

Sigstore vs UrBackup

Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

From
Free
Free plan
Yes
UrBackup logo

UrBackup

Backup

Open source client server backup doing both file and whole disk image backups of Windows machines

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Sigstore lists keyless signing; only UrBackup lists windows image backups.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which Sigstore and UrBackup actually diverge.

Attributes where Sigstore and UrBackup differ
AttributeSigstoreUrBackup
Pricing modelOpen source, public instance free to useOpen source, no licence fee
PlatformsWeb, Linux, macOS, Windows, Self-hostedLinux, Windows, macOS
CategoryCybersecurityBackup

Identical on both: starting price (Free), free tier (Yes).

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 UrBackup

  • Windows image backups
  • File backups
  • Web interface
  • Client discovery
  • Internet mode
  • Filesystem deduplication

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

UrBackup

  • A small office with Windows workstations that needs bare metal restore without per seat licensingnot Sigstore
  • Schools and labs where machines are re-imaged often and a known good image must be recoverablenot Sigstore
  • Backing up a mixed fleet to one server on premises with a web interface non specialists can usenot Sigstore
  • Replacing an expiring commercial endpoint backup licence where the budget is the constraintnot 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

UrBackup

  • Backups are stored on the server without encryption at rest by default, so the backup server holds a readable copy of every machine it protects and becomes the highest value target on the network
  • Deduplication relies on filesystem features such as hard links, btrfs or ZFS, so a server built on the wrong filesystem silently consumes far more space and the fix is a rebuild rather than a setting
  • There is no native object storage target, so offsite copies mean replicating the server storage with another tool rather than backing up to a bucket directly
  • Restoring a full Windows image requires booting a restore environment, which is a manual, on site procedure that needs to be rehearsed before the day it is needed
  • A single server holds everything and there is no built in clustering, so its own failure removes every recovery point at once unless you have separately solved replication

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

UrBackup

Free
  • UrBackupFree
    • Full functionality, unlimited clients
    • File and image backups
    • Web administration interface

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.

Choose UrBackup if

  • You need windows image backups.
  • You want to start without paying.
  • You work on Linux, Windows, macOS.
  • You also want file backups.

Questions people ask

Is Sigstore or UrBackup better?
Neither clearly leads. Sigstore starts at Free and UrBackup at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Sigstore or UrBackup?
Sigstore starts at Free and UrBackup at Free.
Does Sigstore or UrBackup run on more platforms?
Sigstore runs on Web, Linux, macOS, Windows, Self-hosted. UrBackup runs on Linux, Windows, macOS.
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 UrBackup is typically brought in for.
What can Sigstore do that UrBackup cannot?
Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients. UrBackup covers Windows image backups, File backups, Web interface, Client discovery.

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.

UrBackup: Does it back up Linux servers as well?

File backups yes, image backups no. The image path is Windows only through volume shadow copy.

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.

UrBackup: Is the data encrypted?

Transport can be encrypted, and there is optional client side file encryption, but the default server storage is not encrypted at rest. Use full disk encryption on the server.

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.

UrBackup: Can I back up to Amazon S3?

Not directly. The server writes to local or mounted storage, so cloud copies are made by replicating that storage separately.

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.

UrBackup: How many clients can one server handle?

Dozens is routine on decent hardware. The limit is usually storage input and output during overlapping backup windows rather than client count.

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

Other head to heads