product
What EU data residency actually requires for CI
Pinning your compute region is not data residency. Your cache, logs and support access all handle your source code too.
Jess Okonkwo · Co-founder · 2026-07-09 · 7 min read
CI is an unusually complete data-processing surface: your source code, your secrets, your build artefacts and your logs all pass through it. Residency claims that only cover compute do not survive scrutiny.
The four things that must be pinned
| Data | Contains | Frequently overlooked? |
|---|---|---|
| Compute | Source, secrets, artefacts | No |
| Cache | Dependencies, build output | Yes |
| Logs | Whatever your build prints | Yes |
| Metrics | Repository and workflow names | Yes |
And the fifth: support access
A support engineer reading a job log is a data access. If your provider's support team is outside the boundary, your logs effectively are too. Ask about it explicitly — it is rarely volunteered.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
CI when your teammates are agentsAI coding agents push far more often than humans. Here is how that changes pipeline design and cost control.Why we publish instructions for leavingEvery migration page on this site includes the diff to migrate back off us. Here is the reasoning.What we learned running a million CI jobsQueue time, cache behaviour, right-sizing and the failure modes that only appear at scale.Stop retrying flaky testsAutomatic retries convert a real bug into an intermittent one, and train your team to distrust every failure.