Self-hosting sounds great in theory, and running your own password manager, blocking ads across your entire network, and keeping your data on hardware you own instead of someone else's server are all genuinely nice benefits of it. The problem is that actually doing it usually means a lot of work, like maintaining Docker Compose files, understanding basic networking, setting up reverse proxies, and debugging things late at night on a week day when something inevitably breaks. For a lot of people, that's where the enthusiasm dies, and I totally get it.

But what if you could skip most of that? Home Assistant's "Apps" repository, which used to be called " add-ons" before the 2026.2 update renamed them, turns a smart home hub into a self-hosting platform with one-click installs and automatic updates. I've been running several self-hosted services through Home Assistant for nearly a year at this point, and honestly, it's the easiest way into self-hosting I've found. And I say that as someone experienced with self-hosting in the first place.

Apps are just Docker containers with the hard parts stripped away

The rename makes a lot of sense

If you've been using Home Assistant for a while, you know these as add-ons. The rename to "apps" happened in the February 2026 release, and it's purely cosmetic, packing no functional changes and no need to reinstall anything. Your existing add-ons migrated automatically, though "migrated" is probably too strong of a term here. The reasoning is simple: people kept confusing "add-ons" with "integrations," which are a completely different thing. An integration connects Home Assistant to a device or service. An app is a standalone application running alongside Home Assistant.

Under the hood, apps are Docker containers managed by the Home Assistant Supervisor. The Supervisor handles pulling images, configuring networking, managing storage, and orchestrating updates. You don't see any of this. You go to Settings, tap Apps, find what you want, and hit install. That's it; you don't need a terminal, you don't create or maintain any compose files, and you don't have to worry about port mapping.

Take Mosquitto as an example. If you wanted to run an MQTT broker the traditional way, you'd need to pull the Docker image, configure a Compose file with the right ports and volumes, set up authentication (if you wanted it), and make sure it restarts on boot. With Home Assistant, you tap install on the Mosquitto app, and it's running. The MQTT integration then connects Home Assistant Core to the broker automatically. Two clicks, and your Zigbee2MQTT devices can start talking to Home Assistant. While some would argue that Home Assistant has a steep learning curve, what it gives back in ease-of-use when it comes to self-hosted applications can often outweigh the length of time learning Home Assistant in the first place.

You don't need to touch a terminal to self-host

One click and you're running a password manager

The app store that Home Assistant includes has a lot of self-hosted services out of the box, and a lot of them actually have nothing to do with home automation. Many of them are worth installing, as they greatly simplify the process of self-hosting some of the most popular applications.

For example, Vaultwarden is the one I recommend first. It's a lightweight, Bitwarden-compatible password manager that runs on SQLite by default. Install it through Home Assistant, and you've got a working password vault on your local network. Your family's passwords live on hardware in your house, not on someone else's server, and the whole setup takes about two minutes.

AdGuard Home is another solid pick. It's a network-wide DNS-based ad and tracker blocker, not too different from the kind of thing you'd normally set up Pi-hole for. Point your router's DNS settings at your Home Assistant box, and every device on your network gets ad blocking without installing anything on individual devices.

As well, tools like Node-RED gives you a visual, drag-and-drop automation builder that goes well beyond what Home Assistant's built-in automations can do. And if you're into monitoring, there's InfluxDB for time-series data storage and Grafana for building dashboards on top of it.

Compare that to doing it manually. Setting up Vaultwarden in Docker means writing a Compose file, configuring environment variables, mapping ports, setting up a reverse proxy if you want HTTPS, and figuring out backups on your own. In Home Assistant, you install the app and the Supervisor handles the rest. Updates happen automatically, and backups are included in Home Assistant's built-in backup system. All of this means that when you back up your smart home configuration, your self-hosted services are included too.

The app store is bigger than you think

Just keep a few things in mind

Home Assistant ships with an official app repository, but there's also a community repository (addons.community) that's enabled by default and adds a bunch more. On top of that, there are many other unofficial repositories out there that you can set up and install. I use cs2mqtt installed as an unofficial repository, for example.

For management, you can run Studio Code Server (a full VS Code instance in your browser), Samba Share for accessing config files over your network, and Terminal & SSH for when you do want command-line access. Protocol support covers Zigbee2MQTT, Z-Wave JS UI, and ESPHome for custom ESP32 devices. You can even run Plex Media Server or a UniFi Controller as Home Assistant apps.

Not every Docker container has an equivalent app, and that's a fair limitation. If you need something niche, you'll still have to set it up manually. But for the most common self-hosted services, there's a good chance an app already exists.

This approach works because it lets you learn as you go. You start with Home Assistant OS on the device of your choosing, like a Raspberry Pi or in a virtual machine. Then, you install a few management apps like Samba and the File Editor to get comfortable. After that, you add AdGuard or Vaultwarden, and suddenly you're self-hosting real services without having written a single line of a Docker Compose file.

From there, you might get curious and wonder how the networking works, or you might wonder about other containers that aren't available as an app to install. You might outgrow Home Assistant's hand-holding approach by that stage, but by then, you'll likely understand the baseline concepts such as containers, volumes, networking, and backups, because you'll have been using them through Home Assistant's friendlier interface the whole time.

It's important to keep in mind that apps are only available if you're running Home Assistant OS. If you're on a Container installation, you don't get the app store, and you'd need to set up those Docker containers yourself, which defeats the purpose for a new-to-self-hosting user. With the Core and Supervised installation methods being deprecated (support ended with release 2025.12), HAOS is becoming the clear default path anyway.

Resource constraints are real on low-power hardware. A Home Assistant Green or Raspberry Pi will handle the core platform and a handful of apps just fine, but start stacking Plex, InfluxDB, Grafana, and several other services on top, and you'll feel the limits. Keep an eye on CPU and memory usage if you're running on modest hardware. Don't forget about security either. Keep Home Assistant updated, be careful about exposing it to the internet, and make sure you're running regular backups before experimenting with new apps. This is your hardware and your responsibility, meaning that there's no cloud provider managing uptime for you.

Home Assistant's app store won't replace a full self-hosting setup for power users. It's not meant to. But for anyone who's been interested in self-hosting and hasn't known where to start, it's the easiest way in that I've come across. You get real, functional self-hosted services running on a box that also happens to control your smart home, and you didn't have to write a single line of a Docker Compose file to get there.