The biggest risks in Immich’s challenge to Google Photos and Apple iCloud

Immich hit a stable v2.0 release in October 2025, removing the long-standing warning that it was not ready for irreplaceable photos. By early 2026, the project had gathered over 87,000 GitHub stars, making it one of the fastest-growing self-hosted applications in history. It replicates the core utility of Google Photos with automatic background phone backup, AI-powered natural language search, and offline face recognition. The platform runs on four Docker containers: an API server, a machine learning engine, a PostgreSQL database with vector support, and a Redis cache for job queues. This architecture allows users to keep their most personal data on hardware they control, avoiding the perpetual monthly fees and policy shifts of major cloud providers.

The operational burden of ownership

The primary risk is that self-hosting transfers the responsibility for data redundancy entirely to the user. Immich developers explicitly state that the application must never be the only copy of your photos, a shift from the silent redundancy provided by commercial clouds. Users must maintain two distinct backup streams: the raw media files stored in the UPLOAD_LOCATION directory and the PostgreSQL database containing metadata, albums, and face assignments. Losing the database means losing the organizational structure of the library, even if the image files remain intact. A typical family library of 100,000 photos and 5,000 videos requires roughly 500 GB to 1.5 TB of storage, necessitating hardware like a NAS or mini PC with expandable drive bays. You should follow the 3-2-1 rule, keeping three copies on two different media types with one offsite copy, using tools like restic or rclone for automated offsite synchronization.

Hardware requirements are non-negotiable for the full experience. The official minimum is 6 GB of RAM when machine learning features are enabled, though 8 GB provides a comfortable margin for large libraries. On devices with only 4 GB, such as a Raspberry Pi, users must opt for lighter models or offload processing, which degrades performance significantly. The system also demands careful configuration of the .env file, including setting a custom database password and defining the timezone. For Windows users running Docker Desktop, specific adjustments are needed to avoid file permission issues, such as using named volumes for PostgreSQL data instead of bind mounts. These technical hurdles create a high entry barrier compared to the zero-setup nature of iCloud or Google Photos, where the provider handles all infrastructure maintenance.

Security gaps and feature limitations

While privacy is the main draw, the security model relies heavily on external tools rather than built-in enterprise-grade guardrails. Government cloud standards, such as those used by the B.C. government, require strict landing zones with pre-configured security tools like AWS Security Hub or Microsoft Defender for Cloud to monitor threats and manage cryptographic keys. Immich does not provide this level of integrated threat detection or compliance automation out of the box. Users must manually configure remote access via Tailscale or Cloudflare Tunnel to expose the service securely without opening router ports. Even then, Cloudflare’s free tier caps uploads at 100 MB per request, which can hinder the transfer of large video files through the tunnel.

Feature parity with giants like Google Photos is impressive but incomplete. Recent updates introduced shared people management, allowing users to share facial recognition clusters within a cluster group, and birthday memories that automatically generate slideshows based on dates of birth. However, the "Manage access" modal for sharing people is currently unavailable on mobile devices, limiting the convenience of family curation. Additionally, while Immich supports raw formats and LivePhoto playback, it lacks native album creation based on folder structure for external libraries. Users often need third-party scripts like immich-folder-album-creator to automate this process, adding another layer of maintenance complexity. The question remains whether the time spent managing these components justifies the privacy gain for average consumers who value convenience over control.