Self-Hosted Infrastructure

The recurring pattern across this knowledge base: tools that let you

own your stack. Not SaaS, not cloud-managed -- your hardware, your data,

your uptime.

Key Entries

• **Coolify** -- self-hosted Heroku/Vercel alternative. Deploy apps, databases,

services on your own servers. The missing PaaS for people who own metal.

• **Listmonk** -- high-performance newsletter manager in Go. No Mailchimp,

no Substack taking a cut.

• **Pocket ID** -- self-hosted OIDC provider with passkey support. Authentication

without Auth0.

• **ESPHome** -- firmware framework for ESP32 devices. Your smart home, your

firmware, your rules.

The Pattern

Every SaaS product is a self-hostable weekend project once you understand the

protocol. OIDC is a spec. SMTP is a spec. HTTP is a spec. The value prop of

SaaS is operational burden, not technology. These tools collapse that burden.

Connections

• Links to Open Firmware Movement -- same

philosophy applied to consumer hardware

• Links to Privacy-First Tools -- self-hosting

is the ultimate privacy guarantee

• Links to ESP32 Ecosystem -- the hardware

substrate for self-hosted IoT

Open Questions

• What's the minimum viable self-hosted stack? DNS + reverse proxy + auth + email?
• When does self-hosting become more expensive than SaaS? At what scale?
• How do you handle backups and disaster recovery without a team?