Layer 5 · self-hosting reality check
What it actually takes to self-host Home Assistant
The docs say 2 GB. In practice you want 4 GB once you add add-ons and a database. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Proprietary Smart-Home Hubs alternatives, where Home Assistant is one of the picks.
| RAM — documented minimum | 2 GB |
|---|---|
| RAM — what it really needs | 4 GB once you add add-ons and a database |
| CPU | 2 vCPU; a Raspberry Pi 4 works but an SSD is essential |
| Disk | 32 GB minimum, and never an SD card |
| Monthly cost | $0 on a Pi you own, or $15–25/mo on a VPS — though local is the right answer |
| Setup time | 2 hours, then months of tinkering |
| How you install it | Home Assistant OS on dedicated hardware is the supported path; Container loses the add-on store |
| Ongoing maintenance | Active. Monthly releases occasionally ship breaking changes to integrations. |
| Where it stops scaling | Hundreds of devices on modest hardware. The database, not the automation engine, is the constraint. |
The thing that catches people out
The recorder database writes constantly — every state change from every entity — and on an SD card that kills the card in months. It is the single most common Home Assistant failure and it presents as random corruption rather than a disk error. Use an SSD, and set `recorder` exclusions for chatty entities before the database reaches several gigabytes.
When not to self-host Home Assistant
You want it in the cloud. Home Assistant's value is local control of local devices; a VPS puts the internet between you and your light switch.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does Home Assistant actually need?
- 4 GB once you add add-ons and a database in practice. The documented minimum is 2 GB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU; a Raspberry Pi 4 works but an SSD is essential alongside it.
- What does self-hosting Home Assistant cost per month?
- $0 on a Pi you own, or $15–25/mo on a VPS — though local is the right answer This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for active. Monthly releases occasionally ship breaking changes to integrations.
- How long does it take to set up Home Assistant?
- 2 hours, then months of tinkering, via Home Assistant OS on dedicated hardware is the supported path; Container loses the add-on store.
- When should I NOT self-host Home Assistant?
- You want it in the cloud. Home Assistant's value is local control of local devices; a VPS puts the internet between you and your light switch.
- What is the most common mistake when self-hosting Home Assistant?
- The recorder database writes constantly — every state change from every entity — and on an SD card that kills the card in months. It is the single most common Home Assistant failure and it presents as random corruption rather than a disk error. Use an SSD, and set `recorder` exclusions for chatty entities before the database reaches several gigabytes.