Self-hosted app resource planner: will your apps fit on your server?

Version 1.0.1

Add the apps you plan to self-host and your server's RAM and disk to see whether they fit, with a low and a high estimate for each app.

Have the RAM and disk space you can give these apps, after the operating system and anything else on the machine.

App mix

Choose the services you want to compare.

Open App to add
Type at least two letters to search, or choose Custom app.

Host budget

Reserve host headroom.

RAM budget
GiB
App storage budget
GB
Headroom reserve
%

What to enter

Search for each app by name. The estimates come from the self-host apps directory. Each shows its basis, its source, and a confidence level. Most are estimates for a small home setup, not measurements.

For an app that isn't listed, or a setup bigger than the basis describes, add a custom row with your own low and high numbers. Quantity multiplies both, such as two copies of the same database.

RAM is in GiB and storage is in GB, the unit disks are sold in. Headroom reserve holds back a share of each budget once, for the operating system, caches, and spikes. The default 20% is a starting point, not a rule.

How to read the result

StatusWhat it means
WithinEven the high estimates fit.
TightThe low estimates fit, but the high ones don't.
OverEven the low estimates don't fit.
UnknownAt least one app has no estimate, so the total can't be settled.

Jellyfin, Immich, and Vaultwarden on a 16 GiB server

Example

Budget 16 GiB RAM and 1,000 GB storage, with 20% headroom.

The result is RAM may exceed the available amount. RAM needs 10 GiB to 17 GiB, and 13 GiB is available. Storage needs 101 GB to 620 GB, which fits in the 800 GB available. With 24 GiB of RAM, the plan is within budget.

How much RAM does a home server need?

Add up the apps you'll run, then leave room for the system. Small services such as a password manager or a DNS filter need well under 1 GiB each. Media servers and photo libraries need several GiB each, and most of a home server's RAM goes to them.

The planner's estimates name their source. Immich's, for example, follows the project's requirements: 6 GB of RAM minimum and 8 GB recommended.

Should I plan for the low or the high estimate?

Plan for the high one. RAM use grows with users, library size, and background work such as transcoding, thumbnails, or search indexing. A server that fits only the low estimates will run out of memory at busy moments.

When Linux runs out of memory, the kernel starts killing processes, and Docker notes that any process can be picked, including Docker itself.

Does a Docker memory limit make an app need less RAM?

No. A limit caps how much a container can use. An app that needs more than its limit can crash or slow down, but it won't need less. Use limits to protect the other apps on the server, not to make a plan fit.

After the apps are running, docker stats shows what each container really uses. Compare that with the plan and adjust the estimates.

What does the storage estimate include?

It depends on the app, so read its basis. Some ranges cover only the app and its database. Your own data, such as a film library or years of photos, can be far bigger. Add it as a custom row when the basis doesn't mention it.

Leave space for backups too, on another disk if you can.

Does the planner check CPU?

No. It totals RAM and storage only. Video transcoding and machine learning, such as face recognition in photo apps, lean on the CPU or a GPU. Check each app's own requirements. Immich, for example, asks for at least 2 CPU cores.

To pick the machine itself, see the course chapter on picking your first server.