Softwr

Cybersecurity · head to head

Cosign vs UrBackup

Cosign logo

Cosign

Cybersecurity

Signs and verifies container images and artifacts, with or without managing keys

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 Cosign 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 Cosign and UrBackup actually diverge.

Attributes where Cosign and UrBackup differ
AttributeCosignUrBackup
PlatformsmacOS, Linux, Windows, Self-hostedLinux, Windows, macOS
CategoryCybersecurityBackup

Identical on both: starting price (Free), pricing model (Open source, no licence fee), 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 Cosign

  • Keyless signing
  • Key and KMS signing
  • Registry-native storage
  • In-toto attestations
  • Offline verification
  • Trusted root and signing config

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.

Cosign

  • Signing container images in a build pipeline without managing long-lived private keysnot UrBackup
  • Attaching a signed bill of materials to a release so consumers can verify its provenancenot UrBackup
  • Meeting a customer or regulatory requirement for signed artifactsnot UrBackup
  • Verifying third-party images before they enter an internal registrynot UrBackup

UrBackup

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

Where each one falls short

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

Cosign

  • Keyless signing inherits every weakness of the identity provider behind it. Sigstore’s own threat model states that if an identity provider is compromised, Sigstore will issue certificates to those identities, so a compromised account produces perfectly valid signatures
  • A signature proves who signed, never whether they should have. The documentation is explicit that Sigstore cannot determine authorisation, so every consumer must write and maintain their own identity and issuer policy or verification means nothing
  • Nothing is enforced without an admission controller. Signing changes what you can prove, not what runs, and the official policy controller has a small maintainer base for a component sitting in a cluster admission path
  • Upgrades break pipelines. Version 3 changed defaults, version 4 is announced as removing legacy functionality and roughly half the command line flags, and two official client libraries still lacked support for the new log format as of mid 2026
  • Signatures do not expire. An artifact signed before a maintainer account was compromised and one signed after are indistinguishable unless somebody is actively monitoring the transparency log, and almost nobody is

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

Cosign

Free
  • CosignFree
    • Apache-2.0
    • Public Sigstore infrastructure free to use
    • No usage limits published

UrBackup

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

Which should you pick?

Choose Cosign if

  • You need keyless signing.
  • You want to start without paying.
  • You work on macOS, Linux, Windows, Self-hosted.
  • You also want key and kms signing.

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 Cosign or UrBackup better?
Neither clearly leads. Cosign 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, Cosign or UrBackup?
Cosign starts at Free and UrBackup at Free.
Does Cosign or UrBackup run on more platforms?
Cosign runs on macOS, Linux, Windows, Self-hosted. UrBackup runs on Linux, Windows, macOS.
Can I use Cosign for free?
Both have a free tier, so you can try either at no cost before committing.
What is Cosign best used for?
Cosign is most often used for signing container images in a build pipeline without managing long-lived private keys, attaching a signed bill of materials to a release so consumers can verify its provenance, meeting a customer or regulatory requirement for signed artifacts, verifying third-party images before they enter an internal registry. Of those, signing container images in a build pipeline without managing long-lived private keys and attaching a signed bill of materials to a release so consumers can verify its provenance are not what UrBackup is typically brought in for.
What can Cosign do that UrBackup cannot?
Cosign covers Keyless signing, Key and KMS signing, Registry-native storage, In-toto attestations. UrBackup covers Windows image backups, File backups, Web interface, Client discovery.

Answered from the vendors’ own pages

Cosign: Does Cosign tell me if an image is vulnerable?

No. It has no vulnerability knowledge whatsoever. It can carry an SBOM as a signed attestation but never reads it. Pair it with a scanner.

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.

Cosign: Is signing alone enough?

No. Verification is a command somebody runs. Without an admission controller enforcing it, an unsigned image still runs.

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.

Cosign: What does a bare cosign verify actually prove?

Very little. Without a pinned certificate identity and OIDC issuer, it accepts a valid signature from any identity at all.

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.

Cosign: What is the risk of keyless signing?

Your OIDC provider becomes the root of trust. Compromise of that account yields genuine, verifiable signatures, so account security is the control that matters.

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.

Cosign: Should we expect breaking changes?

Yes. Version 4 is announced to remove roughly half the flags, and a post-quantum migration is named as a further breaking change after that.

Share

Related pages

Other head to heads