Comparison
European CI/CD tools: platforms and runners
Which CI/CD tools are European, and where do they actually run? This page lists CI platforms and runners by the company behind them, where the hosted service runs and whether you can host it yourself, checked on each vendor's own site in November 2026.
Updated
Two choices: the platform and the runners
A CI/CD pipeline has two layers that can sit in different places. The CI platform is the control plane: it stores your code, workflow definitions, logs and secrets, and orchestrates every job. The runners are the machines where each job executes, with your code and secrets present. You can make either layer European, or both. Moving the runners is a configuration change; moving the platform is a migration.
How to judge whether a CI/CD tool is European
- The company. Where it is headquartered, which entity you contract with, and which law governs the contract.
- The owner. A company founded in Europe can be owned from elsewhere, and the other way round.
- The hosting. Which regions the hosted service runs in, and on whose infrastructure.
- Self-hosting. Whether you can run it yourself, on infrastructure you choose.
On this page "European" means Europe, not only the EU, so Serbia and the United Kingdom are labelled where they apply. Write down the answers for each layer of your own pipeline and compare them with your requirement.
European CI platforms
| Platform | Company | Where the hosted service runs | Self-hosted |
|---|---|---|---|
| Codeberg | Codeberg e.V., a non-profit association in Berlin, Germany | Mostly its own hardware in a rented facility in Berlin; CI with Woodpecker or Forgejo Actions | Not applicable: Codeberg is a hosted instance of Forgejo |
| Forgejo and Forgejo Actions | A community open-source project, governed by its contributors | No hosted service from the project itself | Yes, GPL v3 or later. Forgejo Actions is familiar to GitHub Actions users but not designed to be compatible |
| Woodpecker CI | A community open-source project, funded through Open Collective; no company or country | No hosted service from the project | Yes, Apache 2.0. Works with Forgejo, Gitea, GitHub, GitLab and Bitbucket |
| JetBrains TeamCity | JetBrains N.V., headquartered in Amsterdam, Netherlands | TeamCity Cloud runs in AWS's Dublin, Ireland, region, which cannot be changed | Yes, TeamCity On-Premises (commercial) |
| Buddy | BDY PSA, Warsaw, Poland | A US region and an EU region on AWS in Stockholm; the EU region is the default for sign-ups from Europe | Yes, an on-premises edition (commercial) |
| Semaphore | Semaphore Technologies doo, Novi Sad, Serbia (Europe, not the EU), under Serbian law | Its security page says the application runs on Google Cloud and build agents on Hetzner in Europe | Yes. The Community Edition is open source (Apache 2.0); the Enterprise Edition is commercial |
European roots, but check the details
- Bitrise (mobile CI) says it is headquartered in Budapest, Hungary. Its terms name Bitrise Limited, in England, as the contracting party and California law as the governing law. Its Mac data centers include Amsterdam, its Linux machines run on Google Cloud in the US, and Enterprise customers can keep builds in the EU.
- Codemagic (mobile CI) is run by Nevercode Ltd, registered in the United Kingdom, with an address in Tartu, Estonia. Its data centers are in the US; dedicated macOS hosts can be EU-based on Enterprise.
- Travis CI was founded in Berlin and has been part of Idera, Inc. since 2019.
Often called European, but not
- GitLab: GitLab Inc. is a US company, incorporated in Delaware and listed on Nasdaq, and describes itself as remote with no headquarters. GitLab.com runs mainly in Google Cloud's us-east1 region, and GitLab Dedicated runs in the AWS region you choose. Self-managed GitLab on European hosting moves where the pipeline runs, not who makes the software.
- Jenkins is an open-source project of the Continuous Delivery Foundation, part of the Linux Foundation. There is no hosted Jenkins from the project: it runs wherever you host it, so it can be fully European on your own infrastructure.
For features and pricing rather than origin, see CI/CD platforms compared.
European runners
If you keep your CI platform and only move where builds execute, the runner is what changes. Most runner providers support GitHub Actions only.
| Runner | Company | Where builds run | CI supported |
|---|---|---|---|
| CRACI | CRACI Corporation Oy, Helsinki, Finland | Managed runners on European bare-metal infrastructure, in several data centers in Finland and Sweden | GitHub Actions; GitLab CI and Jenkins on the roadmap |
| Avrea | Avrea Oy, Helsinki, Finland | Names Aiven, Google Cloud and OVHcloud as hosting providers; data location is agreed with Avrea | GitHub Actions |
| RunsOn | Made by a founder based in Rennes, France | In your own AWS account, in the AWS region you choose | GitHub Actions |
| Ubicloud | Offices in San Francisco, Amstelveen and Istanbul. Customers in the EEA contract with Ubicloud B.V. in the Netherlands, under California law | Falkenstein, Germany, and Helsinki, Finland; open source (AGPL 3.0), so you can also run it yourself | GitHub Actions |
| Self-hosted runners on a European cloud | You, on Hetzner (Germany), OVHcloud (France), Scaleway (France), STACKIT (Germany) or UpCloud (Finland) | The provider's data centers you choose | Any CI system that supports self-hosted runners |
Blacksmith, Namespace, WarpBuild and Depot are US companies. Blacksmith also runs machines in Amsterdam and Frankfurt, which gives you a European location, not a European operator. For price and features side by side, see GitHub Actions runner providers compared, and for GitHub Actions layer by layer, European runners for GitHub Actions.
Three setups that work
| Setup | What is European | What is not |
|---|---|---|
| GitHub with European runners | Build execution, and with CRACI the record of what each build fetched | GitHub stores the code, logs, secrets and artifacts and orchestrates every job |
| A self-hosted forge on European hosting | Everything: Forgejo or self-managed GitLab, with their runners, on a European cloud or your own servers | Nothing in the hosting; with GitLab, the software vendor is a US company |
| A European hosted CI platform | The platform and its builds, where the hosted service runs in Europe (Codeberg, Buddy's EU region, TeamCity Cloud) | Check the infrastructure underneath: TeamCity Cloud and Buddy run on AWS |
Residency is not sovereignty
Data residency is about where data is stored and processed. Sovereignty adds who controls it and which law applies to that party. A European region run by a company from outside Europe gives you residency, not sovereignty. Which jurisdictions matter for you is a question for your legal counsel. The layer-by-layer version for GitHub Actions is on European runners for GitHub Actions.
Where CRACI fits
CRACI provides managed runners for GitHub Actions, operated by a Finnish company in several data centers in Finland
and Sweden. Moving to it is a label change, runs-on: craci. Builds run about twice as fast as on
GitHub-hosted runners, and CRACI records what every build fetched as an SBOM. It charges only for build minutes:
$0.002 per vCPU-minute ($0.004 for a default 2 vCPU runner), metered per second. See
CRACI's runners and pricing.
When CRACI is not the answer
- You use GitLab CI, Jenkins or another CI system. CRACI supports GitHub Actions only today, with GitLab CI and Jenkins on the roadmap.
- Your requirement covers the control plane or code storage. GitHub stays in every CRACI pipeline. You need a self-hosted forge or a European hosted platform.
- Runners must run on your own hardware. Customer-hosted CRACI runners are on the roadmap, not available today.
- You need macOS or Windows builds. CRACI runs Linux on x86-64 and ARM64 today, with Windows and macOS on the roadmap.
European CI/CD tools: frequently asked questions
Which CI/CD tools are European?
Among hosted CI platforms, Codeberg (a German non-profit), JetBrains TeamCity (JetBrains is headquartered in Amsterdam), Buddy (Poland) and Semaphore (Serbia) are run by companies or associations based in Europe. Forgejo and Woodpecker CI are open-source projects you can host in Europe yourself. For GitHub Actions runners, CRACI and Avrea are Finnish companies. Check where each one's hosted service runs as well as where the company is based.
Is GitLab a European company?
No. GitLab Inc. is a US company, incorporated in Delaware and listed on Nasdaq, and it describes itself as remote with no headquarters. GitLab.com runs mainly in Google Cloud's us-east1 region. Self-managed GitLab on European hosting moves where your CI runs, not who makes the software.
Can I run CI/CD entirely on European infrastructure?
Yes, if you move the whole pipeline: a self-hosted forge such as Forgejo or self-managed GitLab, with its runners, on a European cloud or your own servers, or a hosted service such as Codeberg that runs on its own hardware in Berlin. If you stay on GitHub, European runners move the build execution, but GitHub still stores your code and orchestrates every job.
What is the difference between a European CI platform and European runners?
The CI platform is the control plane: it stores the code, the workflow definitions, the logs and the secrets, and decides when jobs run. Runners are the machines where each job executes. Changing runners moves the build itself; changing the platform moves everything else.
Which European options work with GitHub Actions?
Managed runners from CRACI or Avrea, both Finnish companies; RunsOn, made in France, which runs runners in your own AWS account; Ubicloud, which runs runners in Germany and Finland; or self-hosted runners on a European cloud such as Hetzner, OVHcloud, Scaleway, STACKIT or UpCloud.
Run a build on European infrastructure
Book a demo: run one of your GitHub Actions workflows on CRACI in Finland and Sweden and see what it fetched.
Book a demo