This document explains Artifact Registry pricing details.

The same Artifact Registry pricing applies to all repositories that store artifacts and are generally available or in Preview.

• Storage
• Data transfer
• Vulnerability scanning, if it is enabled and supported by the repository

The following types of repositories store artifacts:

• Standard repositories
• Remote repositories
• Repositories that support the gcr.io domain

Virtual repositories do not store artifacts, so your usage costs are for its upstream standard and remote repositories rather than the virtual repository itself.

Pricing applies to billing accounts, not individual Google Cloud projects. For example, if your billing account is attached to multiple projects running Artifact Registry, the limit for the storage free tier is for total usage across all the attached projects.

You can use the Google Cloud Pricing Calculator to estimate the cost of using Artifact Registry.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Storage costs apply to the at-rest storage of your artifacts in Artifact Registry repositories. The following pricing applies to repositories that are in Preview or that are generally available:

Data transfer pricing is per GB delivered from Artifact Registry repositories. When network traffic leaves a repository, the pricing depends on both the repository location and the destination of the traffic.

Data transfer pricing applies to repositories that are in Preview or that are generally available:

• Pricing for outbound Internet data transfer is based on Premium tier pricing. This is network traffic leaving a repository to a client that is not a Google product, such as using a local server that is downloading artifacts.
• Data transfer into Google Cloud is free.
• For data transfer to destinations within Google Cloud, the following pricing applies:

• For egress traffic from a VPC network through an interconnect:

• Data transfer to Google products (such as YouTube, Maps, and Drive) is free.

Automatic vulnerability scanning and On-Demand Scanning is billed for repository scanning features that are generally available or in Preview.

• If the Container Scanning API is enabled in either Artifact Registry or Container Registry, vulnerability scanning is turned on and billed for both products.
• If the On-Demand Scanning API is enabled, On-Demand Scanning is turned on and billed for both Artifact Registry and Container Registry.

For pricing details, see the Artifact Analysis documentation.

The following options can help you to manage your costs:

• Co-locate repositories in the same region as runtimes such as Google Kubernetes Engine, Cloud Run, and Compute Engine so that there are no cross-region data transfer costs.
• Host repositories closer to your consumers to reduce data transfer costs. For example, you can host repositories in a region in Australia for customers in Oceania.
• Delete artifacts that you no longer need.