CRACI vs Sigstore
CRACI
craci.comSigstore
sigstore.devSide by side
| Figure | CRACI | Sigstore |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 2 | 2 |
| Spec score · Software Supply Chain Security Software | 7.8 (#13) | 8.4 (#6) |
| Founded | 2025 | 2021 |
| Support | The Pro plan includes standard support, while Enterprise includes priority support. | Community support is provided through Slack and GitHub issues, with repository CODEOWNERS identifying project maintainers. |
Plans
In their own words
CRACI
CRACI is a web service providing managed continuous-integration runners that capture software dependencies during builds and monitor them for vulnerabilities. It creates build-time SBOMs containing transitive dependencies and declared licenses, with CycloneDX and SPDX export formats. Monitored SBOMs are reevaluated as vulnerabilities emerge, and the service supports triage, fix routing, and VEX. GitHub Actions is the supported CI integration today; other CI systems are roadmap items. CRACI records packages from npm, PyPI, RubyGems, Cargo, Go, Nix, OCI registries, Debian, Ubuntu, Alpine, and Git or other source downloads. Jobs use a prevalidated egress policy that fails closed, and policy gates can stop builds during execution. Managed runners are Linux on x86-64 and ARM64; Windows, macOS, and on-premises runners are planned. CRACI says source code is processed during builds but not stored, while build data is hosted in Europe. Its API returns SBOMs, network traces, and provenance, though the pricing FAQ says reports cannot be exported. Pro has no monthly fee and meters usage at $0.002 /vCPU-minute.
Sigstore
Sigstore is a free, open source project for signing and verifying software artifacts to improve supply chain security. It supports release files, container images, binaries, software bills of materials, and more. Signatures use temporary keys, so developers do not have to manage signing keys; events are recorded in a tamper-resistant public log for audit. Its components include Cosign, Fulcio, Rekor, OpenID Connect, and Policy Controller. Cosign signs and verifies artifacts and stores signatures in an OCI registry. Fulcio issues temporary certificates to authorized identities, while Rekor keeps signed metadata in a searchable ledger. OpenID Connect authenticates users through providers such as GitHub and Google. The trust root uses The Update Framework and is maintained by five keyholders from different companies and academic institutions. Sigstore provides GitHub Actions, documents GitLab CI installation, and offers official clients for Go, Java, JavaScript, Python, Ruby, and Rust. It supports API, Linux, macOS, Windows, and self-hosted environments. One integration caveat is that Cosign has no API stability guarantees, does not follow semantic versioning, and is not recommended for application integration because of its dependencies.