GitLab Partner & Reseller

GitLab licenses, self-managed GitLab, CI/CD and operations from Munich, Germany

Why GitLab?

One platform for code, CI/CD and security

GitLab is a DevSecOps platform that combines Git version control, merge requests, issue tracking, CI/CD pipelines, a container registry and security scanning in a single application. It runs as self-managed GitLab on your own infrastructure, as GitLab Dedicated or as SaaS on GitLab.com. ventx is a GitLab partner and reseller based in Munich, Germany, serving customers across Germany, Austria and Switzerland.

From us you get GitLab licenses, advice on tier and user count, the installation of self-managed GitLab, the implementation of your CI/CD pipelines, upgrades and operations, and the migration from Jenkins, GitHub, Bitbucket or Azure DevOps from a single source – on site, in Munich or remotely. Your point of contact is someone who runs GitLab, not just sells it.

GitLab licenses from GitLab partner and reseller ventx

Premium and Ultimate – self-managed, GitLab.com and GitLab Dedicated

GitLab comes in three tiers: Free, Premium and Ultimate. As a GitLab reseller we sell Premium and Ultimate subscriptions for self-managed GitLab and GitLab.com; GitLab Dedicated is available on request. It is the same license as buying direct – plus the advice that keeps you from buying Ultimate for a Premium-sized problem.

GitLab Free

Git repositories, merge requests, issues, CI/CD, container registry and basic SAST – no subscription needed. If Free or the Community Edition covers your needs, you need neither a quote nor us, and we will say so.

GitLab Premium

For teams that need merge request workflows with approval rules and code owners, merge trains, protected environments, epics and roadmaps for team project management, and Priority Support. USD 29 per user per month, billed annually (USD list price, as of September 2026).

GitLab Ultimate

Everything in Premium plus application security testing beyond basic SAST (DAST, dependency scanning), vulnerability management, software supply chain security, compliance frameworks and governance, portfolio management and unlimited guest users. Price on request.

Self-managed, GitLab.com or GitLab Dedicated?

  • Self-Managed GitLab: runs wherever you install it – in your own data center, on AWS, Azure, Google Cloud or STACKIT; full control over data, network and upgrade timing, operated by you or by ventx. Licensed via activation code (cloud licensing).
  • GitLab.com: operated by GitLab, the least operational effort; the subscription is assigned to your top-level group.
  • GitLab Dedicated: single-tenant instance in the AWS region of your choice, Ultimate only and meant for large installations – GitLab sets the minimum size.

Advice on tier and seat count. GitLab licenses per user (seat) and bills annually. Before we write an offer, a 20-minute call settles the variant, Premium or Ultimate, the user count including guests, service accounts and growth until renewal, your need for GitLab Duo and when existing licenses end. Do you need security scanning beyond basic SAST and compliance evidence in your day-to-day pipelines? Then Ultimate. Are CI/CD, planning and Priority Support enough? Then Premium – many teams are well served by it.

Offer and order handling through ventx. You receive the offer and the invoice from ventx GmbH; it is based on GitLab list prices per user per year, your user count, your term and GitLab Duo as a separate line. Our compensation as a GitLab partner is settled with GitLab, not with you; you see a final price with no hidden line items. GitLab bills annually by default; multi-year terms, EUR billing and payment schedules are possible in principle – which of them you can get depends on GitLab's approval, and we tell you upfront. One point of contact in Munich for contract, technical and billing questions, on top of GitLab Priority Support per your plan.

Renewal support. Before every renewal we review actual seat usage, tier and Duo needs with you so the renewal matches real usage. How the transition from an existing GitLab contract works is agreed with GitLab and stated in the offer – and if switching brings no benefit, we will tell you. As of September 2026: GitLab Duo Core is included with Premium and Ultimate from GitLab 18.0 (Code Suggestions; Agentic Chat from GitLab 19.0); agentic features are usage-based and paid with GitLab Credits, Duo Pro and Duo Enterprise remain per-user add-ons. GitLab adjusts its Duo packaging regularly; we will tell you where things stand.

Self-managed GitLab: setup and installation

GitLab installation by reference architecture – on-premises, on Kubernetes or in the cloud

We install self-managed GitLab the way GitLab documents it: following the reference architecture for your user count, with tested backups, single sign-on and a runner fleet that fits your pipelines. Whether a single server in your data center, a highly available multi-node setup or a cloud-native deployment on Kubernetes – we build the setup your size and your availability requirements actually need.

Linux package or Helm chart

