Pricing
The two things Registry meters — logical storage and egress — how they're measured, and what isn't billed during early access.
Early access. Storage and egress are metered but not yet billed. Usage appears in the Console so you can see it; nothing is charged until pricing is published.
Registry meters two dimensions:
-
Storage (
registry-storage) — the logical bytes your registries hold: the distinct layers they reference. Storage is content-addressed and deduplicated across every repository and the cache, so an identical layer is stored once — deduplication is the platform’s margin, not your bill. Sampled daily. -
Egress (
registry-egress) — the bytes served on pull. This is split for visibility into two lines:- your images — pulls of content you pushed, and
- pull-through cache — pulls served from the cache.
Both are the same rate; the split shows how much the cache is doing for you.
What is not metered:
- Pushes (ingress) are free.
- Upstream fetches the cache makes on your behalf are absorbed by the platform, not charged to you.
- Deduplicated bytes — you pay for logical layers, not physical copies.
Seeing your usage
In the Console, the organization usage view breaks Registry out per registry and
dimension. From the CLI, lbr registry get <slug> shows a registry’s current
logical bytes and repository count.
Where to next
- Core concepts — how storage and garbage collection work.
- Pull-through cache — where cache egress comes from.