Skip to main content
GitLab Channel Partner Program · Track Open

GitLab

One place for the code, the pipeline and the registry

GitLab is where most of the teams we work with keep their code, and increasingly it is where they keep everything that happens to that code afterwards. We are an authorized partner in GitLab's channel programme, listed on the Open track, and the entry is public so you can read it without taking our word for it.

GitLab Channel Partner Program, track Open
Find us in the GitLab Partner Locator

Why we build on it

Why we chose GitLab

01

One tool instead of five

Repository, pipelines, container registry, package registry, issues and releases arrive together and already know about each other. The alternative is four products stitched with webhooks, where every upgrade is a negotiation between vendors and every outage needs someone to work out whose it is.

02

You can run it yourself

Self-managed GitLab is a first-class option rather than a legacy tier. For a team with a regulator to answer to, or a board that wants the source somewhere it controls, that changes the conversation. We run it on Kubernetes for clients who need exactly that, upgrades and restore drills included.

03

The pipeline is readable

GitLab CI is YAML your own engineers can open and follow a year later, which matters more than any feature list. Pipelines we build are meant to be maintained by the team that inherits them, not by us on a retainer.

What we do on it

The work this partnership sits behind

We are listed in GitLab's Authorized Partner Locator, which is the register GitLab points customers at when they want someone to implement, migrate or run the platform for them.

What the membership changes

  • Migrations onto GitLab, including the CI rewrite that no importer does for you
  • Self-managed GitLab on Kubernetes: upgrades, runners, backups and restore drills
  • GitLab CI pipelines your team will actually maintain after we leave
  • Licensing and tier questions answered before you buy rather than after

What it does not mean

We are not neutral about GitLab and we are not paid to recommend it. Plenty of teams should stay exactly where they are, and we maintain GitHub Actions, Jenkins and Bitbucket pipelines for clients who already run them. More than once we have talked someone out of a migration when the only thing wrong with their setup was that it was not the one we know best. A move earns its cost when the tool sprawl is costing more than the migration will.

All product names, logos and brands are the property of their respective owners, used here only to identify each partner programme. Nothing here implies that any of them endorses our services.