Softwr

Backup · head to head

Restic vs Sigstore

Restic logo

Restic

Backup

Fast, secure, and efficient backup program

From
Free
Free plan
Yes
Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

From
Free
Free plan
Yes

The short version

  • Restic is a fast, secure backup program.
  • Both are free.
  • Only Restic lists content-defined chunking; only Sigstore lists keyless signing.
  • Where Restic falls short: A Windows file whose name contains a character Windows treats as invalid cannot be read by restic and has to be renamed.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Restic and Sigstore actually diverge.

Attributes where Restic and Sigstore differ
AttributeResticSigstore
Pricing modelFreeOpen source, public instance free to use
PlatformsWindows, macOS, LinuxWeb, Linux, macOS, Windows, Self-hosted
CategoryBackupCybersecurity

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

Not yet recorded: founded for Sigstore.

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 Restic

  • Content-defined chunking
  • Cryptographic verification
  • Deduplication
  • Encryption
  • Multiple backends
  • Snapshot management
  • AWS S3
  • Azure

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.

Restic

  • Encrypted deduplicated backups to S3, B2, SFTP and local disk from the command linenot Sigstore
  • Scripted server backups with snapshot retention policiesnot Sigstore

Sigstore

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

Where each one falls short

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

Restic

  • Cold storage is not natively supported; restoring from S3 Glacier and S3 Glacier Deep Archive is only available as an experimental feature behind a feature flag
  • A Windows file whose name contains a character Windows treats as invalid cannot be read by restic and has to be renamed
  • Antivirus real-time protection degrades performance on Windows unless the restic binary is added to an exclusions list
  • On large repositories the built-in five minute stuck-request timeout fires during file listing and has to be raised manually with --stuck-request-timeout

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

Restic

Free
  • FreeFree
    • Content-defined chunking
    • Encryption
    • Multiple backends

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

  • You need content-defined chunking.
  • You want to start without paying.
  • You work on Windows, macOS, Linux.
  • You also want cryptographic verification.

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.

Questions people ask

Is Restic or Sigstore better?
Neither clearly leads. Restic 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, Restic or Sigstore?
Restic starts at Free and Sigstore at Free.
Does Restic or Sigstore run on more platforms?
Restic runs on Windows, macOS, Linux. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use Restic for free?
Both have a free tier, so you can try either at no cost before committing.
What is Restic best used for?
Restic is most often used for encrypted deduplicated backups to s3, b2, sftp and local disk from the command line, scripted server backups with snapshot retention policies. Of those, encrypted deduplicated backups to s3, b2, sftp and local disk from the command line and scripted server backups with snapshot retention policies are not what Sigstore is typically brought in for.
What can Restic do that Sigstore cannot?
Restic covers Content-defined chunking, Cryptographic verification, Deduplication, Encryption. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

Restic: How much does restic cost?

Restic is entirely free to use and completely open source. There are no subscription tiers, paid plans, or licensing costs.

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.

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.

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

Other head to heads