Choosing Nano
Small packages.
A useful starting point.
Use hosted storage for the bytes that need a home—not necessarily every upstream application payload.
5 MB storage
12 GB yearly repository egress
Nano suits lightweight packages and small repositories. Larger binaries may not fit.
Ordinary packages work here.
Publish your own .deb files using the CLI. Recipes are optional, and ordinary Debian packages work here.
If a package exceeds your available storage or technical publication limits, it cannot be published. Standard and Pro are planned, not currently available upgrades.
Recipes can keep hosting small.
Mema is an independent installation and version-management tool. A recipe can tell Mema how to retrieve software from its existing upstream.
- Host the recipeTPA Hub distributes the small signed Debian recipe package.
- Retrieve the softwareMema downloads the application from its upstream source.
- Retrieve from the upstreamMema uses that source's availability and trust model for the application download; TPA Hub hosts the recipe package.
This keeps a large application payload at its existing upstream. The Mema runtime is a separate package installed on the consumer's machine.
Estimate with your own artifacts.
At roughly 2 KB per recipe package, 5 MB is approximately 2,500 packages before other published payloads. Real packages vary, and the runtime also needs space if you host it yourself.
Illustration only—not a package-count promise. Download frequency, APT metadata, caching, and package sizes affect egress.