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

CI/CD Integration

Connect your repositories with a GitHub App — CRACI becomes the runner underneath your GitHub Actions workflows, and every run still shows up in GitHub

Connect with a GitHub App

Install the CRACI GitHub App on all or selected repositories. That connection is the whole setup: CRACI can then run the jobs of the repositories you chose, and you keep control of which ones those are.

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

One line per workflow

CRACI replaces the runner, not GitHub Actions. Change a job to runs-on: craci and it executes on CRACI's runners. Your workflow files, actions and secrets stay where they are — there is no second pipeline to maintain.

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 stay in GitHub

Jobs that run on CRACI still appear in GitHub, so runs, logs and pull request checks stay in the place your team already looks. GitHub Actions cache works as before, and CRACI runners use a stable egress IP range for 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

GitHub Actions today

GitHub Actions is the supported CI integration. Other CI systems are on the roadmap. Builds run on Linux x86-64 and ARM64 runners managed by CRACI on European bare-metal infrastructure; Windows and macOS runners are on the roadmap too.

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

Integrate compliance into your workflow

Book a demo to automate CRA compliance in your CI/CD pipeline

Book a demo