Immich started as a personal side project in 2022 and has grown into one of the fastest-growing self-hosted applications in recent memory, passing 90,000 GitHub stars by early 2026. For anyone uneasy about Google Photos or iCloud, the pitch is obvious: run your own photo server, on your own hardware, and no company ever touches your library.
That pitch is real, and for the right person, Immich genuinely delivers on it. But the privacy-focused corners of the internet that recommend self-hosting rarely spend equal time on what it actually takes to keep a self-hosted photo library safe — and the gap between “I escaped Big Tech” and “I lost a decade of family photos” is narrower than most setup guides admit.
What Immich Actually Is
Immich is open-source software you run yourself — on a home server, a NAS, or a cheap cloud VPS — that replicates much of what Google Photos or iCloud Photos does: automatic backup from your phone, albums, face recognition, a searchable timeline, and a clean mobile app for browsing your library. It’s free, actively developed, and genuinely impressive software for what it is.
The core promise is architectural: no company’s servers ever hold your photos. Whatever Immich does with face recognition or search happens on hardware you control. There’s no terms-of-service clause to worry about, no AI training opt-out to check, no company that could be acquired or sell your data, because there’s no company in the loop at all.
For people with the technical background to set it up and maintain it, that’s a meaningfully different privacy posture than any cloud provider, including privacy-focused ones — you’re not trusting a policy, you’re removing the third party entirely.
The Part Self-Hosting Guides Underplay
Search any self-hosting community and you’ll find consistently enthusiastic recommendations for Immich. What you’ll find less often, until you go looking specifically, is the recurring pattern on forums like Reddit’s r/immich: weekly posts from people in genuine panic because they appear to have lost their entire photo library.
You become your own IT department, including for failure modes you’ve never dealt with before. Hosting your own photo server means you’re responsible for everything a cloud provider normally handles invisibly: drive health monitoring, software updates, network configuration, backup verification. Immich is in active, fast-moving development, which is good for features and bug fixes, but it also means updates arrive frequently enough that “check logs and update containers” becomes a real, recurring maintenance task — not a one-time setup chore.
Consumer hard drives are not built for the job you’re asking them to do. A drive sitting in an external enclosure or a budget NAS, spinning continuously to hold your only copy of a decade of family photos, is operating outside the conditions consumer drives are rated for. Drives fail — not eventually in the abstract, but on a predictable enough timeline that “if” is the wrong word.
RAID is not a backup, and a lot of new self-hosters set up RAID and stop there. Redundant disks protect against a single drive failing mid-operation; they don’t protect against accidental deletion, a corrupted database, a ransomware infection, or a fire, flood, or theft affecting the physical location where all your drives happen to live. People who set up RAID and consider their backup strategy “done” are protected against exactly one failure mode out of several common ones.
The 3-2-1 Rule Nobody Skips Without Consequence
The backup strategy security professionals consistently recommend — for self-hosted setups specifically, not just photos in general — is the 3-2-1 rule: three copies of your data, on two different types of storage media, with at least one copy stored somewhere physically separate from the others.
Applied to a self-hosted photo library, that typically means: the live copy Immich serves from, a local backup on a separate drive, and an off-site copy — an encrypted cloud bucket, a drive at a relative’s house, anything that survives if something happens to the location where your main server lives.
The honest reality is that most people who self-host skip the third leg of that strategy. It’s the least convenient one — it requires either paying for off-site storage (which can feel like defeating the purpose of avoiding cloud subscriptions) or physically maintaining a drive somewhere else. Skipping it is understandable. It’s also exactly the gap that turns “my drive failed” from an inconvenience into a catastrophe.
Is Self-Hosting Worth It? It Depends What You’re Actually Solving For
If your primary concern is a company analyzing your photos for AI training, ad targeting, or any commercial purpose, self-hosting genuinely solves that problem completely — there’s no company in the architecture to do any of those things. That’s a real and significant advantage over any cloud provider, including ones with strong no-training policies, because it removes trust from the equation rather than asking you to rely on it.
If your primary concern is keeping your photos safe and accessible over the long term, self-hosting adds risk rather than removing it, unless you’re genuinely willing to maintain the discipline of monitoring drive health, applying updates, and keeping a real off-site backup running indefinitely — not just at setup, but for years, including the years where you’re busy, traveling, or simply not thinking about your home server.
Those are two different questions with two different right answers, and a lot of self-hosting recommendations conflate them — treating “no company touches your data” and “your data is safe” as the same claim, when they’re not.
A Realistic Middle Path
You don’t have to choose between full self-hosting and a major cloud provider’s AI-driven, ad-supported ecosystem. A workable approach for a lot of people looks like this:
Self-host for the features and the architecture, if you want them — face recognition, a familiar timeline interface, full control, no third party in the loop for your day-to-day library.
Pair it with a genuinely off-site backup that isn’t dependent on your own hardware staying healthy. This is the leg of the 3-2-1 strategy people skip, and it’s the one that actually prevents catastrophic loss. It doesn’t need to be a major cloud provider with an AI-training clause buried in its terms — a privacy-committed storage service that’s encrypted, doesn’t train AI on your content, and doesn’t depend on your home network staying online is a reasonable off-site leg specifically because it removes the “my server is the only copy” risk without reintroducing the trust problem you were trying to avoid in the first place.
Be honest about your own maintenance bandwidth. If checking on a self-hosted server every month sounds like a chore you’ll quietly stop doing after the first few months, that’s worth knowing before you build a workflow that depends on you doing it indefinitely. A self-hosted setup that gets neglected isn’t more private than a cloud service — it’s just privately at risk instead of commercially at risk.
The Cost Comparison Nobody Runs Honestly
Self-hosting is frequently pitched as the cheaper option once you’ve bought the hardware, and on the storage line item alone, that’s often true. But an honest total cost of ownership includes more than the price of a NAS.
Hardware has a finite lifespan and needs replacing. Drives fail on a statistically predictable timeline, not a never-needs-attention one, which means the up-front hardware cost isn’t a one-time expense — it recurs every few years, usually at a moment that doesn’t feel convenient.
Electricity for a server running continuously isn’t free, even if it’s easy to overlook because it’s bundled into a household bill rather than itemized as a separate “photo storage” line. A small home server running around the clock adds a real, ongoing cost that rarely factors into the “self-hosting is free” framing.
Your own time has value, even if you don’t bill yourself for it. Hours spent troubleshooting a failed update, restoring from backup after a drive failure, or researching a new vulnerability disclosure in software you’re running are real costs, even though no invoice arrives for them. For some people, that time is genuinely enjoyable — a hobby, not a chore. For others, it’s an ongoing tax on a decision that was sold as a one-time setup.
None of this means self-hosting is a bad deal. It means the comparison against a paid cloud subscription is more honest when it accounts for hardware replacement, power, and time, rather than just the sticker price of the original NAS purchase.
What This Isn’t an Argument Against
None of this is a case against Immich, or against self-hosting generally. The privacy upside is real, the software is genuinely good, and for technically inclined users with the discipline to maintain a proper backup strategy, a self-hosted photo library is one of the strongest privacy postures available — stronger, in the specific dimension of “no third party ever has access,” than anything a company can offer no matter how strict its policy commitments are.
The point is narrower: the enthusiasm in self-hosting communities tends to undersell the maintenance burden, because the people writing setup guides are usually the people who already have the skills and discipline to handle it. If you’re earlier in that journey, the honest version of the advice is “this is worth doing, and it requires more ongoing attention than the setup tutorials suggest” — not “set it up once and you’re done.”
If You Want the Off-Site Leg Without Adding Another Server
For the backup copy that needs to survive a hardware failure at home, daftei is built to be a simple, low-maintenance off-site option: encrypted with AES-256 at rest and TLS 1.3 in transit, with no AI training on your content, no ads, and no data sales. It’s available on iOS, Android, and the web, with 5 GB free and unlimited storage on Pro — enough to cover the photos and documents you genuinely can’t afford to lose, without becoming a second server you have to maintain.