A client situation
Version 14. Ageing hardware. A team that didn't want to become GitLab administrators.
A financial services organisation was running GitLab on-premises at version 14. The hardware was ageing, the instance was unreliable, and developers were feeling it every day — slow builds, unexpected downtime, a platform that was supposed to accelerate delivery but was getting in the way of it. Security patches weren't being applied. The latest GitLab features, including AI functionality, were out of reach. And underneath it all, an undetected HTTP vulnerability was sitting open in their network.
OTTRA took on the full upgrade journey. Starting at version 14, we brought the instance up to the latest GitLab release — restoring security patch coverage and unlocking AI features without any increase in licensing costs. We then established a rolling 12-month upgrade programme: secure, repeatable, zero-touch upgrades delivered via a dedicated runner connected to the customer's infrastructure. The customer retains full control over when upgrades run. OTTRA provides hypercare support throughout and can roll back instantly if anything unexpected occurs.
During the process we identified and resolved the HTTP vulnerability in their network — a security hole that had gone unnoticed — and recommended migrating from a High Availability configuration to a Geo instance on AWS reference architecture, significantly reducing monthly infrastructure costs while improving reliability.
— Financial Services Organisation
The result
Security patches restored, AI features unlocked, and a rolling 12-month programme established — all without increasing licensing costs.
Consume GitLab, don't run it. No maintenance burden. No version debt. No surprise outages.