GitLab Self-Managed

Source control and CI/CD on infrastructure you operate.

  • AWS
  • Azure
  • Google Cloud
  • Oracle Cloud
  • Alibaba Cloud
Customer-operated Servers / containers Open Source / Open Core

8 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

GitLab bundled Git command-execution advisory

CVE-2026-105437 concerns a Git heap-write flaw that can reach command execution inside Gitaly.

Scope: GitLab CE/EE 16.2 to before 19.3.8, 19.4 to before 19.4.6, and 19.5 to before 19.5.4.

All installation types are covered unless the vendor identifies an exception. Source builds need both Gitaly-embedded Git and git.bin_path checked.

Action: Install the patched release for the deployed branch. Rebuild the required Git binaries for source installations, or use a distribution fix for the CVE.

Primary source · Reviewed 2026-11-17

GitLab 19.5.6 security update

GitLab 19.5.6, 19.4.8, and 19.3.9 fix a high-severity cross-site scripting issue and authorization weaknesses in CI/CD and workspaces.

Scope: GitLab CE/EE patch lines 19.3, 19.4, and 19.5; consult the vendor table for the affected versions.

Impact depends on enabled features, user roles, and exposed endpoints. This record does not replace the separate bundled-Git CVE review.

Action: Upgrade to 19.5.6, 19.4.8, or 19.3.9 for the deployed branch, or a later supported patch.

Primary source · Reviewed 2026-11-18

GitLab critical bundled Ruby security update

GitLab updated bundled Ruby for CVE-2026-132825 and related upstream Ruby security issues.

Scope: Self-managed GitLab CE/EE releases before 19.4.10, 19.5 releases before 19.5.8, and 19.6 releases before 19.6.1, per GitLab.

Official Linux packages and container images carry the fixed Ruby. Self-compiled installations manage Ruby separately.

Action: Upgrade to 19.6.1, 19.5.8, or 19.4.10 as appropriate. For source builds, rebuild GitLab’s Ruby with 3.3.14, 3.4.13, or a later patch in the same minor series.

Primary source · Upstream Ruby security advisory · Reviewed 2026-11-20

What lands where

  1. Supplied by

    Vendor or project

    Linux package, container or Helm chart

  2. Operated by

    Your team

    Your team operates, upgrades and backs up the installation.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodLinux package, container or Helm chart
InfrastructureServers / containers
The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.
Licensing modelOpen Source / Open Core
Community Edition uses MIT terms; Enterprise Edition adds components under a more restrictive commercial license.
LicenseFree and paid tiers

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

10 of 12 fields researched (83%) · 10 documented · 0 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery

GitLab documents AWS Marketplace self-service/private offers and Google Cloud Marketplace private offers for paid subscriptions. Delivery/billing does not by itself change where a selected GitLab installation runs.

Premium/Ultimate subscription procurement; self-hosting and SaaS offers must be distinguished · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

Cloud commitment eligibility
Edition-dependentEvidence and scope for Cloud commitment eligibility

GitLab states eligible cloud-marketplace purchases can count toward committed spend on AWS or Google Cloud. Confirm the specific offer, billing account and buyer agreement; this is not an unconditional credit guarantee.

Vendor procurement statement; actual provider commitment terms govern eligibility · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

Instance-wide SAML SSO is documented for Self-Managed Free, Premium and Ultimate. Group SAML and advanced group mapping have separate tier requirements.

GitLab Self-Managed instance authentication; not GitLab.com group SSO · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning

SCIM is documented for Self-Managed Premium and Ultimate, with SAML configured. The API implements part of RFC7644; verify the supported identity provider and operations.

GitLab Self-Managed / Dedicated, Premium and Ultimate · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.

GitLab Self-Managed CE/EE, including Linux packages, containers and self-compiled installations. The separate bundled Git fix has its own requirements. · Source ↗ · Upstream Ruby security advisory ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Air-gapped operation
Edition-dependentEvidence and scope for Air-gapped operation

Self-Managed Free, Premium and Ultimate have an offline installation workflow. Transfer the correct packages/images and handle scanners, AI and update dependencies separately.

Documented offline Self-Managed configuration, not default online installation · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official self-managed guide publishes Compose YAML for versioned Community or Enterprise images with persistent configuration, logs and data. It warns against placing the all-in-one Docker image in Kubernetes; use the Helm chart/operator there. Configure hostname, TLS, secrets, backups and runner capacity separately.

Official self-managed Docker/Compose installation · Source ↗ · Deployment artifact ↗ (Select explicit version-ce.0 or version-ee.0 image tag) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The single-node baseline is 8 vCPU and 16 GB RAM. A memory-constrained configuration can use at least 8 GB; distributed sizing is component- and workload-specific.

Self-Managed single-node baseline; not a total production cost estimate · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

GitLab Self-Managed offers tier-based subscriptions applying to the whole instance; all instance users share the selected features. A GitLab.com subscription cannot be transferred to Self-Managed. Select the required tier, seats and add-ons; this does not establish a complete hosting/support cost.

GitLab Self-Managed instance-wide commercial tiers · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

GitLab published 19.6.1 on November 20, 2026, with parallel Ruby security patches 19.5.8 and 19.4.10.

GitLab Self-Managed Community and Enterprise editions · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Show all fields (2 not researched)
Compliance attestations
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

GitLab documents AWS, Azure and Google Cloud installations. Oracle and Alibaba Cloud also publish deployment guides. These are documented deployment paths, not a promise of identical support or feature availability. Check operating system, edition and region requirements. GitLab 19.5.4, 19.4.6, and 19.3.8 patch critical CVE-2026-105437 in the bundled Git. Affected self-managed versions are 16.2 through versions before 19.3.8, 19.4 before 19.4.6, and 19.5 before 19.5.4. Upgrade immediately. Self-compiled deployments must also rebuild the Git binaries embedded in Gitaly and the Git installation referenced by git.bin_path, or use a distribution-patched Git 2.56.1 or later. GitLab 19.5.6, 19.4.8, and 19.3.9 address a high-severity cross-site scripting issue plus CI/CD and workspace authorization flaws. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.

Category fit

DevOps
Source control and CI/CD on infrastructure you operate.

Compare within DevOps

  • Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
    • AWS
    Customer-operated · Open Source / Open Core
  • Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
    • Azure
    Customer-operated · Commercial Only
  • Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
    • AWS
    • Google Cloud
    Customer-operated · Commercial Only
  • CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
    • Railway
    Customer-operated · Open Source / Open Core
  • HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only

Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • GitLab Self-Managed cloud installation guides ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The upstream installation index links full GitLab Self-Managed deployment on AWS, Azure and Google Cloud. Choose the Linux package, chart or reference architecture appropriate to the selected edition, scale and supported release; a GitLab Runner alone is not the GitLab application.

    • GitLab Community Edition on Alibaba Cloud ECS ↗ · Alibaba Cloud

      Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      Alibaba documents GitLab Community Edition Docker deployment on Alibaba Cloud Linux 3 ECS as well as older package-based examples. Use the Community Edition path for this listing; JiHu GitLab is a separately distributed edition and old CentOS examples are not a current production recommendation.

    • Oracle GitLab application deployment in an OCI tenancy ↗ · Oracle Cloud

      Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      Oracle explicitly documents the GitLab application VM, customer tenancy, region, compartment, compute and VCN configuration, and administrator login. This confirms the provider deployment model. Its linked quick-start architecture has been retired, so these instructions do not establish a currently maintained one-click stack; validate the installer and supported GitLab release before using the legacy automation.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory