Storage and Allowances
Every namespace on the hosted registry has a storage limit: the most its published packages may take up. Reads are never blocked by a limit. When a push would go over it, the registry refuses the push with 402 and keeps everything already published.
Two budgets per person
| Budget | Who has it | Size | What it pays for |
|---|---|---|---|
| Public allowance | everyone, free | 1 GiB | 100 MiB for each public namespace you own, so up to 10 of them |
| Pro storage | a personal Pro plan | your plan’s storage | your private namespaces, and the part of a public namespace above 100 MiB that you sponsor |
An organization has one pool, its Pro plan’s storage, shared by the org’s namespaces.
Public namespaces
A public namespace you create gets 100 MiB, free, from your public allowance. It never touches a Pro plan. If you already own 10 public namespaces, creating another is refused until you delete one.
The size is fixed: only an owner of the namespace with a personal Pro plan can enlarge it. That owner becomes the namespace’s sponsor, and only the part above 100 MiB is counted against their Pro storage. For example, a 300 MiB public namespace uses 200 MiB of the sponsor’s Pro storage. Another owner with Pro can take over the sponsorship, and any owner can bring the namespace back to 100 MiB, which ends it.
If the sponsor’s Pro plan ends, nothing is deleted. Pushes are limited to the free 100 MiB until the sponsor renews or another owner with Pro sponsors it; renewing restores the larger limit by itself.
A public namespace with several owners takes one slot of each owner’s allowance.
Private and organization namespaces
A new private or organization namespace takes 100 MiB of its pool by default, or whatever is left if less remains. Its owner, or an org owner or billing admin, can change the limit as long as all the namespaces in the pool still fit. A namespace’s limit is a reservation: free space inside one namespace isn’t lent to another.
Organization storage
An org’s plan storage is one pool, split three ways:
- Namespace slices, one per org namespace (private or Verified Publisher).
- The capture reserve, for captures and memory candidates (see Session capture).
- Org memory, which uses whatever the slices and the reserve leave free.
The owner sees it on Settings → Storage in the painel:
- a bar of the pool;
- each namespace’s use against its slice, split by package kind (Skills, Rules, Specs, Templates);
- totals by kind;
- memory, and the capture reserve with its use.
The page warns when less than 10% of the pool is free. To free space:
- lower slices or a reserve that are larger than they need;
- delete old package versions;
- or upgrade the plan.
Seeing your usage
- Personal dashboard in the painel: your public allowance (slots used out of 10) and, with Pro, how much of your Pro storage is allocated.
- Namespace page: what the namespace uses against its limit, and for a public namespace, the free part and who sponsors the rest.
- API:
GET /v1/me/planreturnspublic_allowanceandstorage_allocated;GET /v1/namespaces/{namespace}/usagereturns the namespace’s usage, limit and, for a public namespace,free,sponsor,sponsoredExcessandeffectiveLimit.
Self-hosted deployments can change the allowance with LORE_PUBLIC_ALLOWANCE_BYTES.
For an org, GET /v1/orgs/{org}/storage (owner) returns the whole pool, and GET /v1/orgs/{org}/captures/policy?storage=1 the capture reserve and its use.