Container Registry Pricing

A container registry combines a flat monthly fee with metered storage and egress.

The registry fee

A flat monthly fee per registry, prorated from the day you create it. It is charged for the registry existing, independently of what you store in it.

Repositories inside a registry are not charged individually.

Storage

Storage is measured once a day, and totalled across every repository in your organization.

Your invoice reflects the most recent measurement in the billing period. Two consequences follow from that:

• Deleting large images — or letting a retention policy expire them — lowers the next measurement, and therefore the next invoice.
• An image that exists only between two daily measurements is never measured.

Retention policies are the practical lever here: keeping the last N tags, or expiring untagged images after a number of days, keeps the measured total from growing without attention.

Egress

Egress counts only the compressed layers a client actually downloads.

These do not count:

• Layers the pulling machine already holds in its cache
• Requests that only check whether an image or tag exists
• Pushes — uploading images is never charged

Because Docker clients skip layers they already have, a repeated pull of an unchanged image costs far less egress than its total image size suggests.

The included allowance

Each billing period includes an egress allowance before the per-GB rate applies. The allowance covers your whole organization, not each registry separately, and does not roll over.

Public repositories

A public repository can be pulled by anyone without credentials, and that egress is billed to your project. Because a popular or scraped repository can run that up quickly, a public repository requires an egress cap. When the cap is reached the repository reverts to private rather than continuing to bill.

Deleting a registry

Deleting stops the fee and the meters, and credits back the unused part of the period. The stored images are destroyed with it.