A client situation
1,600 engineers. One platform nobody had looked at closely in years.
A large UK public sector research organisation had been running GitLab Community Edition for years. Over 1,600 engineers depended on it daily. The problem was that nobody had looked closely at the platform itself in a long time — and the gap between what they had and what they needed had quietly grown into something significant.
What the Health Check found was a platform under strain. The GitLab instance was several major versions behind current release — meaning security patches hadn't been applied, modern features were unavailable, and the organisation had no access to AI-assisted development capabilities that their licence should have entitled them to. Performance was degrading under load. CI/CD runners were fixed in capacity and couldn't scale to meet demand. Storage limitations were forcing teams to work around the platform rather than with it. Security scanning was largely absent. And critically — secrets and environment variables were scoped so broadly that any repository contributor could access sensitive production configuration.
Across six different engineering teams, the same pattern emerged. Strong technical capability in the teams themselves. An infrastructure that was quietly holding them back.
— Head of Engineering, UK Public Sector Research Organisation
The result
A prioritised roadmap covering infrastructure, security, access controls, and AI readiness — in the right order, without guesswork.
Same pattern across every team: strong engineers held back by platform infrastructure nobody had reviewed.