State of Self-Hosting 2026

Key Findings

We analyzed 1,165 articles covering 370 self-hosted apps across 93 categories to produce the most comprehensive snapshot of the self-hosting ecosystem in 2026. Here’s what the data says.

60% of self-hosted apps run on less than 256 MB of RAM. Most can run on a $5/month VPS or a Raspberry Pi.
PostgreSQL powers nearly 1 in 3 self-hosted apps (90 of 315), making it the dominant database in the ecosystem.
An individual can save $7,700–9,200 per year by replacing their cloud subscriptions with self-hosted alternatives.
A 10-person team can save $76,500–118,500 per year by self-hosting core business tools instead of paying for enterprise SaaS.
AI/ML tools are the most resource-hungry category. 6 of the 12 heaviest apps are AI-related, requiring 4–16 GB of RAM.
The lightest apps use just 10 MB of RAM — less than a single Chrome tab.

Methodology

This report is based on data extracted from our library of 1,165 articles published in February 2026. Every app guide includes verified Docker Compose configurations, resource requirement measurements, and cost comparisons sourced from official documentation and GitHub repositories.

Data Source	Scope
App guides analyzed	315
Comparison articles analyzed	430
Replace guides (SaaS alternatives)	113
Unique apps covered	370
Unique categories	93
Docker Compose configs reviewed	189
Cost comparison tables reviewed	105

All Docker configurations were verified against official sources. Resource measurements reflect documented idle-state requirements. Cost data uses current public pricing as of February 2026.

The Self-Hosting Landscape

93 Categories and Growing

Self-hosting in 2026 covers far more than file storage and media servers. We cataloged 93 distinct categories of self-hosted software — from the expected (password managers, VPNs, note-taking) to the niche (genealogy tools, digital signage, podcast hosting).

The top 10 categories by content depth:

Rank	Category	Apps Covered	Articles
1	Media Servers	15	61
2	Note Taking & Knowledge	16	53
3	Reverse Proxy & SSL	7	51
4	Docker Management	9	34
5	Photo & Video Management	7	32
6	VPN & Remote Access	11	31
7	Download Management	17	28
8	Home Automation	9	27
9	Social Networks & Forums	8	25
10	Password Management	7	23

Media servers dominate, reflecting the community’s enduring appetite for personal media management. The download management category’s 17 apps illustrate how the *arr stack ecosystem (Sonarr, Radarr, Prowlarr, and friends) has become one of the most sophisticated self-hosted toolchains.

370 Unique Apps

The most referenced apps across our entire content library:

Rank	App	Total Articles	Primary Category
1	Jellyfin	25	Media Servers
2	BookStack	20	Note Taking & Knowledge
3	Navidrome	20	Music & Audio
4	Caddy	17	Reverse Proxy & SSL
5	Outline	17	Note Taking & Knowledge
6	Plex	16	Media Servers
7	Traefik	15	Reverse Proxy & SSL
8	Immich	14	Photo & Video Management
9	Nextcloud	14	File Sync & Storage
10	Portainer	14	Docker Management

Jellyfin’s position at the top reflects its status as the leading open-source media server. Plex, though proprietary, remains in the top 10 because most comparison articles pit it against Jellyfin. Immich’s rapid rise — from a new project to one of the most-discussed self-hosted apps — is the story of 2025-2026.

Docker Configuration Patterns

We reviewed 189 Docker Compose configurations across 315 app guides to identify how the self-hosted ecosystem actually works under the hood.

The Database Layer

Database	Apps Using It	Share
PostgreSQL	90	28.6%
MySQL/MariaDB	49	15.6%
Redis (caching)	42	13.3%
SQLite	41	13.0%
Elasticsearch/OpenSearch	6	1.9%
Valkey (Redis fork)	5	1.6%
MongoDB	3	1.0%

PostgreSQL is the undisputed database of self-hosting. It backs nearly 1 in 3 apps we reviewed. The PostgreSQL + Redis combination is the most common stack pattern — used by apps from Immich to Outline to n8n.

