Guide
Small declared resource requirements for a VPS or thin client, with new metrics, notifications, notes and utility recipes. The limit applies to each application separately.
A 1 GB machine cannot run every application listed here together. The cards show a per-recipe minimum; the total adds them without estimating concurrency. Leave room for the operating system and choose recommended RAM when the workload is uncertain.
Start with small, predictable services such as a resolver, notification server or static toolbox. Initial scans, imports, retained monitoring history and large attachment collections change the workload. The published smoke verifies functionality and recovery, not a benchmark under every minimum-memory limit.
Use container memory limits deliberately and monitor pressure. Swap can absorb a short spike, but it does not turn an undersized VPS into a larger server. Retention and off-server backups matter even for a service that starts with very little data.
Sets
The sum of the minimums the recipes below declare. It is a floor, not a recommendation: leave room for the operating system, backups and growth.
Why it is here: 256 MB, and most of that is the runtime rather than the data. A vault for a household is a few megabytes of encrypted blobs; the memory figure does not grow with the number of passwords.
Why it is here: 256 MB for filtering every query on the network. The query log is the part that grows, and it grows on disk — set the retention deliberately.
Why it is here: 256 MB with an important caveat: the initial scan of a large library is the hungriest thing this service ever does, and a first indexing run on a very big collection can want more than steady-state playback.
Why it is here: 256 MB, and the number is driven by how many files are being watched rather than by how large they are. Hundreds of thousands of small files cost more than a few enormous ones.
Why it is here: 512 MB is comfortable for dozens of checks. What eventually grows is the history database, not the resident memory.
Why it is here: A declared 128 MB minimum for configuration-driven availability checks and a status page. Keep the configuration and persistent state in the backup.
Why it is here: The hub declares 128 MB minimum and 256 MB recommended RAM. Agents are separate; metric retention and the number of monitored machines affect storage and load.
Why it is here: A declared 128 MB minimum for authenticated topics and notification delivery. Attachment storage and cache retention need their own disk budget.
Why it is here: A declared 256 MB minimum for notes and attachments. Preserve the whole data directory, including files; closed registration does not make a deliberately public note private.
Why it is here: A declared 256 MB minimum for a shared service dashboard. External integrations add their own requests and credentials; they are not configured by this recipe.
Why it is here: A declared 128 MB minimum for serving static developer utilities. There is no native login; favorites and some inputs live in the browser, outside server backups. The stable image is from 2024.
Why it is here: The recipe declares 512 MB minimum and includes PostgreSQL. Its archive grows with retained feed entries; the minimum is not a maximum for every subscription count.
Why it is here: 512 MB, with the ledger stored in SQLite. The budget of a household is small data by any measure, which is why this fits where a hosted product would have needed an account.