Nano plan
Small packages.
A practical starting point.
Nano gives small Debian repositories a hosted home without requiring a large software catalog.
Included capacity
5 MB storage
12 GB yearly repository egress
Nano suits lightweight packages and small repositories. Published payloads must fit within the available storage and technical limits.
Publish ordinary Debian packages.
Publish your own .deb files using the CLI. Recipes are optional; Nano is a package distribution plan, not a special package format.
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 are optional.
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.run distributes the small signed Debian package.
- Retrieve the softwareMema downloads the application from its upstream source.
- Use the upstream trust modelMema uses that source's availability and trust model for the application download; TPA.run 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 packages.
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.