Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

GitLab Package Registry

docs.gitlab.com

  • Free plan
  • Linux
  • Web
  • API
  • Self-hosted
7.8 Club score Visit docs.gitlab.com

What GitLab Package Registry is

GitLab Package Registry lets projects publish packages for downstream projects to use as dependencies. It can be configured as a private or public registry for supported package managers and is available on GitLab.com, GitLab Self-Managed, and GitLab Dedicated across Free, Premium, and Ultimate. Generally available formats include Generic packages, Helm, Maven, npm, NuGet, and PyPI; Composer and Conan are beta, while Debian, Go, and Ruby gems are experimental. Conda, CRAN, RPM, and Swift are not supported. Projects can host multiple package types, including packages built from a monorepo. GitLab CI/CD can build or import packages, with jobs authenticating through CI_JOB_TOKEN, and the registry can also be administered through an API. Project roles control access; protection rules can limit pushes or deletions for supported formats. Audit events require an enabled namespace setting and Premium or Ultimate. A dependency proxy is beta and limited to those paid tiers. GitLab is an all-remote company with no physical headquarters.

Who it suits

It suits teams that want to publish and consume dependencies within GitLab projects, including projects using GitLab CI/CD. Check that the registry supports your package format and that the needed access or audit controls fit your plan.

Good to know, and what to watch

  • Available on GitLab.com and self-managed deployments.
  • Supports several package formats, including npm and PyPI.
  • CI/CD jobs can authenticate with CI_JOB_TOKEN.
  • Projects can host multiple package types.
  • API administration and automation are available.
  • Conda, CRAN, RPM, and Swift are unsupported.
  • Some package formats are beta or experimental.
  • Audit events require Premium or Ultimate.
  • Dependency proxy is beta and limited to paid tiers.

Ultimate

—

Free

Free

Premium

$29

Free plan · 30-day trial

Getting started

  1. Open https://docs.gitlab.com/user/packages/package_registry/
  2. Choose GitLab.com, Self-Managed or Dedicated
  3. Create or select a project and choose a supported package format
  4. Build or import packages with GitLab CI/CD
  5. Authenticate jobs with CI_JOB_TOKEN
  6. Publish and consume packages using project roles or the API

Limits to check

The Free plan allows five users per top-level group, 400 compute minutes per month and 10 GiB adjustable storage. Audit events and the dependency proxy require Premium or Ultimate, while some package formats are beta, experimental or unsupported.

The Club's review

GitLab Package Registry gives teams a place to publish packages for downstream projects to use as dependencies. It is best suited to teams already building in GitLab who want package publishing connected to project permissions and CI/CD. Its appeal is workflow integration; format maturity and lower-plan quotas deserve careful consideration.

Overview

The registry supports private or public package distribution for supported package managers and is available on GitLab.com, GitLab Self-Managed and GitLab Dedicated. It is included with Free, Premium and Ultimate, so teams can start without buying a separate registry product. A project can host multiple package types, including packages produced from a monorepo, which is useful when related components share one project workflow.

Key features

Formats and automation

Generally available formats include Generic packages, Helm, Maven, npm, NuGet and PyPI. Composer and Conan are beta; Debian, Go and Ruby gems are experimental. Conda, CRAN, RPM and Swift are unsupported. That covers several widely used ecosystems, but teams relying on beta or experimental support should avoid making it a critical publishing path until the format is suitable for their needs.

GitLab CI/CD can build or import packages, and jobs can authenticate with CI_JOB_TOKEN. Registry administration is available through an API, with API access for automating Generic package workflows. This makes the registry a natural fit for GitLab-based build pipelines, though teams using another CI environment may value less of this integration.

Permissions and controls

Project roles govern package access. In private projects, Reporters can view and pull packages, while Developers can publish. Package protection rules can restrict who may push or delete matching packages, with documented support for npm, PyPI, Maven and Conan. These controls help teams separate consumption from publishing, although the protection feature's format coverage is narrower than the full registry format range.

Package publication and deletion can generate audit events when the namespace setting is enabled, but audit events require Premium or Ultimate. The dependency proxy caches upstream packages to reduce external downloads and speed builds; it is beta and also limited to Premium and Ultimate. Both are useful additions for organizations that need them, but neither should be assumed to be part of the Free workflow.

Security and operational limits

For npm audits, GitLab forwards requests to npmjs.com by default to retrieve vulnerability information. Audit request bodies can contain private package information, so teams should account for that behavior when reviewing security and data-handling requirements.

Pricing

GitLab Package Registry is included in GitLab's Free, Premium and Ultimate plans. Free costs nothing, billed per user/month, and is capped at 5 users per top-level group, 400 compute minutes/month and 10 GiB adjustable storage. It is a practical starting point for small teams, but the user, compute and storage ceilings can constrain growing pipelines.

Premium costs $29 a year, billed per user/month and annually. It includes 10,000 compute minutes/month and 500 GiB storage, as well as Priority Support. GitLab states paid-plan support is 24/7 for Emergency severity and 24/5 for other impact levels. Premium suits teams that need more build capacity, storage or its paid-plan features such as audit events and the beta dependency proxy; it is a substantial step up from Free, so those needs should justify the per-user commitment. A 30-day trial is available.

Ultimate has custom pricing, with 50,000 compute minutes/month and 500 GiB storage. It is aimed at organizations that need its higher compute allowance and Ultimate-tier access; no price is given, so buyers should expect a custom quote. The listed paid starting point is $29/user/mo (annual).

