skip to content

In GitLab, how do GitLab.com, Self-Managed and Dedicated differ, and which fits code that must stay in your own data centre?

level: juniorimportance: must knowfreq 44%

answer

  1. who hosts, who upgrades
  2. shared tenant versus single tenant
  3. subscription on a top-level group
  4. only one can run offline

basics

~20 s

GitLab.com is GitLab's shared multi-tenant SaaS, GitLab Dedicated is a single-tenant instance GitLab hosts and runs for you, and GitLab Self-Managed is the same product you install and operate. Only Self-Managed can sit in your own data centre.

solid answer

~40 s

All three run the same GitLab application; what differs is who hosts and operates it. **GitLab.com** is multi-tenant SaaS: a subscription applies to a top-level group, GitLab runs and upgrades the instance, and customers never get the **Admin** area. **GitLab Dedicated** is single-tenant SaaS on the Ultimate tier, hosted in a cloud region you choose, configured through the Switchboard portal and upgraded by GitLab in a weekly maintenance window, one minor release behind the current one. **GitLab Self-Managed** is installed on machines you control: you get the **Admin** area and full control, and with them the upgrades, backups, high availability and patching. Code that must stay in your own data centres, or on an air-gapped network, needs Self-Managed; the Free, Premium or Ultimate tier is a separate choice on top.

go deeper

for a junior

Name the three offerings and say who hosts and upgrades each one. Keep the offering and the Free, Premium or Ultimate tier apart.

for a middle

Explain what the subscription attaches to on each offering, what an unactivated Enterprise Edition instance runs, and why only Self-Managed and Dedicated expose the Admin area.

for a senior

Turn a residency or air-gap requirement into an offering decision, then list the operational work Self-Managed hands you: sizing, backups, upgrades through required stops, availability.

for a principal

Weigh operating cost against control: what an internal platform team must staff to run Self-Managed well, and when Dedicated's isolation without operations satisfies the regulator instead.

## One product, three ways to run it GitLab ships one application. The three **offerings** differ in who owns the infrastructure, who upgrades it, and where the data lives, not in what the code can do. A **tier** (Free, Premium, Ultimate) decides which features are switched on and is chosen separately. | | GitLab.com | GitLab Dedicated | GitLab Self-Managed | |---|---|---|---| | Tenancy | Multi-tenant: one instance shared by every customer | Single tenant, fully isolated | Your instance only | | Who hosts it | GitLab | GitLab, in a cloud region you choose | You: own data centre, own cloud account or an offline network | | Who upgrades it | GitLab | GitLab, in a weekly maintenance window, one minor release behind current | You, along the required upgrade path | | Instance administration | No **Admin** area for customers | **Admin** area plus the Switchboard portal | **Admin** area plus the server's configuration files | | Tiers sold | Free, Premium, Ultimate | Ultimate | Free, Premium, Ultimate | ## What the subscription attaches to - On **GitLab.com** a subscription applies to a **top-level group** namespace. It cannot be applied to a personal namespace, so a company buys for its group, not for the person paying. - On **GitLab Self-Managed** the subscription covers the whole instance and gives the same feature set to every user on it. An administrator activates it with an **activation code** under **Admin** > **Subscription**; an offline instance is activated with a license file or key instead. - A Self-Managed Enterprise Edition instance with no subscription activated runs **only the Free features**. Installing the Enterprise Edition package does not by itself unlock paid features. - Subscriptions **cannot be transferred** between GitLab.com and Self-Managed: moving offering means buying and applying a new subscription, and moving the data is a separate project. ## What running it yourself actually means Self-Managed is the only offering where every operational job is yours: 1. **Install** it, usually with the Linux package on virtual machines or with the GitLab Helm chart on Kubernetes. 2. **Size** it, starting from GitLab's reference architectures for your expected load. 3. **Back it up**, including the configuration and secrets files the backup command leaves out. 4. **Upgrade** it, monthly or at least through the required upgrade stops, letting background migrations finish between them. 5. **Make it highly available** if an outage would stop the business, which multiplies the number of nodes. 6. **Patch and monitor** it, like any other production service. In return you get the **Admin** area (instance-wide settings, every user and project, background jobs and migrations), the choice of hardware, network and region, and the ability to run with no internet connection at all. ## Data residency and air-gapped operation A requirement such as "source code never leaves our data centres" narrows the field quickly: - **GitLab.com** stores your data on GitLab's shared service; you control groups and projects, not where the instance runs. - **GitLab Dedicated** gives isolation and a region you pick, and supports private connectivity and IP allowlists, but it is still a service GitLab hosts in its cloud, so it is neither on your premises nor air-gapped. It also runs the previous minor release (`N-1`): when 19.3 ships, a Dedicated instance runs 19.2. - **GitLab Self-Managed** is the only offering you can install inside your own data centre or on a network with no route to the internet. ## Choosing A sensible order of questions: 1. Must the code sit on hardware you control, or offline? Then Self-Managed, whatever the tier. 2. Must the instance be isolated from other customers and pinned to a region, with no team to run it? Then Dedicated. 3. Otherwise GitLab.com is the cheapest to operate, because GitLab carries upgrades, scaling and availability. The tier is a second, independent decision: a Self-Managed instance can run Free, and a GitLab.com group can run Ultimate. ## Common misreadings - Treating the tier and the offering as one choice ("Ultimate means self-hosted"). - Expecting a group Owner on GitLab.com to reach the **Admin** area; it is not available there. - Calling Dedicated "on-premises": it is single-tenant, but GitLab hosts and operates it. - Assuming a new Self-Managed install has paid features before activation.

  • Can a GitLab.com subscription be moved onto a Self-Managed instance later?
    No. GitLab's documentation states that subscriptions cannot be transferred between GitLab.com and GitLab Self-Managed; switching offering means purchasing and applying a new subscription. Moving the groups, projects and history is a separate migration you plan on its own.
  • What does a GitLab Self-Managed Enterprise Edition instance enable before any subscription is activated, and how do you activate one that has no internet access?
    Without activation it enables only the Free features. Normally an administrator pastes the 24-character activation code under **Admin** > **Subscription**; an offline instance is activated with a license file or license key instead.
  • Why might a regulated team pick GitLab Dedicated over Self-Managed, and when does that choice fail?
    Dedicated gives a single-tenant, isolated instance in a region the team chooses, with GitLab doing upgrades and operations, which suits residency rules without an operations team. It fails when the rule says the data must sit on the organisation's own premises or on a disconnected network: Dedicated is hosted in GitLab's cloud.

  • GitLab Dedicated can be installed in our own data centre
  • A GitLab.com group Owner can open the Admin area
  • Ultimate is the self-hosted edition and Free is GitLab.com
  • Installing the Enterprise Edition package unlocks Premium features without activation
  • A GitLab.com subscription can be carried over to a Self-Managed instance