The Linux package (Omnibus) bundles all components for servers and VMs – on Proxmox, VMware, EC2 or bare metal. The GitLab Helm chart deploys the stateless services on Kubernetes (EKS, AKS, GKE, STACKIT SKE or on-premises), while Gitaly and PostgreSQL run outside the cluster as GitLab recommends (cloud native hybrid).

Reference architecture by user count

GitLab documents reference architectures from a single server for up to 1,000 users via 2,000 and 3,000 up to 5,000, 10,000 and more users. We size according to your user count, your pipeline load and your repository size – and no larger than necessary.

High availability

For HA setups we separate the components: PostgreSQL with Patroni and PgBouncer, Redis with Sentinel, Gitaly Cluster with Praefect for the Git data, Consul for service discovery, a load balancer in front of the Rails nodes and S3-compatible object storage for artifacts, LFS, uploads, packages and the container registry.

Backup & restore

Regular backups of database, repositories and object storage, configuration and secrets (gitlab-secrets.json) backed up separately, retention according to your policy – and a restore we have actually tested before you need it.

SSO with SAML, OIDC or LDAP

Integration with Entra ID, Okta, Keycloak or Active Directory via SAML, OpenID Connect or LDAP, group synchronization (Premium and up), two-factor authentication and a role and permission concept across groups, projects and protected branches.

GitLab Runner, registry & monitoring

GitLab Runner with the Kubernetes executor, the Docker executor or autoscaling on EC2 (including spot instances), runner tags and resource limits per job; the built-in container registry with cleanup policies; metrics via Prometheus exporters and Grafana dashboards, alerting and central logging.

Operations, upgrades and GitLab support

Managed GitLab from Munich – your instance up to date, backed up and monitored

GitLab publishes a new release every month and a new major version once a year; patch releases with security fixes appear in between. If you postpone upgrades for too long, you later have to step through several intermediate versions along the upgrade path GitLab prescribes and wait for background migrations to finish. We plan every GitLab upgrade in advance, review release notes and deprecations, test it on a staging instance and roll it out in the agreed maintenance window – as a zero-downtime upgrade on multi-node setups, with a short, announced interruption on single servers.

With managed GitLab, ventx takes over the day-to-day operation of your self-managed GitLab instance: monitoring and alerting, incident response, monthly upgrades and security patches, backups with regular restore tests, capacity and cost control, and the operation of your runner fleet including autoscaling and runner upgrades. Security hardening is part of it: TLS configuration, access protection for the admin area and the API, rate limits, secret rotation and regular reviews of the instance settings. The scope is defined together in a service level agreement that matches your requirements for response and support hours – terms on request.

Customers with a Premium or Ultimate subscription keep GitLab Priority Support per their plan. For issues that lie in the product itself we open the ticket with GitLab, supply logs and a reproduction and stay on it until it is resolved – you have one point of contact in Munich who knows your environment. We offer GitLab support and managed GitLab to customers across Germany, Austria and Switzerland.

CI/CD with GitLab: implementation

Pipelines your team understands and can evolve

A GitLab license alone does not ship anything faster. Our DevOps engineers in Munich design and implement GitLab CI/CD pipelines for applications, containers and infrastructure – traceable, reusable and without access keys in CI variables.

  • Pipeline design: stages, rules and caches, parent-child and merge request pipelines, environments and deployments with approvals, review apps.
  • CI/CD components and templates: reusable building blocks in your instance's CI/CD catalog so teams do not reinvent every pipeline.
  • OIDC to AWS, Azure and Google Cloud: short-lived tokens instead of stored access keys – as described in our posts Connect your GitLab CI/CD pipeline to AWS via OIDC and OIDC with id_tokens.
  • Infrastructure as code: Terraform and OpenTofu pipelines with plan review in the merge request, GitLab-managed state and separate environments.
  • Container builds and registry: reproducible image builds, tagging strategy, cleanup policies and signing.
  • Dependency updates with Renovate: automatic merge requests for dependencies, base images and Terraform providers – see Run Renovate in self-hosted GitLab CI.
  • Security scanning: SAST, secret detection and container scanning in every tier; DAST, dependency scanning, the vulnerability report and compliance pipelines as Ultimate features – see GitLab Ultimate in practice.
  • GitOps handover to Argo CD or Flux: the pipeline builds and tests, the GitOps controller deploys – see Argo CD app of apps and Flux image update automation with the GitLab container registry.

Read more about our DevOps offering under DevOps services and, if your pipelines deploy to Kubernetes, under Kubernetes support.

