GitLab

A Git forge sold as one application for the whole software lifecycle, from issues and merge requests to built-in CI/CD, packages and security scanning, that you can use on GitLab.com or run yourself.

What it is: Version control
Used for: CI/CD pipelines,Issue tracking
Type: Commercial product
Made by: GitLab Inc.
License: Open core: MIT for everything outside the ee/ directory (the Community Edition); ee/ is under the proprietary GitLab Enterprise Edition license and needs a paid tier
Facts checked: 20 October 2026

What it is

GitLab is a Ruby on Rails application served by Puma, with Sidekiq running background jobs from a Redis queue. It doesn’t touch repositories directly: every Git operation goes through Gitaly, a separate service written in Go, built so large installations no longer need repositories on shared NFS. GitLab Shell handles git over SSH, Workhorse, a reverse proxy, takes load off Puma, and PostgreSQL, the only supported database, holds users, issues, merge requests and permissions. A self-managed single server starts at 8 vCPUs and 16 GB of memory.

What sets it apart is scope. Issues and boards, merge requests (GitLab’s name for pull requests), CI/CD from a .gitlab-ci.yml file, a package and container registry, security scanners and deployment tracking share one data model and one permission system, so a pipeline’s results, a vulnerability and the issue it fixes all appear on the merge request. Jobs run on GitLab Runner, an agent you install on your own machines or use hosted on GitLab.com. GitLab ships a new version on the third Thursday of every month and a major version every May; 19.5 came out on October 15, 2026.

The code is open core. Everything outside the ee/ directory is MIT and builds the free Community Edition; the ee/ features are proprietary and unlocked by the Premium ($29 per user a month) and Ultimate tiers. You can use it on GitLab.com, run it yourself, or rent GitLab Dedicated, a single-tenant instance GitLab runs for you. GitLab Inc. has been listed on Nasdaq since 2021, reported $955.2 million of revenue in its fiscal year to January 31, 2026, and says GitLab has more than 50 million registered users.

Why teams pick it

One product for the whole loop: code, review, CI/CD, packages and security scanning without wiring separate tools together
You can self-host all of it, CI included, from the free MIT-licensed Community Edition up to Ultimate
Open about how it works: the source code, the company handbook and even outage postmortems are public
A predictable cadence: a release every month on a fixed day, and a major version once a year in May

Watch out for

Heavy to run yourself: a single server starts at 8 vCPUs and 16 GB of memory, and needs PostgreSQL and Redis alongside
Team controls cost money: required approval rules, code owner approvals and merge trains are Premium or Ultimate only
The free tier on GitLab.com is small: 5 users per private top-level group, 400 compute minutes a month and 10 GiB of storage
Security fixes go only to the latest three monthly releases, so a self-managed instance must be upgraded every few months

Alternatives

What all version control have in common →Compare side by side →

JenkinsOpen sourceThe self-hosted automation server much of CI started on: a Java controller that hands jobs to agents, more than 2,300 plugins, and pipelines written as a Jenkinsfile.

GitHubCommercialThe largest Git host: repositories, pull requests, code review, issues and packages in one web service, owned by Microsoft since 2018 and used by more than 180 million developers.

BitbucketCommercialAtlassian’s Git host, built to sit next to Jira: pull requests, code review and Bitbucket Pipelines CI, as the Bitbucket Cloud service or the self-managed Bitbucket Data Center.

GiteaOpen sourceA lightweight, self-hosted Git forge in one Go program: repositories, pull requests, issues, a package registry and GitHub Actions-style CI, under the MIT license.

ForgejoOpen sourceA self-hosted Git forge, like a small GitHub you run yourself: repositories, pull requests, issues, a package registry and built-in CI in one Go program, developed by a community under the non-profit Codeberg e.V. as a hard fork of Gitea.

CodebergCommercialA public, non-profit Git forge for free and open-source projects, run on Forgejo by Codeberg e.V., a member-owned association in Berlin: repositories, issues, pull requests, CI, static pages and translations without a company behind them.

RadicleOpen sourceA peer-to-peer code forge built on Git: every user runs a node that stores and shares repositories, and issues, patches and reviews travel inside the repository as signed Git objects, with no central server.

How it fits with other technologies

What GitLab uses

What uses GitLab

A merge request from the terminal with the GitLab CLI · bash

git switch -c fix-login-timeout
git commit -am "Extend login session timeout to 30 minutes"

glab mr create --fill --reviewer alice --remove-source-branch --yes
# pushes the branch and opens a merge request against the default branch

glab mr approve 235          # a reviewer approves
glab mr merge 235 --squash   # auto-merges once the running pipeline succeeds

See it in a real stack

No architecture uses GitLab yet. Drop it into the playground and wire it up yourself.Open playground →

Where it came from2011–2026

Dmitriy Zaporozhets needed a good tool for his team to collaborate on code. Working from a house in Ukraine that had no running water, he decided the missing collaboration tool was the bigger problem, and with Valeriy Sizov he started GitLab: the first commit is dated October 8, 2011. Sid Sijbrandij found it in 2012, thought it natural that a tool for programmers should be open source, and started GitLab.com. In November 2012 Zaporozhets wrote the first version of GitLab CI.

In 2013 large organizations running GitLab asked for features they needed, Zaporozhets said he wanted to work on GitLab full time, and he and Sijbrandij introduced the paid Enterprise Edition. The company was incorporated in 2014 and went through Y Combinator in early 2015 with nine people. It stayed all-remote, and wrote down how it works in a public handbook.

That openness was tested on January 31, 2017, when an engineer wiped the production database directory on the wrong server and the backups turned out not to work. GitLab.com was down for about 18 hours and lost about six hours of database changes, and the team live-streamed the recovery on YouTube. GitLab Inc. went public on Nasdaq on October 14, 2021, priced at $77 a share and describing itself as “The DevOps platform, a single application.”

Why it’s built this way

One application instead of a toolchain: GitLab added CI in 2012 and then planning, packages, security and deployment to the same product, so teams share one data model, one interface and one set of permissions instead of integrating separate tools. It is how GitLab described itself when it went public.
Open core, split by who buys the feature: GitLab Inc. earns almost all its revenue from paid tiers. Its stewardship promises say a feature whose likely buyer is an individual contributor goes into the MIT-licensed core, one aimed at managers or executives is proprietary, open features are never moved to a paid tier, and features land in both editions at the same time.
Work in public: GitLab’s source code and company handbook are public. After the 2017 database outage it kept its recovery notes in a public document, live-streamed the work to about 5,000 viewers, and published a detailed postmortem.

Timeline

2011
Dmitriy Zaporozhets and Valeriy Sizov start GitLab in Ukraine (first commit October 8)
2012
Sid Sijbrandij starts GitLab.com; the first GitLab CI (November)
2013
GitLab Enterprise Edition introduced for larger organizations
2015
Graduates from Y Combinator in March with nine people
2017
GitLab.com database outage, recovered on a live stream (January 31)
2021
IPO on Nasdaq as GTLB (October 14)
2026
$955.2 million revenue in fiscal 2026 (March); GitLab 19.5 released October 15

Sources19 · facts checked 20 October 2026

Improve this page on GitHub