SQLite’s 13% share is notable. These are typically lightweight, single-purpose apps (Baikal, ntfy, Miniflux) that embed their database and need no separate container. For users running a handful of small services, SQLite apps are the easiest to deploy and maintain.

The Valkey entry is a 2026 development: five apps have already switched from Redis to this open-source fork following Redis’s license change. Expect this number to grow.

Image Sources

Registry	Share
Docker Hub	77.0%
GitHub Container Registry (ghcr.io)	14.3%
LinuxServer.io (lscr.io)	6.2%
Other	2.5%

Docker Hub remains dominant, but GitHub Container Registry is gaining ground — especially among newer projects that want tighter integration with their CI/CD pipelines. LinuxServer.io maintains curated images for 44 apps in our library, providing consistent PUID/PGID user mapping and Alpine-based containers.

The Most Common Docker Images

Rank	Image	Count	Purpose
1	`postgres:16-alpine`	54	Database
2	`redis:7-alpine`	20	Cache
3	`mariadb:11.7`	10	Database
4	`mariadb:10.11`	8	Database (legacy)
5	`redis:7.4-alpine`	6	Cache

Alpine-based images lead every major category. The self-hosting community has decisively moved toward minimal container images for smaller attack surfaces and faster pulls.

Port Patterns

Container Port	Count	Typical Use
:80	79	HTTP web servers
:8080	64	Alternative HTTP / app UIs
:3000	32	Node.js apps, Grafana, Gitea
:443	28	HTTPS
:8000	25	Python/Django apps

The most common port mapping is 8080:80 (39 occurrences) — remapping container port 80 to host port 8080 to avoid conflicts with other services. This is the first thing most self-hosters learn to change.

Environment Variables

Rank	Variable	Count	Purpose
1	`TZ`	111	Timezone
2	`POSTGRES_PASSWORD`	108	Database password
3	`POSTGRES_USER`	95	Database username
4	`POSTGRES_DB`	94	Database name
5	`PUID` / `PGID`	57 each	LinuxServer.io user mapping
6	`DB_PASSWORD`	46	Generic database password
7	`MYSQL_ROOT_PASSWORD`	39	MySQL/MariaDB root password
8	`DATABASE_URL`	28	Connection string
9	`ADMIN_PASSWORD`	20	Application admin
10	`SECRET_KEY`	18	Application secret

TZ (timezone) is the most common environment variable in self-hosted apps — appearing in 111 of 315 guides. Database credentials dominate the rest of the list. The inconsistent naming conventions (DB_PASSWORD vs MYSQL_PASSWORD vs POSTGRES_PASSWORD) reflect the self-hosted ecosystem’s organic growth: there’s no committee standardizing app configuration.

Volume Patterns

Volume Type	Count	Share
Named volumes	708	61.7%
Bind mounts	440	38.3%

Named volumes are preferred over bind mounts at a nearly 2:1 ratio. Docker best practices recommend named volumes for database storage (where consistent permissions and Docker-managed lifecycle matter), while bind mounts are common for configuration files and media libraries where direct filesystem access is needed.

The Docker socket mount (/var/run/docker.sock) appears in 33 guides — the gateway to container management tools like Portainer, Watchtower, and Dockge. Mounting the Docker socket is a necessary convenience, but it grants root-equivalent access to the host. Every guide that includes it should note the security implications.

Configuration Quality

98.4% of Docker Compose files include restart: unless-stopped
100% of images use pinned version tags (no :latest)

These near-perfect scores reflect the self-hosting community’s maturity around reliability. An app that doesn’t restart after a reboot is an app you’ll forget about until it’s needed.

Resource Requirements

Most Self-Hosted Apps Are Lightweight

We extracted resource requirements from 278 app guides with parseable data. The results challenge the assumption that self-hosting requires expensive hardware.

RAM Distribution

Category	Count	Percentage
Light (<256 MB)	167	60.1%
Moderate (256 MB – 1 GB)	59	21.2%
Heavy (1 – 4 GB)	39	14.0%
Very Heavy (4+ GB)	12	4.3%

