GitLab for financial services
Self-managed GitLab for banks and payment firms: SOX and PCI DSS change evidence, separation of duties, Geo for disaster recovery and keeping source code in-house.
GitLab for industries
Where self-managed GitLab deployments differ by sector because of regulation and network constraints.
GitLab for public sector
Self-managed GitLab for government agencies: air-gapped installation, offline security scanners, FIPS images and NIST SP 800-53 hardening guidance.
GitLab for healthcare and life sciences
Self-managed GitLab for healthcare software teams and life sciences: keeping code and pipelines in controlled infrastructure, approval re-authentication as an electronic signature and audit trails for regulated changes.
GitLab for SaaS and technology companies
Why SaaS companies self-manage GitLab: SOC 2 change evidence, runner cost control, data residency and scaling from one node to reference architectures as engineering grows.
GitLab for manufacturing and embedded software
Self-managed GitLab for manufacturers building embedded and industrial software: isolated plant networks, Windows and macOS runners for toolchains, large binary repositories and supply chain evidence.
GitLab for energy and utilities
Running GitLab inside utility and energy networks: offline and air-gapped operation, change control evidence for NERC CIP style programs and separating OT code from corporate systems.
GitLab for defense contractors handling CUI
Self-managed GitLab for defense industrial base suppliers: CMMC and NIST SP 800-171 scoping, FIPS images, offline licensing for Duo and keeping CUI repositories inside the enclave.
