Plans and capacity

Choose the capacity that fits your packages.

Deliver approved versions to Debian machines through the same signed APT repository workflow. Plans differ in hosted package capacity and delivery, not in a required fleet agent.

Capacity is measured in package bytes and repository egress, not an arbitrary repository count.

Not available

Standard

500 MB storage
20 GB monthly repository egress

Planned fixed capacity for larger application packages. It cannot be purchased today.

Not available

Pro

Pay as you go
500 MB storage blocks
20 GB egress blocks

Planned usage-based capacity. Storage and egress would scale independently. It cannot be purchased today.

What counts toward capacity?

Storage

The canonical published .deb payloads across your repositories. APT metadata, queued uploads, and temporary workspaces are excluded from this measurement. The quota applies account-wide to the final active package payload, not separately to each repository.

Publishing is subject to entitlement and technical upload limits.

Repository egress

Package and repository metadata bytes actually delivered. Nano uses an annual entitlement period. After its allowance, new package downloads are rate-limited rather than abruptly cutting off active transfers.

Uploads remain subject to technical rate and request limits. Read the usage reference.