123% flere rapporterede CVE'er pr. dag i 2026 end sidste år.

CRA-compliance til SaaS og cloud-tjenester

Vid, hvad hvert build af din tjeneste hentede, uden at bremse dine releases

Bygget til levering i skyen

CRACI kører dine GitHub Actions-builds på administrerede runnere på europæisk infrastruktur og registrerer hver afhængighed, hvert build henter. Det automatiserer en væsentlig del af den synlighed i og dokumentation for forsyningskæden, din CRA-proces har brug for, for de tjenester, du bygger og leverer.

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

Beskyttelse af continuous deployment

CRACI registrerer en SBOM ved hvert build, med en fuldstændighedsstatus, håndhæver en egress-politik, der valideres, før hvert job starter, og returnerer SBOM'er, netværkstraces og provenance via sit API. Opsætningen er runs-on: craci, så din release-kadence forbliver den samme.

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

Styring af flere produkter

Fund samles på tværs af builds og repositories, og inventaroversigten viser præcis, hvilke softwareversioner der er udrullet til hvilke produkter. SBOM'er eksporteres som CycloneDX eller SPDX, inklusive sårbarheder.

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-sikkerhed og overvågning

Vid, hvad dine API-servere kører. CRACI's API returnerer hvert builds CycloneDX-SBOM, netværkstrace og provenance, og overvågede SBOM'er genvurderes, efterhånden som nye sårbarheder offentliggøres.

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

Skalér din SaaS trygt

Book en demo for at sikre dine cloud-tjenester med CRACI

Book en demo