Every artifact your teams ship, assembled right the first time

GitLab announced Artifact Central, a beta organization-level artifact registry designed to replace fragmented project-level package and container registries with centralized governance for retention, storage quotas, publishing permissions, and access controls. It offers hosted repositories for internal artifacts, remote repositories that proxy external sources such as Docker Hub and Maven Central, and virtual repositories that provide a single endpoint while caching external dependencies; beta support includes Maven, npm, Docker, and OCI formats. Artifacts automatically retain provenance data from GitLab CI pipelines, including their originating pipeline, branch, commit, and trigger, while CI_JOB_TOKEN provides unified authentication for people and agents without separate service accounts. Artifact Central is intended to work alongside GitLab Dependency Firewall, which can block risky packages in pipelines, with deeper policy integration planned. Organizations can migrate gradually by using existing registries as remote sources behind virtual repositories before converting them to hosted repositories. The service is currently free in beta for GitLab.com, with GitLab Self-Managed availability planned later in the month.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.