Migration to GitLab

From Jenkins, GitHub, Bitbucket or Azure DevOps – and between GitLab.com and self-managed

For GitHub and Bitbucket, GitLab ships importers that take over repositories with their history, pull requests, issues and users as far as the source APIs allow; Azure DevOps repositories come in via Git import, and there is no Jenkins importer. We do the rest: translating Jenkinsfiles and workflows to GitLab CI/CD, setting up runners, mapping permissions and group structure, moving integrations such as Jira, Slack or Artifactory.

The move between GitLab.com and self-managed GitLab is a GitLab migration with its own tooling, too: groups and projects move in either direction via direct transfer or project export, including issues, merge requests and CI/CD configuration. Going from the Community Edition to Premium or Ultimate, on the other hand, is not a migration but a license upgrade: switch the instance to the Enterprise Edition packages, enter the activation code – your data stays where it is.

Every migration gets a cut-over plan: an inventory of repositories, pipelines and integrations, a test migration with reconciliation, a freeze of the source, the final move and a window in which both systems stay readable. The order is always the same: decide on tier and user count first, then buy, then migrate. If the new instance runs in the cloud, we plan it together with our cloud migration service.

GitLab training, workshops and hands-on articles

Knowledge that stays with your team

We train your team in GitLab CI/CD and pipeline design, in administering self-managed GitLab (upgrades, backups, runners, SSO) and in the DevSecOps features of Ultimate – as a one-day workshop on your own repositories or as a multi-part series, on site, in Munich or as a webinar. The goal is that your team evolves the platform on its own afterwards and only calls us when it makes sense.

Hands-on articles by our engineers

Frequently asked questions

Is ventx a GitLab partner and reseller?

Yes. ventx GmbH, based in Munich, is a GitLab partner and reseller in Germany, Austria and Switzerland and is listed in the GitLab partner directory. We sell GitLab Premium and Ultimate subscriptions and deliver consulting, installation, CI/CD implementation, operations and training on GitLab CI/CD, administration and the DevSecOps features of Ultimate from a single source – on site, in Munich or remotely.

Which GitLab licenses can I buy through ventx?

GitLab Premium and GitLab Ultimate as subscriptions for self-managed GitLab and for GitLab.com; GitLab Dedicated (single-tenant, Ultimate only) on request. It is the same license as buying direct: for self-managed you receive an activation code (cloud licensing), on GitLab.com the subscription is assigned to your top-level group. GitLab Free and the Community Edition need no license – and no quote from us.

Self-managed GitLab or GitLab.com – which one fits us?

GitLab.com means the least operational effort; GitLab operates the platform. Self-managed GitLab means full control over data, network, integrations and upgrade timing – operated by you or by ventx. GitLab Dedicated is single-tenant in the AWS region of your choice, Ultimate only and meant for large installations; GitLab sets the minimum size. Which variant matches your compliance requirements is something we clarify before the offer. We install self-managed GitLab in your own data center, on Proxmox or VMware, on AWS, Azure, Google Cloud and STACKIT – as the Linux package (Omnibus) or via the Helm chart on Kubernetes, following the GitLab reference architecture for your user count, including backup, SSO, runners and monitoring.

How much does GitLab cost?

GitLab licenses per user (seat) and bills annually. The official tiers are Free, Premium (USD 29 per user per month, billed annually, USD list price) and Ultimate (price on request) – as of September 2026. Through ventx you receive an offer based on GitLab list prices, your user count and your term; consulting, migration and operations are separate, clearly itemized services. Get in touch for a quote.

Does ventx take over GitLab upgrades and operations?

Yes. With managed GitLab, ventx runs your instance day to day: monthly GitLab upgrades along the upgrade path, security patches, backups with restore tests, monitoring and the operation of your runner fleet. Scope and service levels are defined individually in a service level agreement – terms on request. GitLab Priority Support per your plan remains available to you on top.

Does ventx migrate from Jenkins, GitHub or Bitbucket to GitLab?

Yes. For GitHub and Bitbucket, GitLab ships importers for repositories, pull requests and users; Azure DevOps repositories come in via Git import; there is no Jenkins importer. We do the rest: translating pipelines to GitLab CI/CD, setting up runners, mapping permissions and group structure, moving integrations. We also handle moves between GitLab.com and self-managed GitLab and the license upgrade from the Community Edition.

Ready for GitLab?

Contact us for a quote or a personalized consultation.
Get in Touch Now