Every artifact you publish, assembled right every time.

Higher agent accuracy, lower token cost
Learn how to harden your software factory and let AI agents earn autonomy, without trading away security.
Stay updated with our latest features and improvements.
GitLab Artifact Central
GitLab Artifact Central is one governed home for every package and container image your teams and agents touch.
Artifact CentralA control plane for every artifact
For platform teams setting policy, and the developers who build on it.
Set retention, quota, and access once at the organization level instead of once per project. Hosted, remote, and virtual repos sit behind a single URL, so developers hit one address.
Publish your own packages and images to a hosted repo. Proxy external sources like Docker Hub through a remote repo. A virtual repo fronts both: hosted first, remote as fallback.
Every artifact carries its build provenance: pipeline, branch, commit, and who triggered the job. Publishing and pulling use the same CI/CD identity your pipelines already rely on.
Pay for what you keep: no per-seat fees, no charge for cached content, no guessing at what's coming. Your bill reflects what you actually use.
Add your existing repos as remotes behind a virtual repo. Developers point at one URL; artifacts move over only when a build actually asks for one. No bulk copy, no downtime window. Your old registry stays the system of record until you convert the remote to hosted, on your own schedule.
// Start building faster today
Here's what's bringing teams to Artifact Central. If this sounds like you, we'd love to hear from you.
Running at scale: You're maintaining artifact infrastructure across many projects or teams, not just one.
Core formats: Maven, npm, Docker, or OCI make up most of what you publish today.
A change already in motion: A registry renewal is coming up, or you're actively evaluating a move off your current tool.
Room to get setup: You can commit some platform engineering time to onboarding.
For Self-Managed customers, GitLab 19.5 or later and Cloud Native GitLab are required.
AI agents now pull and publish packages at machine speed, so the artifact surface you have to govern grows faster than any team can review by hand. Most companies are also running more registries than they can reasonably manage, each with its own logins, audits, and cost surprises.
During its beta period, Artifact Central is rolling out to GitLab.com customers first. We're also working with a small group of Self-Managed design partners, and will expand that group over time. Dedicated customers will be the final cohort we roll out to.
Fill out the form on this page, and a member of the GitLab team will follow up with next steps. There's no cost or commitment to sign up; it's the fastest way to get access as new cohorts open.
We are not charging for Artifact Central during the beta period. When it becomes generally available, it will be billed on the average daily count of artifact versions you keep, never on cached content or peak usage. GitLab.com and Dedicated customers also meter storage and egress; Self-Managed is billed on components only. Cost draws down from your existing GitLab Credits; no new contract, no per-seat fee.
Today's registries are free, but live project by project, so policy gets set hundreds of times with no company-wide view of cost or usage. Artifact Central moves that to the organization level: one place to set policy, see usage, and govern what teams and agents publish.
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license