At its Transcend event, GitLab announced Artifact Central, an organization-level registry intended to replace hundreds of project-level registries. The aim is to ensure every pull or publish—whether by a developer or an automation agent—passes through the same governed door, enabling platform teams to assemble the right software the first time.
The beta is free on GitLab.com, with a Self-Managed version planned for later this month and no billing during the beta period.
WHAT ARTIFACT CENTRAL DOES AND WHY IT MATTERS
Artifact Central brings packages and container images into one governed home beside code and pipelines. It centralizes policy—retention, quotas, and access—at the organization level rather than configuring rules inside hundreds of projects. The result is intended to reduce registry sprawl and the operational friction that arises when agents continuously publish across many projects. TechStaged has also covered Azure AI Foundry Agent Operations for Production Teams.
- One organization-level registry that replaces hundreds of project-level registries
- Retention rules, storage quotas, and access policies set once at the organizational level
- Policies inherited by all repositories under the organization
HOW THE REGISTRY IS STRUCTURED AND HOW IT WORKS
GitLab Artifact Central supports three repository types that developers publish to and pull from via a single URL: Hosted (private packages and images you build), Remote (a proxy in front of external sources like Docker Hub or Maven Central), and Virtual (a unified endpoint that combines hosted and remote and caches the first external pull).
- Hosted repositories store internal artifacts
- Remote repositories proxy external sources and are validated before use
- Virtual repositories centralize access and cache first pulls for faster subsequent access
BUILD PROVENANCE AND AUTHENTICATION
Artifacts published through Artifact Central carry provenance data from the originating pipeline, including the build pipeline, branch, commit, and the publisher. Authentication uses the existing CI_JOB_TOKEN for both publishing and pulling, aligning artifact access with the same identity used by pipelines and agents.
CENTRALIZED GOVERNANCE AND MIGRATION PATH
Policy and access controls are defined at the organization level, removed from per-project configurations, and inherited by all underlying repositories. For teams migrating from existing registries, GitLab provides a gradual path by adding current repos as remotes behind a virtual repository, with the option to convert remotes to hosted repositories later.
- Organization-level policy for retention, quotas, and access
- Single URL for publishing and proxying
- No need for bulk, zero-downtime migration; existing registries can be phased into Artifact Central
AVAILABILITY, PRICING, AND WHAT HAPPENS NEXT
Artifact Central is available in beta on GitLab.com. A Self-Managed version is planned for later in the month. There is no billing during the beta, and pricing details will be announced ahead of general availability.
- Beta on GitLab.com
- Self-Managed version planned for later this month
- No billing during beta; pricing to be announced
RELATED COVERAGE
SOURCES
- GitLab: Every artifact your teams ship, assembled right the first time Published · Primary source
