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
Your pipeline checks the candidate against the evidence. The gate stays yours.
01 / 04
Your pipelineDeploy candidate
Before deploying, your pipeline pulls the candidate and hashes it.
What the evidence proves
- That the candidate is byte for byte the artifact that was sealed.
- Which organisation's certificate sealed it, and when.
What it does not prove
- That an unverified artifact was kept out of production. The check is a step you add; Sigill has no deploy gate.
- Which workflow built it, from the seal file alone. That link is kept in Sigill's record.
- That the artifact is safe to run.
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.