Self-Hosted App Picker + Resource Budget Estimator
Enter a hardware budget (or pick a typical box), add self-hosted apps to a stack, and watch a live meter sum realistic idle and active RAM plus CPU share — shared databases counted once — with a fit verdict and lighter-alternative suggestions when you go over.
App catalog
Budget meter
Methodology & honest caveats
Each app has two RAM numbers: idle (resident at the login screen, no traffic) and
active (a realistic working peak under light single-user use — not a synthetic stress
test). The meter sums idle for a floor and active for the ceiling you should actually budget against.
Figures come from each project's documented minimum/recommended requirements, cross-checked against
community docker stats reports, then rounded up slightly so a "comfortable" verdict has slack.
Shared databases are counted once. If three apps declare postgres, one
Postgres instance is added to the total, not three — that single dedup is the difference between "won't fit"
and "comfortable" on small boxes. cpuWeight is a relative steady-state core-share
(1.0 ≈ one modern core busy under light load); it is summed and compared to your thread count as a rough
saturation gauge, not a benchmark.
Verdict thresholds: active RAM ≤ 70% of budget → comfortable, ≤ 90% → tight, otherwise won't fit; CPU is
flagged when summed weight exceeds available threads. These are sizing estimates: heavy
media libraries, many users, sync storms or chatty integrations push real usage above these steady-state
numbers, and transcoding/OCR/indexing spike CPU far beyond the idle figure. Use this to rule options in or
out, then measure the real thing with docker stats.
Catalog & figures: src/data/selfhost-apps.json (model v1.0).
Decision-support only.