60% of self-hosted apps run on less than 256 MB of RAM. This means the majority of the self-hosting ecosystem is accessible on minimal hardware — a Raspberry Pi 4 with 4 GB of RAM can comfortably run a dozen lightweight services simultaneously. A $5/month VPS with 1 GB of RAM handles most single-app deployments.

Only 18% of apps need 1 GB or more. These tend to be complex platforms (Nextcloud, GitLab, Discourse) or AI/ML tools.

The Most Resource-Hungry Apps

App	Idle RAM	Category
vLLM	16 GB	AI/ML
ComfyUI	8 GB	AI/ML
PostHog	8 GB	Analytics
Stable Diffusion WebUI	8 GB	AI/ML
Text Generation WebUI	8 GB	AI/ML
Zammad	6 GB	Helpdesk
LocalAI	4 GB	AI/ML
Mailcow	4 GB	Email
OpenProject	4 GB	Project Management
Penpot	4 GB	Design
Plane	4 GB	Project Management
Tabby	4 GB	AI/ML

6 of the 12 most resource-demanding self-hosted apps are AI/ML tools. Self-hosted AI is the newest and most resource-intensive frontier. Running your own LLM inference (vLLM, Text Generation WebUI) requires dedicated GPU hardware and 16+ GB of RAM — a fundamentally different hosting profile from running Pi-hole or Vaultwarden.

This creates a clear two-tier self-hosting world: lightweight utility apps that run anywhere, and AI workloads that demand serious hardware.

The Lightest Apps

App	Idle RAM	Category
LazyDocker	10 MB	Docker Management
MicroBin	10 MB	Pastebin
Mosquitto	10 MB	IoT/MQTT
Nginx	10 MB	Web Server
Sonic	10 MB	Search
HAProxy	15 MB	Load Balancer
PocketBase	15 MB	Backend
Watchtower	15 MB	Container Updates
Baikal	20 MB	CalDAV/CardDAV
Caddy	20 MB	Web Server

The lightest self-hosted apps use just 10 MB of RAM — less than a single Chrome tab. These are almost all single Go or Rust binaries that embed their functionality without framework overhead. PocketBase (15 MB) is particularly remarkable: a complete backend-as-a-service with authentication, database, and file storage in a single 10 MB binary.

CPU Requirements

Level	Count	Percentage
Negligible / Very Low / Minimal	83	26.7%
Low	103	33.1%
Low-Medium	30	9.6%
Medium / Moderate	20	6.4%
Medium-High or High	4	1.3%

Nearly 60% of self-hosted apps have Low or lower CPU requirements. Even on a Raspberry Pi’s ARM processor, most services idle at near-zero CPU usage and only spike during active requests.

Disk Space

Category	Count	Percentage
Tiny (<200 MB)	111	43.4%
Small (200 MB – 1 GB)	82	32.0%
Medium (1 – 5 GB)	31	12.1%
Large (5+ GB)	32	12.5%

75% of apps need less than 1 GB for the application itself (not counting user data). The largest disk footprints belong to AI model storage (text-generation-webui: 100 GB) and video surveillance systems (Frigate, ZoneMinder: 50 GB each) — both of which store massive datasets by design.

Hardware Recommendation by Workload

Based on the resource data, here’s what you actually need:

Workload	Recommended Hardware	Monthly Cost
1–5 lightweight apps (Pi-hole, Vaultwarden, ntfy)	Raspberry Pi 4 (4 GB) or $5/mo VPS	$0–5
5–15 mixed apps (Nextcloud, Jellyfin, Gitea, monitoring)	Mini PC (N100, 16 GB RAM) or $15/mo VPS	$5–15
15–30 apps including heavy ones (GitLab, Discourse, Mailcow)	Used Dell Micro (32 GB RAM) or $30/mo VPS	$10–30
AI/ML workloads (Ollama, Stable Diffusion, vLLM)	Desktop with GPU (RTX 3060+, 32 GB RAM)	$15–40 (electricity)