Platforms

The registry is offered on GitLab.com, GitLab Self-Managed and GitLab Dedicated. Its listed platform coverage includes API, Linux, self-hosted and web, giving teams hosted and self-managed deployment choices.

Who it's for

Choose it when GitLab is already central to your source projects and CI/CD, and you want package permissions, publishing and dependency use to follow those project workflows. It is less suitable when a required format is unsupported or experimental, or when a team needs Premium/Ultimate capabilities but cannot justify moving beyond Free.

Pros and cons

  • Pro: CI/CD jobs can build or import packages and authenticate with CI_JOB_TOKEN, keeping package publishing close to GitLab pipelines.
  • Pro: Private-project roles distinguish package consumers from publishers, with additional push/delete protection for several common formats.
  • Pro: The registry is included across all three plans and supports hosted, self-managed and Dedicated GitLab deployments.
  • Con: Several formats are only beta or experimental, and Conda, CRAN, RPM and Swift are unsupported.
  • Con: Free limits compute to 400 minutes/month and storage to 10 GiB, with a 5-user top-level group cap.
  • Con: Audit events and the beta dependency proxy require Premium or Ultimate; npm audit requests are forwarded externally by default.

Alternatives

For broader software selection, browse Application Lifecycle Management Software, ML Experiment Tracking Software, Model Registry Software, Game Version Control Software, GitOps Tools or Preview Environment Software.

Innoslate is another option for buyers comparing software platforms with a free plan and a free trial. ONES is a freemium alternative with a free tier capped at 30 seats and 30 MB per file. Rally Software offers a free Starter Edition for 50 named users, available only in listed countries. TechExcel ProjectOne ALM is a paid alternative with a free trial and a plan displayed at $10 a month per user on annual billing. SAP Cloud ALM is a free option for eligible support customers, with one tenant per customer number. OpenText Core Performance Engineering has usage-based custom pricing and a free trial, but no free plan. IBM Targetprocess is a paid alternative with a free trial and no free plan. TechExcel DevSuite is a paid alternative with a free trial and a cloud plan displayed at $35 a month per user with annual billing.

Verdict

GitLab Package Registry is a strong choice for teams that already run projects and CI/CD in GitLab and want package publishing to fit those workflows without a separate product purchase. Its main trade-offs are uneven format maturity and the compute, storage and feature limits that make larger or more controlled deployments a paid-plan decision.

The verdict

GitLab Package Registry links package publishing and dependency use with GitLab projects and CI/CD. Verify package-format status and plan requirements before relying on features such as audit events or the dependency proxy.

Questions people ask

Is GitLab Package Registry free?

Yes. It is included in the Free plan, which lists five users per top-level group, 400 compute minutes monthly and 10 GiB adjustable storage.

What is the paid price?

Premium is listed at $29 a year, billed annually per user per month. Ultimate uses custom pricing.

Where can it run?

The registry is offered on GitLab.com, GitLab Self-Managed and GitLab Dedicated, with API, Linux, self-hosted and web platforms listed.

Which package formats are supported?

Generally available formats include Generic, Helm, Maven, npm, NuGet and PyPI. Composer and Conan are beta; Debian, Go and Ruby gems are experimental.

Who can publish private-project packages?

In private projects, Reporters can view and pull packages, while Developers can publish them.

Does it integrate with CI/CD?

Yes. GitLab CI/CD can build or import packages, and jobs can authenticate with CI_JOB_TOKEN.

What the maker publishes

Access controls
Project roles govern package access; for private projects, Reporters can view and pull packages and Developers can publish them. source
API and automation
The registry can be administered through an API, and generic packages support API access for automation. source
Audit events
Package publication and deletion can generate audit events when the namespace setting is enabled; audit events are a Premium and Ultimate feature. source
Availability
The Package Registry is included in Free, Premium and Ultimate and is offered on GitLab.com, GitLab Self-Managed and GitLab Dedicated. source
CI/CD integration
GitLab CI/CD can build or import packages, and jobs can authenticate to the registry with CI_JOB_TOKEN. source
Dependency proxy
The dependency proxy caches copies of upstream packages to reduce external downloads and speed up builds; GitLab marks this feature beta and Premium/Ultimate. source
Founded
2011 source
Founded
2011 source
Founded
2011 source
Headquarters
No physical headquarters; GitLab is all-remote source
Known limits
GitLab lists Conda, CRAN, RPM and Swift among package formats that are not supported by the registry. source
npm security behavior
For npm audits, GitLab forwards requests to npmjs.com by default to retrieve vulnerability information, and warns that audit request bodies can include private package information. source
Package protection
Package protection rules can restrict who may push or delete matching packages, with support documented for npm, PyPI, Maven and Conan. source
Package workflows
A project can host packages for multiple package types, including packages built from a monorepo. source
Purpose
The registry lets users publish and share packages that downstream projects can consume as dependencies. source
Support
The Premium plan includes Priority Support; GitLab states paid-plan support is 24/7 for Emergency severity and 24/5 for other impact levels. source
Supported formats
Generally available formats include Generic packages, Helm, Maven, npm, NuGet and PyPI; Composer and Conan are beta, while Debian, Go and Ruby gems are experiments. source
Visibility
GitLab can be used as a private or public registry for supported package managers. source

Checked against the maker's pages on 29 Sept 2026.