Self-hosting has a PR problem. On one end you’ve got the homelabbers who run 40 Docker containers on a server rack in their basement and don’t understand why you wouldn’t do the same. On the other end you’ve got the “just use the cloud” crowd who wave away any attempt at running your own stuff as some kind of unnecessary nerd cosplay.
Both camps are wrong. And neither one is going to give you a straight answer about whether self-hosting is worth it for the specific thing you’re considering.
I’ve spent the last few months writing a beginner guide to all of this: how to set up a home server for under $200, how to get started with Tailscale, how to run n8n for automation, how to set up Home Assistant. I’ve done the research so those guides aren’t guesswork. And after going through all of it, I have some opinions.
For what it’s worth, I want to be transparent: I don’t personally run a full homelab. My actual production stack is DigitalOcean plus Render plus Hostinger, and I’ve written about why. But I’ve spent a lot of time with this ecosystem, and I know enough to tell you what’s actually worth your time and what will eat your weekend for no real benefit.
Here’s my survey of the state of self hosting in mid-2026: what’s actually worth the effort and what isn’t.
The Quick Answer: What to Self-Host and What to Leave Alone
Before I get into the details, here’s the summary table. We’ll dig into each row below.
| Category | Self-Host Pick | Managed Alternative | Effort | Cost Self-Host | Cost Managed | Verdict |
|---|---|---|---|---|---|---|
| Photos | Immich | Google Photos | Medium | ~$5/mo (electricity) | $2-10/mo | Do it |
| Automation | n8n | Zapier | Medium | ~$5-7/mo (VPS) | $30-400+/mo | Do it (>100 workflows/mo) |
| Local AI | Ollama | ChatGPT / Claude API | Low | $0 (existing hardware) | $20-50+/mo | Do it (if hardware fits) |
| Smart Home | Home Assistant | Google Home / Alexa | Medium-High | ~$3/mo (Pi power) | $0 but lock-in | Do it (5+ devices) |
| Password Manager | Vaultwarden | 1Password / Bitwarden Premium | Low | ~$3-5/mo (Pi power or shared VPS) | $1.65-4.49/mo | Do it |
| File Storage | Nextcloud | Google Drive / Dropbox | High | $5-10/mo (VPS+storage) | $10-12/mo | Skip unless privacy-critical |
| (none worth it) | Fastmail / ProtonMail | Very High | Your sanity | $4-5/mo | Do NOT do it |
Now the longer version of why.
Photo Backup: Immich Has Won This Category
This is the clearest win on the list. Immich has matured fast, and as of mid-2026 the feature gap with Google Photos is basically gone. Face recognition, AI-powered search, timeline view, shared albums. It’s all there.
The cost math holds up. Google Photos gives you 15GB free, then it’s $1.99/month for 100GB or $9.99/month for 2TB. Sounds reasonable until you realize a 2TB plan costs $120/year indefinitely. A used mini PC plus a 4TB hard drive to run Immich runs $300-500 one time, with maybe $5/month in electricity. You break even somewhere around 18-24 months. After that you’re paying $60/year for the electricity to run a server that also does everything else on this list.
The privacy argument is even more straightforward. Your photos never leave your house. Not to Google’s servers, not to their training data pipeline, not anywhere. If that matters to you, this is the one to start with.
Effort level: call it 2 hours for initial setup if you follow a solid guide. Maintenance after that is light. Immich’s developers ship updates regularly, Docker Compose handles most of it, and the upgrade process has gotten dramatically better in the last year.
I have a full setup guide for Immich coming later this year if you want the step-by-step.
Workflow Automation: n8n vs Zapier Isn’t Even Close
If you’re doing any workflow automation and you’re paying for Zapier, you should be mad at yourself. I say that with love.
n8n’s self-hosted Community Edition is free. You run it on a $5-7/month VPS and you have unlimited workflow executions. Zapier’s free tier caps out at 100 tasks per month, which you’ll hit if you’re doing anything useful. Zapier Professional is $29.99/month for 750 tasks. And here’s the thing that makes Zapier pricing hurt: they charge per step, not per workflow run. A 10-step workflow costs you 10 Zapier tasks per run.
n8n charges one execution per workflow run regardless of steps. Run that same 10-step workflow 200 times a day and you’ve used 200 n8n executions. On Zapier? 60,000 tasks. That pushes you into their $400+/month enterprise tier for the same workload n8n handles for the cost of a cheap VPS.
Setup is about an hour if you’re comfortable with Docker. The learning curve on actually building workflows is real, but that’s true of any automation platform. My n8n beginner guide walks through the install and your first few workflows.
If I’m being honest, the only reason to stick with Zapier is if you need the polished UI for non-technical collaborators. For solo operators or small teams willing to learn the tool, n8n is the answer.
Running AI Locally: Worth It If the Hardware Already Fits
Ollama has made running local AI models scarily easy. Two commands and you’re running a local AI model. No API key, no monthly bill, no queries leaving your machine.
# Install Ollama (macOS / Linux)
curl -fsSL https://ollama.com/install.sh | sh
# Pull and run a current small model (3.4GB download)
ollama run qwen3.5:4bFor a lot of use cases, it holds up well.
The nuance is in the hardware math. You want at least 8GB of RAM for a useful small model. As of August 2026 the sane first pull is something in the 4B class, like qwen3.5:4b, which is a 3.4GB download and still leaves room for your operating system and the forty browser tabs you are not going to close. Most laptops and mini PCs made in the last three years meet that threshold. If you already have a machine that qualifies, running Ollama costs you nothing beyond the electricity.
Where people get into trouble is buying dedicated hardware for this. A Mac Studio M4 Max starts around $2,500 (Apple bumped prices in June 2026, and it scales higher from there). An RTX 4090 PC runs $2,500 or more now that the 40-series is end-of-life and inventory has dried up. The cost math on those only works if you’re running tens of thousands of AI queries per day, which almost nobody doing homelab stuff actually is. At 1,000 requests a day, cloud APIs run you $30-45/month. You’d be paying for a $2,500+ GPU for a very long time before you broke even.
My advice: try it on hardware you already own. If your current machine can run a 4B model at a usable speed, great. If you find yourself wanting more capability than that, the cloud APIs are better value for most workloads.
The full Ollama setup guide is live if you want the step-by-step install. I also have a follow-up covering Open WebUI and RAG, now live: the Open WebUI and RAG setup guide. If you’re not sure which model to start with, the synthesis of what 311 r/LocalLLaMA replies agreed on is a good starting point for picking your first pull.
Smart Home: Home Assistant Is Still the Right Call
The cost argument for Home Assistant is weaker than people admit. Google Home and Amazon Alexa are free. A Raspberry Pi 4 runs $70 and the HA Green hub runs $99. You’re not saving money on the front end.
The real case for Home Assistant is escape velocity from vendor lock-in. I’ve written about this before in the Home Assistant dashboard guide. When Google or Amazon decides to deprecate a device integration, your automations break and you’re at their mercy. Home Assistant supports thousands of integrations and runs locally, so when Nest changes their API or Wemo discontinues a hub, you fix the Home Assistant integration and move on.
The other thing nobody tells you is that “local processing” isn’t just a privacy benefit. It’s a reliability benefit. Automations running locally don’t have cloud round-trips, they don’t fail when your internet goes down, and they’re not subject to whatever outage Google or Amazon is having today.
Effort level is medium-high. The initial setup has gotten better with the HA Green and Raspberry Pi images, but if you want to do anything more complex than flipping lights on and off, you will end up reading YAML at some point. If you have 5 or more smart home devices and you’re planning to add more, it’s worth that learning curve. If you have a single smart light bulb, just keep using the app.
Tailscale pairs well with Home Assistant for remote access without opening ports. Here’s the guide on setting that up. If you want to extend HA into health metrics without the vendor app in the middle, there’s also a guide to syncing BLE smart scales directly to Home Assistant and Garmin.
Password Managers: Vaultwarden Is the One Nobody Skips
Read enough of these what-should-I-self-host lists and one name shows up on nearly all of them. Vaultwarden. Code Capsules and Hurrikane both put it first in their 2026 roundups, and Hurrikane calls password management the highest-impact, lowest-effort place to start. That much agreement is rare in a hobby where people will argue about Docker versus LXC for six hours.
Vaultwarden is an unofficial Bitwarden-compatible server written in Rust, and the point of it is that it is small. It runs on a Raspberry Pi without complaint. The official Bitwarden server stack wants considerably more machine than that. You point the normal Bitwarden apps and browser extensions at your own server and everything works the way it did before, except the vault lives in your house.
The money argument is weaker here than anywhere else on this list, and I would rather say so than oversell it. Bitwarden Premium is $1.65 a month billed annually, $19.80 for the year. 1Password is $2.99 a month for an individual plan and $4.49 for families, also annual. Keeping a Pi powered on all day costs you somewhere around $3 a month. Nobody is getting rich on that spread.
It still lands on a do-it verdict, for a different reason. A password vault is the one category where a vendor breach is an emergency instead of an annoyance, and the ongoing maintenance is about as light as self-hosting gets. Docker Compose, a reverse proxy, done.
I should say plainly that I am not running this one either, same disclosure as up top. But I did write the setup guide, including the parts where you should not do this: the Vaultwarden self-hosted password manager guide covers the backup routine and what actually happens when your server is down and you need a password.
File Storage: Nextcloud Is Probably Not Worth Your Time
This one’s going to disappoint some people.
Nextcloud is technically impressive. It replicates most of Google Drive’s functionality, has apps for every platform, and keeps your files on your hardware. The privacy argument is real.
The maintenance argument is also real, in the wrong direction. Nextcloud updates have a history of breaking things in ways that take real time to diagnose and fix. The software has improved but it’s still the most complex thing on this list to keep running reliably. For $10-12/month, Dropbox or Google Drive gives you 2TB of storage that just works and you never think about it.
If you have specific compliance requirements, or if you’re running a business where keeping documents off Google’s servers is non-negotiable, Nextcloud makes sense. For most people doing homelab stuff for the first time, I’d say start with Immich for photos specifically (I go deeper on the tradeoffs in my Nextcloud vs Immich vs Seafile comparison). Nextcloud is Immich plus file sync plus calendar plus contacts plus a task manager and a bunch of other stuff, and that complexity costs you.
For what it’s worth, Immich handles the photo use case better than Nextcloud does anyway. Focus there first.
Self-Hosted Email: Just Don’t
No.
I want to say more about this but the answer is just no. Running your own email server means managing deliverability. It means SPF records, DKIM signing, DMARC policy, PTR records, IP reputation. It means getting flagged as spam by Gmail and spending hours figuring out why. It means being on a blocklist you didn’t know existed and getting removed from it.
Even the people who’ve been running homelabs for 10 years outsource email. This is the universal consensus, and I’m not going to pretend otherwise.
Fastmail costs $5/month. ProtonMail costs $4/month and gives you real privacy without the operational nightmare. Pay for one of them. Move on. Self-hosted email is the one category where the effort-to-benefit ratio is so bad that I can say with confidence it’s not worth it for essentially anyone reading this.
So Should You Actually Set Any of This Up?
Here’s how I’d think about it.
Self-hosting is a good choice when: the service handles personal data you’d rather not hand over to a big company, the managed alternative costs real money that accumulates over time, and the setup effort is something you’re willing to invest once for long-term payoff.
Self-hosting is a bad choice when: reliability matters above all, you don’t have the time to debug something when it breaks at 11pm, or you’re trying to replace a service that works fine for a nominal monthly fee.
The hybrid approach is the right answer for most people. Self-host the things where the privacy and cost arguments are strong (photos, automation, smart home, local AI if the hardware fits). Leave the stuff that’s high-friction for low-gain on managed services (email above all, and probably general file storage).
If I’m being honest, the biggest mistake I see people make is trying to do everything at once. Pick one service. Get it running. Live with it for a month. Then add the next thing. The community around all of this is actually helpful, Docker Compose has made the tooling much better than it was three or four years ago, and the barrier to getting started has never been lower. Start with Immich or n8n if you’re going to start anywhere. Both have strong upside and manageable setup.
One more entry point worth naming, because it keeps showing up on other people’s priority lists: DNS filtering. Pi-hole and AdGuard Home sit on your network and block ad and tracker domains for every device in the house, phones and smart TVs included, and either one is an evening of work. Hurrikane’s 2026 writeup ranks it right next to password management as a first move, and I think that’s fair, mostly because the payoff is visible on your own phone the same night instead of being theoretical. My Pi-hole home server setup guide has the Proxmox and Docker versions. It stayed out of the table above for a boring reason: there is no managed alternative to price it against. Nobody sells you a household ad blocker for $6 a month.
The beginner home server guide is where to start if you need the hardware foundation first. Go there, get a machine running, and then come back to this list.
Sources
- Self-Hosting in 2026: What Is Actually Worth Running Yourself (DEV Community)
- Self-hosting as silver bullet: Myths and trade-offs (Zapier Blog)
- Immich vs Google Photos: Is Self-Hosting Worth It? (Serverman)
- n8n vs Zapier 2026: 8K Apps vs 90% Cost Gap (Tech Insider)
- Self-Hosting vs Cloud Services: A Cost and Privacy Analysis (dasroot.net)
- Local AI in 2026: Ollama Benchmarks, $0 Inference (DEV Community)
- 4 things that help me decide if a service is not worth self-hosting (XDA Developers)
- n8n Pricing 2026: Free Self-Hosted + Cloud + AI Agent Costs (Pxlpeak)
- Self-Hosting Tools: Still Worth Trying In 2026? (Tedium)
- The Self-Hosting Sweet Spot in 2026 (Code Capsules)
- Why Self-Hosting Matters More Than Ever in 2026 (Hurrikane)
- Bitwarden pricing: Premium and Families plans (Bitwarden)
- 1Password personal and family plan pricing (1Password)
- qwen3.5 model library page, including the 4B tag download size (Ollama)
What Are You Actually Running?
I’m curious where everyone is on this. Are you running a full homelab, or picking one or two services to try? Did you set up Immich and love it? Did you try Nextcloud and hate your life for a week? Drop a comment below, I read them all.
And if you found this useful, share it with whoever in your life keeps saying they “should probably set up their own server someday.” Now they have a roadmap for which parts are actually worth the weekend.
Pingback: How to Run AI Locally With Ollama (Free Setup Guide)