Managed GitLab Hosting

We operate the GitLab instance as a production service: monitoring, backups, updates, incident handling, and platform operations. You own the GitLab configuration and day-to-day usage.

We host the instances in our b'nerd Public Cloud on our own hardware in a data center with VK4 in Munich, Germany.

Each customer gets an isolated GitLab instance. Depending on tier, parts of the underlying infrastructure may be shared or dedicated (e.g. resources, networking, HA setup).

Of course. Upon request, we can run your GitLab instances on a cloud provider of your choice (AWS, GCP, Azure, Hetzner, …) or on-premises in your own data center.

Yes. We and our data center partners are ISO 27001 certified.

We can operate GitLab Community Edition (CE) or GitLab Enterprise Edition (Premium/Ultimate licenses). Updates are performed in defined maintenance windows; security fixes follow the agreed patch policy.

We announce regular maintenance windows in advance. Updates are performed in a controlled way to avoid version drift; emergency security updates follow the agreed timelines (tier-dependent).

Incidents are handled via defined escalation paths and response times (SLA). Communication can happen via email/phone and, on request, via Slack Connect.

Our company is based in Hamburg, Germany.

Yes, of course! Please coordinate this with our support team.

Yes. We operate GitLab behind HTTPS/TLS. Certificate handling depends on your requirements (managed certificates or customer-provided certificates).

No. A GitLab license is not required for the Community Edition (CE). For additional features, you can purchase GitLab Premium and Ultimate licenses through us.

Yes. Each GitLab server is connected via a dedicated public IPv4 address, and SSH for Git operations is available on port 22.

Of course, we provide regular updates. With Managed Hosting, all updates are included. We will notify you in advance via email about any upcoming updates and when they will be performed.

We create regular backups of the data (once daily), encrypt them, and store them at an external location in Germany. Please contact support if you need to restore one of these backups.

Retention and restore objectives depend on your tier and setup. As a baseline we run daily backups; for stricter RPO/RTO or additional restore testing, we define this explicitly with you.

We store the backups on our S3-compatible object storage. We can grant you access to this so you can retrieve the backups yourself. This service is included from the Professional Package onward (for Startup 49€/month). Other backup solutions (Push/Pull) are possible. Just reach out to us.

Yes. We support structured offboarding: exports/backups, a handover window, and deletion of the instance after confirmation. Details depend on the data volume and tier.

Yes, additional storage can be added to any package in increments of 100 GB for 12€/month.

Git repositories use the instance storage. Artifacts/registry/packages can be backed by S3-compatible object storage depending on your configuration and tier.

With the GitLab Community Edition, there is no limit to the number of users. You can create as many users and groups as you need. With the Enterprise Edition, Premium or Ultimate licenses apply, and there are license costs for each user created. Please note that these are annual licenses.

No. You can create as many repositories as you need.

We have a Fair Use Policy of at least 1 or 2 TB per month (outgoing) per GitLab instance. This is a soft limit. Data traffic between GitLab instances and GitLab runners is, of course, included.

Yes, our GitLab Managed Hosting supports Single Sign-On (SSO). This allows your team members to log in securely using their existing credentials, improving usability and simplifying credential management. We support a variety of SSO providers, including but not limited to Google, GitLab & GitHub, OpenID Connect, and Azure Active Directory.

You control user and admin permissions inside GitLab. Operational access by b'nerd is restricted to what is necessary for service operation and troubleshooting, and follows documented processes.

Yes. Depending on your tier, we can implement network restrictions such as IP allowlists and private connectivity options.

We continuously monitor the service. Depending on tier, we can provide operational visibility (dashboards/alerts) and agreed reporting.

Basic support is included in all our Managed Hosting offerings. Additional support can be agreed upon on a contract or project basis. Talk to us about your specific needs.

Our support team is happy to help: support@bnerd.com. We can also schedule a short technical call to clarify scope, SLAs, and migration details.

Of course, we can migrate an existing GitLab installation to us. We are happy to assist you actively in migrating the instance. Before the final migration, we will update your instance to the latest version.

We plan the target setup, perform test migrations where needed, and execute a controlled cutover. Scope can include projects, groups, users, runners, and data transfer—depending on your source system and constraints.

Downtime depends on data volume and source setup. We aim for a predictable maintenance window for the final cutover and clarify expectations during planning.

With monthly payment, the contract duration is one month. With annual payment in advance (including 15% discount), the contract duration is one year.

Changing the package is of course possible at any time (upgrades/downgrades). For downgrades, we will first check whether this is possible without issues (e.g., sufficient storage available, etc.).

Yes. For business customers we provide the contractual documents typically required for GDPR (including a data processing agreement where applicable).

We support data export/offboarding and then delete the instance after confirmation. Any retention or additional requirements are handled contractually.

Various payment methods are available for our Managed GitLab services. Payments can be conveniently made by direct debit, credit card, or invoice.