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
Each artifact gets its own evidence at build time. A changed byte no longer matches.
01 / 04
Your pipelineBuild output
Each file the build produces is hashed on the runner.
What the evidence proves
- Whether a file is byte for byte what the build timestamped or sealed.
- When the build's evidence was created.
What it does not prove
- What was changed, or by whom.
- That the build output itself was free of flaws or malicious code.
- Anything about files nobody checks. A change is found when someone verifies.
04 · Go deeper
Technical depth, when you want it.
Connect GitHub Setup guide with screenshots, from install to first sealed build.Verify before you deploy A pipeline step that checks a candidate with OpenSSL. No Sigill service needed.GitHub Actions in the API docs Token exchange, signing rules and provenance.Sigill Evidence action Open source on GitHub, Apache 2.0.
Try it yourself, or run a pilot
Create an account and an API key to evaluate Sigill on your own, or talk to us about a pilot.