Independent self-hosting lab
Self-hosted apps, actually tested.
Measured RAM, verified Docker Compose files, the hardware and VPS that fit.
We run each app in Docker in our lab, record the version and test date, and publish what it really uses. Read how we test.
- Lab runs published
- 22
- Articles
- 16
- Latest run
- 2026-11-08
Latest lab results
How we measure| App | Version | Idle RAM | Peak RAM | Tested |
|---|---|---|---|---|
| AutheliaAuthentik vs Authelia · 4.39.28 · 2026-11-08 | 4.39.28 | 56 MiBrange 48–65 · 3 runs | 607 MiBrange 518–650 · 3 runs | |
| authentikauthentik Docker Compose · 2026.8.5 · 2026-11-08 | 2026.8.5 | 1.0 GiBrange 840 MiB–1.0 GiB · 3 runs | 1.1 GiBrange 918 MiB–1.1 GiB · 3 runs | |
| AdGuard HomeAdGuard Home vs Pi-hole v6 · v0.107.79 · 2026-11-06 | v0.107.79 | 26 MiBsame when rounded in all 3 runs | 52 MiBsame when rounded in all 3 runs | |
| Pi-hole v6Pi-hole Docker Compose (v6) · 2026.10.1 · 2026-11-06 | 2026.10.1 | 9 MiBrange 9–10 · 3 runs | 18 MiBsame when rounded in all 3 runs | |
| JellyfinJellyfin Docker Compose · 12.4 · 2026-11-03 | 12.4 | 186 MiBrange 184–187 · 3 runs | 406 MiBrange 405–406 · 3 runs | |
| Uptime KumaUptime Kuma Docker Compose · 2.5.9 · 2026-11-03 | 2.5.9 | 123 MiBrange 122–124 · 3 runs | 139 MiBrange 138–140 · 3 runs | |
| Vaultwarden backup and restoreHow to Back Up Self-Hosted Bitwarden (Vaultwarden) · 1.37.5 · 2026-11-03 | 1.37.5 | Command-line tool, RAM in the measured table | ||
| Vaultwarden with CaddyVaultwarden Docker Compose · 1.37.5 · 2026-11-03 | 1.37.5 | 22 MiBrange 21–22 · 3 runs | 67 MiBrange 66–69 · 3 runs | |
| FileBrowser QuantumSelf-Hosted Alternative to Google Drive · v2.0.2-stable · 2026-10-28 | v2.0.2-stable | 21 MiBrange 20–22 · 3 runs | 36 MiBrange 34–39 · 3 runs | |
| Home AssistantHome Assistant Docker Compose · 2026.10.4 · 2026-10-28 | 2026.10.4 | 363 MiBrange 354–366 · 3 runs | 368 MiBrange 358–369 · 3 runs | |
| ImmichImmich Docker Compose · v3.3.5 · 2026-10-28 | v3.3.5 | 1.3 GiBsame when rounded in all 3 runs | 3.6 GiBrange 3.5–3.7 · 3 runs | |
| Immich (4 GiB cap)Immich RAM Requirements · v3.3.5 · 2026-10-28 | v3.3.5 | 1.4 GiBrange 1.3–1.4 · 3 runs | 3.0 GiBrange 2.8–3.2 · 3 runs | |
| Immich (ML job concurrency 1)Immich RAM Requirements · v3.3.5 · 2026-10-28 | v3.3.5 | 1.4 GiBrange 1.3–1.4 · 3 runs | 3.6 GiBrange 3.5–3.7 · 3 runs | |
| Immich (no machine learning, 2 GiB cap)Immich RAM Requirements · v3.3.5 · 2026-10-28 | v3.3.5 | 1.0 GiBrange 1.0–1.3 · 3 runs | 1.5 GiBrange 1.5–1.6 · 3 runs | |
| Immich (no machine learning)Immich RAM Requirements · v3.3.5 · 2026-10-28 | v3.3.5 | 1.1 GiBrange 1.0–1.1 · 3 runs | 1.6 GiBrange 1.6–1.7 · 3 runs | |
| ownCloud Infinite ScaleSelf-Hosted Alternative to Google Drive · 8.2.2 · 2026-10-28 | 8.2.2 | 152 MiBrange 95–165 · 3 runsvaries between runs | 314 MiBrange 313–315 · 3 runs | |
| BorgBackup backup benchmarkRestic vs Borg vs Kopia · 1.4.5 · 2026-10-19 | 1.4.5 | Command-line tool, RAM in the measured table | ||
| Kopia backup benchmarkRestic vs Borg vs Kopia · 0.23.1 · 2026-10-19 | 0.23.1 | Command-line tool, RAM in the measured table | ||
| restic backup benchmarkRestic vs Borg vs Kopia · 0.19.1 · 2026-10-19 | 0.19.1 | Command-line tool, RAM in the measured table | ||
| NextcloudSelf-Hosted Alternative to Google Drive · 35.0.2 · 2026-10-18 | 35.0.2 | 297 MiBrange 295–301 · 3 runs | 452 MiBrange 402–479 · 3 runs | |
| File BrowserSelf-Hosted Alternative to Google Drive · 2.63.23 · 2026-10-16 | 2.63.23 | 15 MiBrange 13–15 · 3 runs | 23 MiBrange 21–23 · 3 runs | |
| SeafileSelf-Hosted Alternative to Google Drive · 13.0.28 · 2026-10-16 | 13.0.28 | 616 MiBrange 590–759 · 3 runs | 905 MiBrange 876–911 · 3 runs | |
Total RAM across all containers of the stack you would run, on our lab host (a 2-vCPU GitHub Actions runner), after the stack settled. Containers that only the lab adds, such as a test target, are not counted. Command-line tools show no stack RAM: their own memory is in the article. Each figure is the median of repeated fresh runs, with the lowest to highest value below it; "1 run" marks a result we have not repeated yet. Peak is the median of the highest totals under load. MiB and GiB are binary units. Per-container figures, every run, the lab host and the raw JSON are in each Test box. Why we repeat runs.
Start here
- AppsDocker deploy guides, comparisons and SaaS alternatives for self-hosted apps, with idle and peak RAM measured in our lab.
- HardwareIn-progress hub for home server hardware: mini PCs, NAS boxes and drives. There are no hardware pages yet. App RAM from our lab is on the Apps hub.
- VPSIn-progress hub for VPS plans for self-hosting. There are no provider reviews yet and we have not tested any plan. App RAM from our lab is on the Apps hub.
- Local AIIn-progress hub for running local AI tools such as Ollama and Open WebUI on your own hardware. There are no guides or benchmarks yet.
- StackThe plumbing around your apps: reverse proxies, remote access, single sign-on, backups, Docker and monitoring.
- Every number comes from a Docker run
- Versions pinned
- Compose files verified
- AI-run lab, human editor
Latest articles
Evidence: MixedStack
authentik Docker Compose: Verified on 2026.8.5
authentik Docker Compose, verified on 2026.8.5: three containers, no Redis, 1,067 MiB idle, a 2 GB plan, first-run setup, proxy rules and an IPv6 listen fix.
- Idle RAM
- 1.0 GiBrange 840 MiB–1.0 GiB · 3 runs
- Peak RAM
- 1.1 GiBrange 918 MiB–1.1 GiB · 3 runs
Evidence: MixedApps
Pi-hole Docker Compose (v6): Verified 2026.10.1
Pihole Docker Compose for v6, verified on 2026.10.1: 9.3 MiB idle, password by environment variable, the port 53 fix and v5 variable changes.
- Idle RAM
- 9 MiBrange 9–10 · 3 runs
- Peak RAM
- 18 MiBsame when rounded in all 3 runs
Evidence: TestedApps
How Much RAM Do Self-Hosted Apps Need? Idle and Peak
How much RAM do self-hosted apps need? Idle and peak RAM for the apps we tested, from Pi-hole to Immich, with the RAM each needs by our sizing rule.
Evidence: TestedApps
Uptime Kuma Docker Compose: 123 MiB Idle, 30 Monitors
Uptime Kuma 2.5.9 Docker Compose file, tested: 123 MiB idle, 139 MiB with 30 monitors, so 1 GB is enough. Backup and restore checked.
- Idle RAM
- 123 MiBrange 122–124 · 3 runs
- Peak RAM
- 139 MiBrange 138–140 · 3 runs
Evidence: TestedApps
How to Back Up Self-Hosted Bitwarden (Vaultwarden)
How to back up self-hosted Bitwarden (Vaultwarden 1.37.5): three methods restored 15 of 15 checks in all 3 runs; a plain file copy lost 12 to 86 items.
Command-line tool, RAM in the measured table
Evidence: MixedStack
Authentik vs Authelia: Measured RAM per Container
Authentik vs Authelia, measured on one host: authentik idled at 1,067 MiB in 3 containers, Authelia at 56 MiB in 1. Not the same work per login.
- Idle RAM
- 1.0 GiBrange 840 MiB–1.0 GiB · 3 runs
- Peak RAM
- 1.1 GiBrange 918 MiB–1.1 GiB · 3 runs