The self-hosting community rarely talks about the cost that doesn't appear on a bill. Every NAS and home server you run has a maintenance burden: updates that need testing, services that need monitoring, disks that need replacing, and configurations that need updating when software changes break your setup. This cost is real but invisible until it accumulates into what people in the self-hosting community recognise as 'self-hosting fatigue'. The point where maintaining the infrastructure feels like more work than the services are worth. This article does not argue against self-hosting. It argues for self-hosting selectively, which means being honest about which categories are worth the overhead and which are better left to SaaS providers.
In short: Self-hosting makes clear sense for: file storage and sync, password management, notes, photo management, ad blocking (Pi-hole), and home automation. It is borderline for: email, video conferencing, collaborative document editing, and analytics. It rarely makes sense for: calendar/contacts sync (the protocol complexity is high for marginal privacy benefit), business email deliverability, or services where reliability guarantees matter and downtime has real consequences. The rule of thumb: self-host things where a few hours of downtime is inconvenient, not catastrophic, and where the SaaS alternative charges subscription fees you would actually notice.
What Self-Hosting Actually Costs You
Visible costs include NAS hardware, drives, electricity, and connectivity; totals vary substantially with the hardware class, storage capacity, system power draw, usage, and electricity tariff. These compare favourably against cloud subscriptions for storage and software.
The invisible costs are harder to quantify but worth naming:
- Attention and decision overhead: Every service you run requires monitoring, even if that monitoring is just occasionally checking it still works. As the stack grows, the number of things that can fail grows with it. A stack of 15 services means 15 possible failure points, each with its own update cycle, dependency chain, and configuration surface.
- Update risk: Every update is a potential regression. Testing updates before applying them requires time; not testing them is a silent risk. Self-hosters who fall behind on updates create security exposure; those who stay current accept periodic breakage risk.
- Knowledge debt: Configurations built without documentation are a tax on your future self. The Nginx reverse proxy config you spent a weekend tuning in 2023 will need debugging in 2026 when it stops working, and you will have forgotten why it was configured that way.
- Single point of failure: When the NAS has a drive failure, the power supply dies, or DSM updates badly, everything goes down at once. A SaaS outage still affects user access; any SLA commitment and remedy depend on the provider, plan, and contract.
None of these are arguments against self-hosting. They are arguments for being deliberate about what you self-host and realistic about the ongoing cost.
Categories Where Self-Hosting Clearly Wins
Some categories are good candidates for self-hosting because the SaaS alternative is expensive, the self-hosted option is mature and stable, and downtime is an inconvenience rather than a crisis:
- File storage and sync: Nextcloud, Synology Drive, and Seafile replace Google Drive or Dropbox storage (which cost $15-30 AUD/month for 2TB). The self-hosted option is better privacy, comparable functionality, and pays back hardware cost quickly. Synology Drive in particular requires very little maintenance for Synology NAS owners.
- Password management: Vaultwarden (Bitwarden-compatible) is one of the best self-hosting decisions available. 1Password costs $5 AUD/month per user. Vaultwarden can run on low-resource hardware, but resource requirements and power draw depend on the host system, database size, and workload. Downtime means temporarily using cached passwords. Not a crisis.
- Photo management: Immich has become a strong Google Photos replacement with face recognition, album sharing, and a polished mobile app for uploads. Google Photos at 2TB costs $15 AUD/month. The self-hosted option handles large libraries well on a NAS with sufficient RAM.
- Ad blocking: Pi-hole or AdGuard Home run on almost any hardware. The SaaS alternative does not exist in a meaningful form. Network-level ad blocking is also available through hosted filtering DNS services such as AdGuard DNS; Pi-hole and AdGuard Home are self-hosted options.
- Home automation: Home Assistant is the definitive home automation platform and has no credible commercial equivalent. Cloud-based home automation products are fragmented, have spotty longevity, and often sunset without warning. Self-hosting HA is nearly always the right choice for serious home automation.
- Note sync: Joplin, Obsidian, and Standard Notes with self-hosted sync replace Evernote (pricing varies by currency and billing channel; the Australian App Store currently lists Evernote Personal at A$214.99/year) or Notion ($10-20 USD/month) with privacy-first alternatives that work well for personal use.
Categories Where It Gets Complicated
Some categories are technically self-hostable but come with friction that makes the comparison less clear-cut:
- Email: Self-hosted email (Mailcow, Mail-in-a-Box, Mailu) is technically achievable but involves managing IP reputation, deliverability, spam filtering, and staying off blacklists. Most residential IP addresses are on dynamic IP ranges that are pre-blocked by major providers. A dedicated VPS helps but adds ongoing cost. For personal use where deliverability matters, Fastmail or Proton Mail is a better value proposition than self-hosted email for most people.
- Collaborative document editing: Nextcloud Office (Collabora Online) and OnlyOffice are functional alternatives to Google Docs but have notable performance and compatibility gaps. For occasional use, they are fine. For a household where someone regularly collaborates with external colleagues who use Google Docs or Microsoft 365, the format compatibility and real-time collaboration performance make SaaS the more practical choice.
- Analytics: Plausible, Umami, and Matomo self-hosted are good options for website analytics with privacy-by-default. Hosted-plan savings vary by provider and traffic volume: Umami offers a free hosted tier, while other hosted analytics plans may fall below or above this range. But they require a server with good uptime. If the analytics container is down when traffic spikes, you lose that data. Borderline: worth it if you already have a VPS or reliable NAS with good uptime.
- Video conferencing: Jitsi Meet is self-hostable but WebRTC performance is highly sensitive to network configuration, NAT traversal, and TURN server availability. Reliable self-hosted Jitsi requires correct DNS, NAT and media-port configuration plus adequate network capacity; dynamic IPs can work with dynamic DNS, and TURN provides fallback connectivity where direct connections fail. The convenience gap is large enough that most households should not bother.
Where SaaS Is Genuinely the Better Choice
Some categories are better left to SaaS, not because self-hosting is impossible but because the cost-benefit genuinely favours the commercial service:
- Calendar and contacts sync (CalDAV/CardDAV): The protocols work, but the maintenance overhead of running a CalDAV/CardDAV server (Radicale, Baikal, Nextcloud) for the privacy benefit over iCloud, Google Calendar, or Fastmail is rarely worth it. These services cost $0-5/month and are deeply integrated with mobile operating systems. A calendar sync outage affects daily life immediately. Proton Mail with its calendar provides a reasonable privacy-first alternative without self-hosting if that is the concern.
- Transactional email delivery: If you run a small business or personal project that sends email (form submissions, notifications, invoices), self-hosted SMTP delivery is unreliable from residential or even standard VPS IPs. Postmark, SendGrid, or Resend have free tiers sufficient for most small-scale needs and provide managed sending infrastructure and authentication tooling, but you must still configure and verify domain-authentication DNS records such as DKIM and DMARC.
- Database backups for critical business data: Off-site backup of critical business data using a verified, compliant cloud provider gives you audit trail, geographic redundancy, and SLA guarantees that a home NAS setup cannot match. For business-critical data, compliance depends on the applicable obligations and implemented controls rather than cloud versus self-hosted storage alone. Use resilient, tested backups with appropriate access controls and off-site protection, and assess any cloud provider's contracts and security controls.
- DNS: Self-hosted recursive resolvers such as Unbound can make sense for privacy; NextDNS is a hosted DNS-over-HTTPS service with an optional local proxy client, not a self-hosted recursive resolver. Self-hosting your authoritative DNS for public domains does not. The reliability requirements are too high, and Cloudflare offers free authoritative DNS on its global network; relative reliability depends on the architecture and operation of the alternative deployment.
A Framework for Deciding What to Self-Host
When evaluating whether to self-host a new service, four questions cut through most of the noise:
| 1. What does the SaaS alternative cost? | If the SaaS is free or under $5/month, the cost case for self-hosting is weak. The hardware amortisation, electricity, and your time often exceed the savings. Self-host when the SaaS costs $10+/month per user or where the cost compounds across a family. |
|---|---|
| 2. What is the cost of downtime? | If a service being down for 4-8 hours causes a meaningful problem (missed emails, lost work, household conflict), self-hosting requires a reliability investment that may not be worthwhile. If downtime is a minor inconvenience, self-hosting is fine. |
| 3. What is the maintenance surface? | A container that runs for months without intervention (Vaultwarden, Pi-hole, Uptime Kuma) has low maintenance surface. A container that needs regular updates, has complex dependencies, or generates frequent errors has high maintenance surface. Be honest about how much ongoing attention you will actually provide. |
| 4. Is the privacy benefit real? | Not all data is worth protecting from your cloud provider. Photos stored in iCloud have different privacy implications than your password database or private notes. Prioritise self-hosting for your most sensitive data categories rather than everything. |
Managing Fatigue: The Sustainable Self-Hosting Stack
Self-hosting fatigue typically comes not from any single service but from stack sprawl. Adding services faster than the maintenance overhead can be absorbed. A sustainable self-hosted stack has a few characteristics:
- Everything is in Docker Compose: Services deployed as Docker Compose stacks with
docker compose pull && docker compose up -dcan be updated in minutes. Services deployed manually, via package managers, or with custom init scripts require custom update procedures that you will forget by the time the next update is needed. - One reverse proxy handles all TLS: Traefik or Nginx Proxy Manager terminates HTTPS for all services through one configuration. Maintaining separate TLS certificates per service does not scale.
- A limit on the number of services: Set a practical limit on core services based on actual use and the maintenance capacity available. Each additional service beyond that adds diminishing returns. The ten services you actually use every day deliver more value than twenty services that seemed interesting when you deployed them.
- Monitoring that alerts you: Uptime Kuma or Healthchecks.io watching your services means you find out about failures before the family does. Without monitoring, outages become support incidents rather than infrastructure events.
- Documented configuration: A brief README or comments in your Docker Compose files explaining non-obvious configuration choices costs 10 minutes when you set something up and saves hours when you need to debug it six months later.
Related reading: our NAS buyer's guide.
Free tools: Cloud vs NAS Cost Calculator and NAS Sizing Wizard. No signup required.
Related reading: our NAS explainer.
See also: our complete Synology NAS Australia guide.
Is it worth self-hosting if I am not particularly technical?
For some services, yes. Synology Drive, Vaultwarden, and Pi-hole are all achievable for users with basic NAS management skills and willingness to follow a setup guide. Nextcloud AIO is harder but manageable. Complex stacks involving manual server configuration, custom databases, and inter-service dependencies are genuinely difficult without technical background. The honest answer: start with one or two low-maintenance services (Vaultwarden, a NAS with Synology Drive) and expand only when you are comfortable with the maintenance cycle of what you already have running.
How do I know when I have too many self-hosted services?
Practical indicators: you have containers running that you have not accessed in over six months; you avoid applying updates because you are not sure what will break; outages get discovered by family members before you notice; you do not remember why a configuration option is set the way it is. If more than one of these is true, reducing the number of running services. Rather than adding more. Will improve your overall reliability and reduce ongoing stress.
What should I do if my NAS is down and my family needs access to files?
This is the argument for maintaining a thin cloud fallback for truly critical data. Keeping your most critical documents (tax records, insurance policies, medical information) in both self-hosted storage and a free cloud tier (iCloud free 5GB, Google One free 15GB) provides a fallback that survives NAS outages. This is not a defeat for self-hosting. It is the same redundancy principle as having both local and cloud backup. Self-hosting your primary storage while keeping a small amount of critical data in cloud as a resilience layer is a practical, not ideological, decision.
What is the best way to update Docker containers reliably?
Watchtower is a popular tool that automatically updates Docker containers, but auto-updating production services without testing is risky. Updates that break containers can take services down silently. A more reliable approach: use Watchtower in monitor-only mode (it reports available updates without applying them), then review and apply updates manually with docker compose pull && docker compose up -d on a weekend when you can notice and fix any issues. For services with persistent data, always ensure backups are current before updating.
If I stop self-hosting, how do I migrate my data out?
Data portability varies by service. Nextcloud and Synology Drive files are stored as regular files on the NAS. Direct export. Vaultwarden can be used with Bitwarden-format exports, but destination compatibility is conditional: 1Password currently requires a password-protected encrypted JSON, does not support Argon2id for this import, and does not import passkeys or shared collections. Immich can export original photos in their original format. Home Assistant configuration is not limited to YAML; most integrations use persistently stored UI configuration. Home Assistant's supported migration method is to restore a full backup on the target device, with additional steps sometimes required for radios, storage, and device connectivity. The well-maintained self-hosted services generally have good data export. The services to check carefully before committing are those with proprietary database formats. Always test an export before you are in a situation where you need it.
If you are evaluating which self-hosted services to run on a NAS, the comparison between Nextcloud, Seafile, and Synology Drive for file sync is a good starting point for the most commonly used service category.