CRACI
Managed Linux runners for GitHub Actions on European bare metal that record a build-time SBOM and apply an egress policy to each job. A European managed runner service for GitHub Actions that pairs per-job virtual machines with SBOM, provenance and egress-policy features, suited to teams with supply-chain or data-location requirements.
Overview
CRACI is a Helsinki-based company whose managed runners replace the GitHub-hosted runner while workflows, reviews and deployments stay in GitHub Actions. A team installs the CRACI GitHub App on its organization and sets runs-on: craci. Jobs run in isolated virtual machines on bare-metal servers in Finland and Sweden, on Ubuntu 24.04 images for x64 or ARM64. Only Linux jobs are supported.
The product is built around supply-chain evidence: CRACI records the packages a job downloads into an SBOM without a plugin, keeps network traces and provenance records, and checks an egress policy before a job starts. Runner size is a number of compute units, each 1 vCPU and 3 GiB of memory, and compute costs €0.002 per vCPU-minute on either architecture, billed by the second. The Starter plan has no platform fee.
Notable
- 2025: CRACI was founded in Helsinki (about page).
- 2026: a €1.4M pre-seed round led by Lifeline Ventures, with First Fellow Partners and Wave Ventures, was announced (about page).
- As of November 22, 2026 the pricing page says early-adopter terms stay in place through 2027.
CRACI specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux |
| Architectures | x64, arm64 |
| Deployment | Managed runner service |
| Isolation | Each job runs in its own isolated virtual machine on bare-metal infrastructure; the hypervisor is not named |
| Fresh environment per job | Not documented |
| Hardware | European bare-metal infrastructure in data centers in Finland and Sweden; CPU models are not published. |
| Performance (vendor claim) | CRACI says jobs run twice as fast as on GitHub-hosted runners (vendor claim) |
| Runner sizes | Any size from 1 to 32 vCPU with 3 GiB of memory per vCPU on Starter (default 2 vCPU / 6 GiB); up to 64 vCPU on Secure and Enterprise |
| Caching | Autocaching for common public packages is included, with private sources on the Secure plan. Other cache features are not documented; the docs note that an SBOM may be incomplete when a job restores dependencies from a cache. |
| Docker layer caching | Not documented |
| GPU | Not documented |
| Concurrency | No limit on parallel jobs on any plan; while running on free credits, jobs can use 8 vCPUs in total at a time |
| Job limits | Not documented |
| Static IPs | Not documented |
| SSH into running jobs | Not documented |
| Observability | Per-job SBOMs, network traces and provenance records, retained for 180 days by default |
| Setup | Connect a GitHub organization by installing the CRACI GitHub App, then change runs-on to craci. Size, image and network policy are set with the cracicorp/setup@v1 action or with runner templates. |
| Example label | craci |
| Pricing | €0.002 per vCPU-minute, billed by the second, at the same rate on x86-64 and ARM64: €0.004/min (2 vCPU / 6 GB), €0.008 (4 vCPU), €0.016 (8 vCPU), €0.032 (16 vCPU), €0.064 (32 vCPU). Starter has no platform fee; Secure is €2,000/month plus usage with 10% off compute. |
| Free tier | €10 of free credit on the Starter plan, with no card needed |
| Compliance | ISO/IEC 27001 (certificate issued by Into Certification) |
| Regions | Data centers in Finland and Sweden |
| Open source | No |
| Company headquarters | Helsinki, Finland · More from Finland |
Facts from CRACI’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- You need CI jobs to run on bare-metal infrastructure in Finland and Sweden
- You want an SBOM and network trace recorded for every job without adding workflow steps
- You want to restrict outbound network access from jobs with a policy checked before the job starts
- You want x86-64 and ARM64 runners at the same per-vCPU rate, with no limit on parallel jobs
Trade-offs
- Runs Linux jobs only; macOS and Windows jobs stay on other runners (quickstart)
- GitHub Actions is the only CI system supported today
- While on free credits, jobs can use 8 vCPUs in total at a time
- An SBOM may be incomplete when a job restores dependencies from a cache
Good fit for: Teams on GitHub Actions that want European-hosted Linux runners with per-job SBOMs and network egress policy.
Use cases CRACI fits
- Lower CI cost: Compute is €0.002 per vCPU-minute billed by the second, with no platform fee on Starter and €10 of free credit.
- ARM64 builds: A full Ubuntu 24.04 image is available for native ARM64 builds at the same per-vCPU rate as x86-64.
- Security and compliance: Each job gets an isolated VM, a recorded SBOM and network trace, and an egress policy checked before it starts; CRACI states ISO/IEC 27001 certification.
How CRACI compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| CRACI | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | Per-job VM | €0.004/min | 32 vCPU / 96 GB | Not documented | Not documented | No | Finland |
| Blacksmith | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Firecracker microVM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | United States |
| Depot GitHub Actions Runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Single-tenant EC2 instance | $0.006/min | 64 vCPU / 256 GB | Yes | Yes | No | Not documented |
| Namespace | GitHub Actions, Buildkite | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Virtual machine | $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) | 64 vCPU / 512 GB | Yes | Not documented | No | Not documented |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United States |
| WarpBuild | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Ephemeral VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Not documented |
| RunJob | GitHub Actions, GitLab CI | Linux, x64 | Vendor-hosted | KVM virtual machine | €0.00002 per vCPU-second used | 48 vCPU / 96 GB | No | Yes | No | Estonia |
| Actuated | GitHub Actions, GitLab CI | Linux, x64, arm64 | Your cloud or hardware | Firecracker microVM | $150/mo per server + your servers | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
Head-to-head: Blacksmith vs CRACI
Frequently asked questions
What is CRACI?
Which CI systems does CRACI work with?
How does CRACI isolate jobs?
Is CRACI open source?
How much does CRACI cost?
How do I switch from GitHub-hosted runners to CRACI?
craci.How fast is CRACI?
Does CRACI have a free tier?
Does CRACI support ARM64 runners?
How many jobs can run at once on CRACI?
Where do CRACI runners run?
What compliance certifications does CRACI have?
Where is CRACI Corporation Oy based?
What are the alternatives to CRACI?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
CI Runners. (2026). CRACI. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/craci/