Backup · head to head
Borg Backup vs Cosign

Borg Backup
Backup
Deduplicating archiver with compression and encryption
- From
- Free
- Free plan
- Yes

Cosign
Cybersecurity
Signs and verifies container images and artifacts, with or without managing keys
- From
- Free
- Free plan
- Yes
The short version
- Borg Backup is a deduplicating backup program.
- Both are free.
- Only Borg Backup lists content-defined chunking; only Cosign lists keyless signing.
- Where Borg Backup falls short: linux, macOS and BSD only; Windows is not a supported platform.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Borg Backup and Cosign actually diverge.
| Attribute | Borg Backup | Cosign |
|---|---|---|
| Pricing model | Free | Open source, no licence fee |
| Platforms | Linux, macOS | macOS, Linux, Windows, Self-hosted |
| Category | Backup | Cybersecurity |
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: founded for Cosign.
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 Borg Backup
- Content-defined chunking
- Deduplication
- Compression
- Authenticated encryption
- Pruning
- Mount archives
- SSH
- BorgBase
Only in Cosign
- Keyless signing
- Key and KMS signing
- Registry-native storage
- In-toto attestations
- Offline verification
- Trusted root and signing config
What people use each for
The jobs each tool is most often brought in to do.
Borg Backup
- Deduplicated backups where daily full snapshots would otherwise be expensivenot Cosign
- Encrypted backup to a server you do not fully trust, since the server never sees plaintextnot Cosign
- Browsing previous versions by mounting an archive over FUSEnot Cosign
- Scripted server backups with no agent or daemon to runnot Cosign
Cosign
- Signing container images in a build pipeline without managing long-lived private keysnot Borg Backup
- Attaching a signed bill of materials to a release so consumers can verify its provenancenot Borg Backup
- Meeting a customer or regulatory requirement for signed artifactsnot Borg Backup
- Verifying third-party images before they enter an internal registrynot Borg Backup
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Borg Backup
- Linux, macOS and BSD only; Windows is not a supported platform
- Command-line only, with no graphical interface in the project itself
- Version 2.0 is still in beta, so production use means staying on the 1.4 line
- Restoring requires the Borg tooling, since archives are a deduplicated chunk store rather than plain files
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
Pricing, plan by plan
Borg Backup
Free- FreeFree
- Deduplication
- Compression
- Encryption
Cosign
Free- CosignFree
- Apache-2.0
- Public Sigstore infrastructure free to use
- No usage limits published
Which should you pick?
Choose Borg Backup if
- You need content-defined chunking.
- You want to start without paying.
- You work on Linux, macOS.
- You also want deduplication.
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.
Questions people ask
- Is Borg Backup or Cosign better?
- Neither clearly leads. Borg Backup starts at Free and Cosign at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Borg Backup or Cosign?
- Borg Backup starts at Free and Cosign at Free.
- Does Borg Backup or Cosign run on more platforms?
- Borg Backup runs on Linux, macOS. Cosign runs on macOS, Linux, Windows, Self-hosted.
- Can I use Borg Backup for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Borg Backup best used for?
- Borg Backup is most often used for deduplicated backups where daily full snapshots would otherwise be expensive, encrypted backup to a server you do not fully trust, since the server never sees plaintext, browsing previous versions by mounting an archive over fuse, scripted server backups with no agent or daemon to run. Of those, deduplicated backups where daily full snapshots would otherwise be expensive and encrypted backup to a server you do not fully trust, since the server never sees plaintext are not what Cosign is typically brought in for.
- What can Borg Backup do that Cosign cannot?
- Borg Backup covers Content-defined chunking, Deduplication, Compression, Authenticated encryption. Cosign covers Keyless signing, Key and KMS signing, Registry-native storage, In-toto attestations.
Answered from the vendors’ own pages
Borg Backup: What is the cost of BorgBackup?
BorgBackup is completely free and open source under the BSD license with no mandatory costs for the core software.
SourceCosign: 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.
Borg Backup: Are there paid services available for BorgBackup?
Yes, optional third-party services are available: BorgBase for specialized Borg repository hosting, Hetzner Storage Box with Borg support, and rsync.net cloud storage integration.
SourceCosign: Is signing alone enough?
No. Verification is a command somebody runs. Without an admission controller enforcing it, an unsigned image still runs.
Borg Backup: How can I support the BorgBackup project?
BorgBackup accepts voluntary contributions through Open Collective, GitHub Sponsors, Liberapay, and PayPal, though donations are optional.
SourceCosign: 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.
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.
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.
Related pages
More on Borg Backup
Other head to heads
- Borg Backup vs Kopia
- Borg Backup vs rustic
- Borg Backup vs Acronis Cyber Protect
- Borg Backup vs Restic
- Borg Backup vs Clonezilla
- Borg Backup vs Velero
- Borg Backup vs Proxmox Backup Server
- Borg Backup vs Duplicacy
- Borg Backup vs HPE StoreOnce
- Borg Backup vs Amanda Enterprise
- Borg Backup vs Bacula Enterprise
- Borg Backup vs Apple Time Machine
- Borg Backup vs UrBackup
- Borg Backup vs Windows Backup
- Borg Backup vs Backupify
- Borg Backup vs Spanning Backup
- Borg Backup vs CloudAlly
- Borg Backup vs Commvault Complete Data Protection
- Borg Backup vs Sigstore
- Borg Backup vs Syft
- Borg Backup vs Chainguard
- Borg Backup vs HashiCorp Vault
- Borg Backup vs Infisical
- Borg Backup vs OWASP ZAP
- Borg Backup vs Wireshark
- Borg Backup vs Bitwarden
- Borg Backup vs Semgrep
- Borg Backup vs Trivy
- Borg Backup vs authentik
- Borg Backup vs Resolver
- Borg Backup vs Saviynt
- Borg Backup vs Securiti
- Borg Backup vs Speakeasy
- Borg Backup vs Sysdig
- Borg Backup vs Tenable
- Borg Backup vs Grype
- Cosign vs Kopia
- Cosign vs rustic
- Cosign vs Acronis Cyber Protect
- Cosign vs Restic
- Cosign vs Clonezilla
- Cosign vs Velero
- Cosign vs Proxmox Backup Server
- Cosign vs Duplicacy
- Cosign vs HPE StoreOnce
- Cosign vs Amanda Enterprise
- Cosign vs Bacula Enterprise
- Cosign vs Apple Time Machine
- Cosign vs UrBackup
- Cosign vs Windows Backup
- Cosign vs Backupify
- Cosign vs Spanning Backup
- Cosign vs CloudAlly
- Cosign vs Commvault Complete Data Protection
- Cosign vs Sigstore
- Cosign vs Syft
- Cosign vs Chainguard
- Cosign vs HashiCorp Vault
- Cosign vs Infisical
- Cosign vs OWASP ZAP
- Cosign vs Wireshark
- Cosign vs Bitwarden
- Cosign vs Semgrep
- Cosign vs Trivy
- Cosign vs authentik
- Cosign vs Resolver
- Cosign vs Saviynt
- Cosign vs Securiti
- Cosign vs Speakeasy
- Cosign vs Sysdig
- Cosign vs Tenable
- Cosign vs Grype
