120% more reported CVEs per day in 2026 than last year.

CRA Compliance for SaaS & Cloud Services

Know what every build of your service pulled in, without slowing down releases

Built for Cloud Delivery

CRACI runs your GitHub Actions builds on managed runners on European infrastructure and records every dependency each build pulls in. It automates a significant part of the supply chain visibility and evidence your CRA process needs, for the services you build and ship.

GitHub Actions jobs on CRACI runners A GitHub Actions workflow sets runs-on to craci. Each job runs in its own isolated virtual machine on a CRACI runner, on Linux x86-64 or ARM64, hosted in Europe, and the run still appears in GitHub. .github/workflows/release.yml jobs: build: runs-on: craci was: ubuntu-latest CRACI runners Hosted in Europe Job VM build Linux x86-64 Job VM test Linux ARM64 Job VM publish Linux x86-64 One isolated virtual machine per job, 1 to 32 vCPU Runs still appear in GitHub About 2x GitHub-hosted speed

Continuous Deployment Protection

CRACI records an SBOM on every build, with a completeness state, enforces an egress policy validated before each job starts, and returns SBOMs, network traces and provenance through its API. Setup is runs-on: craci, so your release cadence stays the same.

An SBOM recorded during the build Packages from npm, PyPI, Cargo, Go, OCI registries and the CI cache pass through a package-aware proxy on the CRACI runner. The job's SBOM lists what was fetched, states its completeness and exports as CycloneDX or SPDX. Package sources npm PyPI Cargo · Go OCI registries CI cache restore Package- aware proxy on the runner Job SBOM express 5.2.1 requests 2.32.3 serde 1.0.219 + transitive deps Declared license on every component Complete Completeness states per job and cache: Complete, Complete with connections, Incomplete, Unavailable, Not recorded CycloneDX · SPDX

Multi-Product Management

Findings aggregate across builds and repositories, and the inventory view shows exactly which software versions are deployed to which products. SBOMs export as CycloneDX or SPDX, including vulnerabilities.

One view across builds and repositories Findings from every build are aggregated across repositories, with organization views on the default branch. The inventory view shows which software versions are deployed to which products. Default branch builds api-service web-app firmware billing Organization view Findings aggregated across builds and repositories 4 repositories, one list of findings Inventory: deployed versions Product Version Web app v4.12.0 Mobile API v2.3.1 Gateway firmware v1.8.4

API Security & Monitoring

Know what your API servers are running. The CRACI API returns each build's CycloneDX SBOM, network trace and provenance, and monitored SBOMs are re-evaluated as new vulnerabilities are published.

Provenance data from every build Every job on CRACI records the packages it fetched and its network trace. The public REST API returns the job's SBOMs, network trace and provenance. Build release job on CRACI Recorded packages fetched network trace Provenance build data, via the API Ask the API about any job Job → SBOM, trace, provenance Returned by the API Job Packages CycloneDX SBOM Network trace Recorded on every CRACI job, no extra step

Scale your SaaS with confidence

Book a demo to secure your cloud services with CRACI

Book a demo