Self-Hosted Apps Distributed as Single Static Binaries Instead of Interpreter-Plus-Docker Stacks
A photo of a self-hosting newbie getting cooked by n8n + Python topped r/selfhosted with 3,372 upvotes and triggered a long, knowledgeable thread about why FOSS web apps are still so painful to install. The recurring complaint isn't that Docker is hard — it's that every project ships a 200-line compose file with hardcoded hosts, missing env vars, weird non-root UID gotchas, and an interpreter (Python, PHP, Ruby, Node) that drags in its own version-management hell. Multiple top commenters explicitly ask for an Apple-style 'self-contained binary, no external dependencies, no interpreters' as the FOSS default. Caddy already proves the pattern works. The wedge isn't a new self-hosted app — it's a curated catalog or build-tooling layer that systematically converts the popular FOSS web apps into single-binary distributions.
Two paths and they don't compete. Path A is a packager — a tool that takes a popular self-hosted Python/Node app and produces a single static Linux binary with embedded SQLite by default and PG/MySQL behind a flag. Path B is a 'works from defaults' grade for the existing catalog: install every app from its quickstart on a fresh VM, score it on whether the user hits any error before first successful login, and rank publicly. Path B is achievable in a weekend and would do more for the ecosystem than another Umbrel competitor.
landscape (5 existing solutions)
The self-hosted ecosystem keeps adding higher-level wrappers (Umbrel, Coolify, Cosmos) but the underlying apps still ship as interpreter-plus-database compose files with subtle bugs the wrapper can't fix. Caddy is the lone proof that a popular FOSS app can ship as one Go binary with sane defaults. Nobody is funding the unglamorous work of converting Vaultwarden, Immich, Paperless, Audiobookshelf, Linkwarden, etc. into the same shape — or, at minimum, scoring and ranking apps by 'works from defaults' so non-technical users can pick safely.