Getting started with self-hosting
This path is written by Ben Liu for individuals and small teams who want control without drowning in options. Follow the steps in order. Skip shiny extras until the first service is reliable.
1. Pick one job-to-be-done
Replace one SaaS habit: passwords, photos, notes, or bookmarks. Write the success criteria and acceptable downtime before you open a terminal.
Read the primer →2. Shortlist with a curated stack
Open a curated stack for your job (Docker-first starter, privacy essentials, etc.). Prefer projects with recent activity and clear upstream docs. Avoid installing twenty containers on day one.
Browse stacks →3. Deploy the smallest useful slice
Start with Compose behind a reverse proxy. Do not expose admin UIs publicly on day one. Get automatic TLS (ACME) and a hostname working first.
Automatic SSL certificates →4. Prove backups with a restore drill
Take a backup, restore to a spare project or host, open three real files, and time it. Only then migrate real data.
Restore drill playbook →5. Harden and monitor lightly
Lock down ports, rotate secrets, and add disk/certificate alerts. Expand the stack only after the first service is boring.
Hardening checklist →First 30 days (week by week)
If you prefer a calendar instead of a checklist, follow the same order: one service in week 1, a proven restore in week 2, light hardening in week 3, and a family handoff in week 4. Expanding before restore drills is the most common beginner failure.
Read the beginner guide (weekend + 30 days) →Starter collections
Shortlists beat infinite scrolling when you are choosing a first rack.
- Docker-first starter stack
Compose-friendly picks for reverse proxy, vault, photos, and a homepage — a practical first rack.
- Privacy-minded essentials
DNS filtering, sync, notes, and analytics with fewer third parties in the path.
- Reading and capture stack
RSS, later-reading, and bookmarks — keep articles and links off opaque SaaS timelines.
Recommended starter reading
- Reverse Proxy and Automatic TLS for Homelabs
One ops guide for reverse proxy + ACME: what a proxy solves, Caddy/Traefik/Nginx fit, certificate renewal, Docker wiring, failure modes, and troubleshooting — without three overlapping primers.
- Family Handoff Docs: Keep the Homelab Alive Without You
Write a one-hour handoff pack so a partner or friend can restart services, restore from backup, and contact you with useful facts.
- Restore Drill Playbook: Prove Backups Before You Trust Them
A practical restore drill: what to back up, how to restore to scratch, offsite S3-compatible copies, and a calendar you will actually keep.
- VPS vs Home Lab: Which Host Belongs Where?
A calm comparison of cost, latency, power, and blast radius for common self-hosted workloads.
- Docker Compose Hardening Checklist for Home Servers
Practical defaults for networks, secrets, updates, and least privilege on a personal Docker host — with lab notes from real breakages.
- Updating Self-Hosted Apps Without Fear
A repeatable update ritual: changelog, snapshot, migrate, verify, and roll back — with lab notes from upgrade nights.
- The Real Cost of Self-Hosting: Money, Time, and Attention
Line-item costs beyond hardware: power, disks, domains, backups, failure time, and when SaaS is cheaper in attention.
- How to Choose Your First Self-Hosted Stack (App Selection Only)
Constraint-first shortlist for your first apps — not a second beginner primer. Pair with the self-hosting beginner pillar for weekend/30-day calendars.
- Lightweight Monitoring for a Home Lab That You Will Actually Maintain
Uptime checks, disk alerts, and notification channels that do not create alert fatigue.
- Self-Hosting Beginner Guide: First Weekend and First 30 Days
A practical beginner guide: what you actually take on, a Saturday–Sunday build that proves TLS and restore, and a week-by-week first month — without competing primer pages.
Safety reminder
Self-hosting can expose personal data if misconfigured. Keep admin panels private, enable updates, and never reuse weak passwords on internet-facing services. When unsure, read the FAQ, how we review, or contact us.