Where GitLab runs
Who operates each part
GitLab.com or
GitLab Dedicated
Shared SaaS or a single-tenant instance
- Who hosts
- GitLab
- Who operates
- GitLab
- Where OTTRA helps
- Configuration, pipelines and migration
Managed Services
Cloud Choice™Managed GitLab and Claude, where you need them.
Choose where GitLab runs, how engineers access AI tools and which operations OTTRA takes on. Keep data, access and ownership clear.
You choose the setup. We agree our operating scope with you.
Meet a platform specialist
David Tacheny
CTO, Enterprise DevSecOps and AI
Enterprise platforms, secure delivery and AI workflows.
Meet David
Meet a platform specialist
Nick Lotz
DevSecOps Lead
DevSecOps, infrastructure automation and AI workflows.
Meet NickYour working setup
Make three clear decisions.
Choose where GitLab runs
Compare hosting, operations and where OTTRA helps.
GitLab.com or
Your Cloud
- Who hosts
- A cloud account you own
- Who operates
- OTTRA, within the agreed scope
- Where OTTRA helps
- Monitoring, maintenance and upgrades
Our Cloud
By enquiry
- Who hosts
- A provider agreed with OTTRA
- Who operates
- OTTRA, subject to the agreed setup
- Where OTTRA helps
- Hosting location and operating responsibilities
Choose how you access Claude
Claude access is a separate choice from GitLab hosting.
Engineer
Prompt + allowed context
Response for review
Model serviceClaude Enterprise
Access Claude Code through Anthropic’s hosted service, with central sign-in and user controls.
Your Cloud
Use a supported provider in your cloud account, such as Amazon Bedrock. Verify model and endpoint availability, authentication, routing, data handling and billing before integration.
Our Cloud
For an OTTRA-hosted platform enquiry, scope the connection to a Claude provider. Agree who operates it and where the provider processes requests.
The operating agreement
Agree who operates each part.
Hosting and operations are separate decisions. Record the owners before work starts.
- Your team
- Sets priorities, acceptance criteria and approval for significant changes.
- OTTRA
- Owns the configuration, maintenance and operating work in the agreed scope.
- Provider
- Supplies hosting or model services under the selected provider’s terms.
Zero-touch operations. You stay in control.
When OTTRA operates GitLab for you, your engineers don’t need to touch the routine operating work. We run monitoring, maintenance and monthly upgrades through automated, repeatable pipelines, with rollback ready at every step.
Your team still sets the maintenance windows, approves significant changes and decides on recovery. Zero-touch means no operating work for your team. It doesn’t mean decisions are made without you.
Applies to GitLab that OTTRA operates in your cloud account or ours. On GitLab.com and GitLab Dedicated, GitLab operates the platform.
Service levels when OTTRA operates GitLab
For managed GitLab in your cloud account, or in ours by enquiry.
- Uptime SLA
- 99.9%
- For the managed GitLab infrastructure.
- Critical response
- 1 hour
- When GitLab is completely unavailable, with a 4-hour resolution target.
- Major response
- 4 hours
- When major functionality is affected, with an 8-hour resolution target.
- Monitoring
- 24/7
- Prometheus and Grafana dashboards, early-warning alerts and first-line support from GitLab specialists.
- Upgrades
- Monthly
- On the latest supported GitLab release, in agreed maintenance windows, with rollback ready at every step.
Sovereignty by design
Start with the control your organisation needs. UKAI’s sovereignty framework considers ownership, autonomy, control and resilience: the ability to govern and sustain essential AI, beyond a data centre’s address. Read UKAI’s framework.
UK-hosted platforms
Choose UK locations for repositories and backups. Establish access and operating ownership. Check each AI service’s processing and storage route separately.
UK-controlled AI infrastructure
Consider UK-controlled compute with a model licensed for deployment there. Establish who administers it, manages updates and can sustain or move the service.
Customer-controlled private AI
Run a suitable deployable model in an agreed private or on-premises environment. Balance control against hardware, engineering capability, model performance and ongoing operations.
These are options to assess with you, with provider availability and OTTRA’s scope agreed for the work. Civo’s public and private AI infrastructure is one current provider example.
Check the Claude route separately
GitLab hosting does not determine Claude’s inference location. Check the provider, model, endpoint, routing, retention and terms. AWS distinguishes in-region, geographic and global inference: check current model and regional availability.
Start the conversation
Luke Burgess
Account Executive
Understanding the problem before anyone proposes a platform.
Meet LukeNot sure which setup fits yet? That is the right place to start. Luke maps where your code and AI need to run, what has to stay under your control and which trade-offs matter, then brings in the engineers who will build and operate it.
Talk to Luke about your platformFind the right setup.
Bring your current platform and the work you want OTTRA to manage. We agree scope, timing and cost before work starts.
