When we reach for it
Self-hosted estates, and clients whose code cannot leave their own infrastructure. Having the repository, pipeline and registry in one product is the point for teams who have to run all three themselves.
GitLab CI
A capable pipeline system tied to a platform many organisations self-host for good reasons.
When we would argue against it
Nothing inherent. As with any CI, the risk is a pipeline definition that has grown past the point anyone can read it. Self-hosting also means upgrading it, backing it up and being on call for it — a real ongoing cost that should be chosen deliberately rather than inherited.
What it looks like in delivery
Stages kept few and named for what they prove, with the same checks a developer can run locally. Same standard as anywhere else: the pipeline is the definition of done, and it runs the checks that would otherwise be somebody’s job to remember.
Where this appears on the site
Nothing on this site names it yet
We work in GitLab CI, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.
Also in delivery and observability
Working in GitLab CI?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.