The Cost of Cloud vs Self-Hosting

We reviewed 113 replace guides comparing self-hosted alternatives to paid cloud services. The savings range from negligible (free-tier services) to staggering (enterprise SaaS).

113 Cloud Services With Self-Hosted Alternatives

Our library covers self-hosted alternatives to 113 cloud services, spanning every major category:

Productivity: Google Docs, Notion, Confluence, Evernote, OneNote, Todoist, Trello, Asana, Jira, ClickUp
Storage & Sync: Google Drive, Dropbox, OneDrive, iCloud Drive, Box, WeTransfer
Media: Netflix, Spotify, YouTube, Amazon Music, Apple Music, Apple TV+, Kindle Unlimited, Audible, Tidal
Communication: Slack, Discord, Teams, Zoom, Google Meet
Security: 1Password, LastPass, Dashlane, Bitwarden Cloud, NordVPN, ExpressVPN, Auth0, Okta
Business: Salesforce, HubSpot, Zendesk, Shopify, QuickBooks, Mailchimp, Typeform
Development: GitHub Codespaces, Heroku, Docker Desktop, GitHub Copilot, Managed Kubernetes

Biggest Savings: Enterprise SaaS

Cloud Service	Cost (25 users/yr)	Self-Hosted Cost/yr	Annual Savings
Salesforce	$24,000	$120–240	$23,760+
HubSpot Professional	$21,372	$120–240	$21,132+
Slack Business+ (200 users)	$21,000	$180–480	$20,520+
Jira Premium (100 users)	$16,000	$120–480	$15,520+
Microsoft Teams (200 users)	$14,400	$360–720	$13,680+
Zendesk Business (10 agents)	$13,800	$120	$13,680
Auth0 Professional	$12,000+	$120	$11,880+
Okta Adaptive MFA (100 users)	$7,200–18,000	$120	$7,080–17,880

Per-seat enterprise SaaS offers the most dramatic savings. A 200-person organization paying $21,000/year for Slack Business+ could run Mattermost or Rocket.Chat on a $15/month VPS for under $500/year. The self-hosted version handles the same features — channels, threads, file sharing, integrations — without the per-user pricing model that makes enterprise SaaS expensive at scale.

Individual Savings

Scenario	Cloud Cost/yr	Self-Hosted Cost/yr	Annual Savings
All consumer services (maximal)	$8,000–9,500	$100–300	$7,700–9,200
Top 10 services (realistic)	$1,500–2,000	$60–120	$1,380–1,880

For individuals, the highest-impact replacements are:

Cloud storage — Google Drive/Dropbox ($120–240/yr) → Nextcloud ($0–60/yr)
Streaming — Netflix + Spotify ($300+/yr) → Jellyfin + Navidrome ($0 with existing media)
Password manager — 1Password/LastPass ($36–48/yr) → Vaultwarden ($0)
VPN — NordVPN/ExpressVPN ($100–150/yr) → WireGuard/Tailscale ($0)
Photo backup — Google Photos/iCloud ($30–120/yr) → Immich ($0)

Self-Hosting Cost Tiers

Tier	Monthly Cost	What You Get
Free (existing hardware)	$0	Raspberry Pi, old laptop, NAS you already own
Electricity only	$2–5/mo	Running 24/7 on owned hardware
Shared VPS	$3–5/mo	1–3 lightweight apps
Dedicated VPS	$5–15/mo	Most single-app deployments
Medium VPS	$10–20/mo	Full home server stack
Heavy VPS	$15–40/mo	Enterprise-scale or AI workloads

The floor is $0 for someone with a Raspberry Pi and a few lightweight apps. The ceiling for most home self-hosters is $10–20/month for a VPS or the equivalent in electricity for home hardware. Only AI workloads and enterprise-scale deployments push costs higher.

What You Give Up

Self-hosting isn’t free in every dimension. The real costs are:

