123% meer gemelde CVE's per dag in 2026 dan vorig jaar.

CI/CD-integratie

Koppel uw repositories met een GitHub App: CRACI wordt de runner onder uw GitHub Actions-workflows, en elke run blijft zichtbaar in GitHub

Koppelen met een GitHub App

Installeer de CRACI GitHub App op alle of op geselecteerde repositories. Die koppeling is de hele installatie: CRACI kan daarna de jobs draaien van de repositories die u hebt gekozen, en u houdt zelf in de hand welke dat zijn.

Connect CRACI with a GitHub App The CRACI GitHub App is installed on all or selected repositories of a GitHub organization. CRACI can then run the jobs of the repositories you chose. Install the CRACI GitHub App Repository access for your organization All repositories Only selected repositories api-service web-app firmware sandbox CRACI runs the jobs of the repositories you chose You keep control of which repositories those are Runs, logs and checks stay in GitHub

Eén regel per workflow

CRACI vervangt de runner, niet GitHub Actions. Zet een job op runs-on: craci en hij wordt uitgevoerd op de runners van CRACI. Uw workflowbestanden, actions en secrets blijven waar ze zijn; er is geen tweede pipeline om te onderhouden.

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

Runs blijven in GitHub

Jobs die op CRACI draaien, verschijnen nog steeds in GitHub, dus runs, logs en pull-requestchecks blijven op de plek waar uw team al kijkt. De GitHub Actions-cache werkt zoals voorheen, en CRACI-runners gebruiken een vast egress-IP-bereik voor allowlists.

CRACI runs stay in GitHub Jobs that run on CRACI still appear in GitHub with their runs, logs and pull request checks. The GitHub Actions cache works as before, and CRACI runners use a stable egress IP range for allowlists. Pull request checks build runs-on: craci 1m 12s test runs-on: craci 2m 04s lint runs-on: craci 0m 31s Runs, logs and pull request checks in the usual place GitHub Actions cache as before Stable egress IP range No second pipeline to maintain Workflow files, actions and secrets stay where they are

Momenteel GitHub Actions

GitHub Actions is de ondersteunde CI-integratie. Andere CI-systemen staan op de roadmap. Builds draaien op Linux-runners voor x86-64 en ARM64, beheerd door CRACI op Europese bare-metalinfrastructuur; Windows- en macOS-runners staan ook op de roadmap.

What CRACI supports today GitHub Actions is supported today, and other CI systems, starting with GitLab CI and Jenkins, are on the roadmap. Runners are Linux on x86-64 and ARM64, managed by CRACI on European bare-metal infrastructure, with Windows and macOS on the roadmap. CI integration GitHub Actions: today GitLab CI, Jenkins: roadmap Runner operating systems Linux x86-64: today Linux ARM64: today Windows: roadmap macOS: roadmap Managed by CRACI European bare-metal infrastructure One isolated virtual machine per job Sizes from 1 to 32 vCPU, same rate on ARM64 Images: CRACI Slim, CRACI Slim ARM64, Ubuntu 24.04

Integreer naleving in uw workflow

Boek een demo om CRA-naleving in uw CI/CD-pipeline te automatiseren

Demo boeken