What would you like to secure?

Software from build to production

Can you trust what reaches production?

Between a build and a deployment, an artifact passes through registries, caches and many hands. Sigill seals what your pipeline produced, so whatever arrives later can be checked against it.

03 · How Sigill helps

Release assets ship with their seals, in your organisation's name.

01 / 04

Your pipelineRelease published

When you publish a release, the action hashes each asset on the runner.

A seal file next to each download · optional post-quantum seal

What the evidence proves

  • That a download is byte for byte the asset your organisation sealed.
  • When it was sealed.

What it does not prove

  • How the asset was built, or that it is free of flaws.
  • That the asset is what the build produced, if it was replaced on the release page before it was sealed.
  • That it is a qualified electronic seal.