Time. Initial setup takes 30 minutes to several hours per app. Ongoing maintenance (updates, backups, troubleshooting) adds 1–5 hours per month depending on stack complexity.
Reliability. Cloud providers offer 99.9%+ uptime with professional ops teams. Your home server is as reliable as your internet connection and your willingness to fix things at midnight.
Convenience. Mobile apps for self-hosted services are improving but rarely match the polish of commercial alternatives. Immich’s app is excellent; Nextcloud’s is functional but rough around the edges.
Support. When something breaks, you’re the support team. Community forums and Discord servers are helpful but not the same as a paid support contract.

Ecosystem Signals

Docker Adoption

189 of 315 app guides (60%) include complete Docker Compose configurations. The remaining 40% are apps distributed as binaries, managed services, or platform-specific packages. Docker has become the default deployment method for self-hosted software, but it’s not universal — some categories (home automation, desktop apps) often use native installation.

The LinuxServer.io Effect

LinuxServer.io maintains curated Docker images for 44 apps in our library. Their images follow a consistent pattern:

Alpine-based for minimal size
PUID/PGID environment variables for user mapping
Standardized /config volume mount
Regular automated rebuilds

For apps with a LinuxServer.io image, the setup experience is markedly more consistent. The organization deserves recognition as critical infrastructure for the self-hosting ecosystem.

Alpine Dominance

Alpine Linux-based images lead every major dependency category. postgres:16-alpine, redis:7-alpine, and node:20-alpine appear far more frequently than their Debian-based equivalents. The self-hosting community has voted with its Dockerfiles: smaller images, faster pulls, reduced attack surface.

The Valkey Migration

Five apps in our library have already switched from Redis to Valkey following Redis’s 2024 license change from BSD to dual SSPL/RSAL. This is still early — the majority use standard Redis images — but the trend is clear. Expect Valkey adoption to accelerate as more projects evaluate their Redis dependency.

Trends to Watch in 2026

1. Self-Hosted AI Is Mainstream But Expensive

AI/ML is the fastest-growing self-hosting category. Tools like Ollama, Open WebUI, and Stable Diffusion WebUI have made running models locally accessible to enthusiasts with consumer GPUs. But the resource gap between AI and everything else is enormous — vLLM needs 16 GB of RAM where Pi-hole needs 80 MB. Self-hosted AI is mainstream in interest but limited in practice to users with dedicated GPU hardware.

2. The Photo Management Gold Rush

Immich’s meteoric rise has ignited the self-hosted photo management category. With Google Photos squeezing free storage and Apple locking users into iCloud, the demand for private photo backup is at an all-time high. Immich, PhotoPrism, and LibrePhotos are competing to become the default, with Immich currently leading in community momentum and feature velocity.

Mastodon, GoToSocial, Lemmy, and Pixelfed represent a growing movement toward self-hosted social networking. The Fediverse’s ActivityPub protocol enables federation between independent servers — you host your own instance but can interact with users everywhere. GoToSocial in particular is gaining traction as a lightweight, single-user Fediverse server for personal use.

4. The *arr Stack as an Ecosystem Standard

The *arr family (Sonarr, Radarr, Lidarr, Readarr, Prowlarr) has evolved from individual tools into a deeply integrated media automation platform. Combined with Jellyfin and Jellyseerr, it creates a complete end-to-end media management pipeline. The *arr stack is to media what the LAMP stack was to web development: a well-understood, opinionated architecture that most practitioners adopt wholesale.

5. Authentication Consolidation

Authentik, Authelia, and Keycloak are bringing enterprise-grade SSO to home servers. As self-hosters run 10, 20, or 50 services, managing individual logins per app becomes unsustainable. Expect authentication middleware to become standard infrastructure in 2026 — not a luxury, but a necessity.

How This Report Was Produced

This report was compiled entirely by AI agents as part of the selfhosting.sh content library. Data was extracted from 1,165 articles using automated analysis of frontmatter metadata, Docker Compose configurations, resource requirement sections, and cost comparison tables.

All underlying data, Docker configurations, and cost comparisons are available in our individual app guides, comparison articles, and replace guides at selfhosting.sh.