Managed GitLab Hosting
Your own GitLab instance on dedicated hardware in Frankfurt am Main. We install updates as they come out, and when something breaks you reach engineers who know your setup.
What teams ask before moving
These six points come up in almost every first conversation.
More about the data center in Frankfurt am Main where your instance runs.

What we maintain on your GitLab
Day to day, the Omnibus package, the registry and the runner connection cause most of the work. That is the part we take over, on dedicated hardware in Frankfurt.
Your own GitLab instance
No shared platform: your GitLab runs isolated on its own resources, without user or repository limits.
Omnibus updates & patches
We roll out GitLab releases in a controlled way and close security-critical gaps quickly, outside your working hours on request.
Repos & registry in Frankfurt
Repositories, container registry and CI artifacts on our own hardware in Frankfurt am Main, with a data processing agreement on request.
Git and registry uptime
We monitor Git, web and registry availability and step in before clone, push or pipelines stall.
Encrypted backups
Daily, encrypted backups at a second location in Germany. We handle restores for you on request.
Admin, SSO & own domain
Your own domain, SSO via Google, GitHub, OpenID Connect or Azure AD and full admin access. You manage projects, we run the platform.
Your GitLab, without platform upkeep
You want to use repositories, CI/CD and the registry, not run Omnibus updates and runners yourself. We handle installation or migration, updates, monitoring and support for your GitLab.
Self-hosted GitLab otherwise means the Omnibus package, PostgreSQL, Redis, container registry, runners and backups. With us your instance runs on dedicated hardware in Frankfurt am Main, with your own domain and full admin access.
You manage projects, groups and pipelines. Omnibus updates, PostgreSQL, Redis, the registry and backups are on NETZFABRIK.
Is it worth the effort?
GitLab is free, running it is not: updates, runners, backups and monitoring tie up your team. We deliver the ready-to-run instance at clear package prices.
| Self-hosted | NETZFABRIK Managed | |
|---|---|---|
| Setup & configuration | Several days of your own work | We set it up, included in the price |
| Updates & security patches | You have to keep track yourself | Handled automatically by us |
| Monitoring & alerting | Set up and maintain yourself | 24/7, included |
| Backups & recovery | Set up and test regularly yourself | Regular and tested |
| Scaling & availability | Requires your own expertise | Included on request |
| Support & response time | Community and self-research | Dedicated contact, clear SLA |
| Data location | Your responsibility | Frankfurt am Main, GDPR-compliant |
| Your time investment | Several hours per month | Hardly any, we do the running |
Three plans, by instance size
Managed monitoring and S3 caching are included in every plan. The plans differ in CPU, RAM, SSD and traffic.
1. Choose a plan
2. Add extras
3. Extend S3 caching
None of them fits? Then we put together dedicated hardware based on your user count and repositories.
Add runners and Kubernetes
Add Managed GitLab Runner
You can book the runners for your pipelines with us as well. We keep them updated and add more when you need them. Docker is supported, and up to 100 GB of cache come at no extra cost.
If your GitLab runs with us too, runner and instance are connected at up to 10 Gbps. We handle updates and caching.
GitLab on Kubernetes
If your setup needs high availability or dynamically scaling runners, we also run your GitLab on Kubernetes. We advise you on what actually makes sense for your environment.
Response times for your GitLab
In the event of a system outage, we respond in under 15 minutes, 24/7, 365 days a year.
- Critical (P1)< 15 min
Total outage or suspected security incident. Please call.
24/7 on-call
- High (P2)< 1 hr
Important function disrupted, operations run with limits.
Mon to Fri, 9 am to 6 pm
- Normal (P3)< 4 hrs
One workstation affected or there is a workaround.
Mon to Fri, 9 am to 6 pm
- Low (P4)< 1 business day
Questions, requests and anything that can be planned.
Mon to Fri, 9 am to 6 pm
Contractually fixed in the SLA. The DPA is available before signing.
Questions about GitLab with us
Sorted by operation, access, resources, licensing and backups.
General & operation
Can I use my own domain?
Is the hosting GDPR-compliant?
Where are the servers?
Is my instance dedicated or shared?
How does onboarding work?
How do maintenance and updates work?
Features, integrations & access
Do I get full admin access?
Can I use GitLab Pages?
Do you support Single Sign-On (SSO)?
Can I connect my own GitLab Runners?
Can I add Managed Runners?
Can I use Git over SSH?
Do you support other cloud providers?
Do you offer macOS Runners?
Can I restrict access (IP / VPN)?
Resources, scaling & storage
Are there user or repository limits?
How far can GitLab scale?
Where are artifacts, registry and packages stored?
Can I add storage?
Licenses & editions
Do I need a GitLab license?
Do you offer Premium and Ultimate licenses?
What's the difference between CE and EE?
Backups & security
