Skip to content
Start free
Documentation menu

Limits and quotas

Limits are published so you can design around them. Where a limit can be raised, the last column says how.

Objects

LimitStarterTeamScaleEnterprise
Largest container layer5 GB50 GB100 GB200 GB
Largest generic object5 GB50 GB200 GB1 TB
Largest package file500 MB2 GB5 GB10 GB
Tags per repository1,000100,0001,000,000No fixed limit
Largest cache entry5 GB40 GB40 GB200 GB

Request rates

OperationStarterTeamScaleNotes
Blob and package reads6,000 per dayNo limitNo limitBandwidth is limited per organisation to 40 Gbit/s on Team and 200 Gbit/s on Scale per region.
Manifest and metadata reads60 per minute3,000 per minute12,000 per minutePer token. A 429 includes a Retry-After header.
Writes30 per minute600 per minute3,000 per minuteCounted per manifest or version, not per blob.
Management API120 per minute600 per minute1,800 per minutePer organisation.

Retention and recovery

  • Soft-deleted artifacts can be restored for 7 days on all plans.
  • Audit log retention is 7 days on Starter, 90 days on Team, 1 year on Scale.
  • Cache entries unused for 14 days are removed by default; the setting is per organisation.
  • Mirrors revalidate tags after 6 hours and package metadata after 30 days.

Replication and regions

Team organisations may replicate to one additional region and Scale organisations to three. Replication is asynchronous, with a median lag of 1.4 seconds for 100 MB between eu-north-1 and eu-central-1 and 3.1 seconds between eu-north-1 and us-east-1. Enterprise organisations can use a dedicated storage cell in any region, with synchronous replication between two availability zones.

Need a higher limit on a paid plan? Write to support@fi4.enotcloud.com with the organisation slug and the use case. Most object size increases are approved the same day.