Your Family Photos Are Training Someone’s AI — Take Them Back With Immich on Hostinger in One Afternoon

Reading Time: 10 minutes

Key Takeaway

• 📸 Your family photos are training someone’s AI. Google eliminated the free photo tier in 2025 and retains rights to analyze uploaded photos for model training — deletion does not guarantee removal from the model data.
• 🏠 Immich on Hostinger gives the vault back to you. Auto-backup from every phone in the household, facial recognition and “dog on the beach” search that run on your own server, zero subscription — one Docker Compose file on a KVM 2 VPS.
• 🧮 The math is one afternoon versus $120 a year. A Hostinger KVM 2 (2 vCPU, 8GB RAM) runs Immich comfortably at roughly $7–9 introductory per month — against Google One’s $9.99/month for just 2TB with no privacy guarantees.
• 🛠️ Version 3.x made it family-proof. The July 2026 releases added visual automation workflows, mobile photo editing, integrity checks that prove your migration worked, and a patched album-sharing flaw (CVE-2026-59258).
• 🚀 Deploy in six steps: create the VPS, install Docker, paste the complete compose file, create the admin, connect the phones, and set the upgrade ritual — this guide hands over every file and command.

Immich on Hostinger is the exit ramp for a decision every Filipino family has already made badly: where the family photo library lives. Google ended free uploads over 15GB in 2025, pushed households onto paid plans, and kept the right to train models on what you upload — while Immich, the self-hosted photo platform funded by nonprofit FUTO and past 102,000 GitHub stars — the engine behind Immich on Hostinger deployments worldwide, shipped version 3.0 in July 2026 with the missing pieces families actually felt: reliable Android background backup, editing on the phone, and an integrity checker that tells you the archive is whole. This guide deploys Immich on Hostinger — a KVM VPS from an empty server to a working family photo vault — every phone in the household auto-backing up, faces and places searchable in plain language, and no monthly bill to any cloud. Total hands-on time: one afternoon on Immich on Hostinger. Total cost after that: the VPS, a backup routine, and nothing else.

Why Families Are Leaving Google Photos in 2026

Three facts changed the household calculus. First, the free tier is gone: uploads beyond 15GB shared across Gmail and Drive now require a Google One subscription — $2.99/month for 200GB, $9.99 for 2TB — and a decade-old “unlimited” promise is remembered only by the people who never got it. Second, the AI-training clause: Google retains rights to analyze uploaded photos for model training, and deleting a photo does not guarantee its data leaves the model — a red line for families who treat their library as a private archive. Third, the alternatives matured: Immich crossed from beta to version 3.x in 2026 with nonprofit FUTO funding, grew past 100,000 GitHub stars at the fastest rate of any self-hosted photo project, and — crucially for non-technical households — the mobile apps became the part that just works, with background backup that finally survives aggressive Android battery optimization — the official Immich Docker Compose documentation is the canonical reference alongside this guide. When a private alternative matches the convenience and removes the subscription, the switching decision stops being about ideology and becomes arithmetic — and Immich on Hostinger is where that arithmetic lands. Our Immich photo-backup analysis covers the why-leave-Google case in depth; this guide is the how.

WorldNgayon Analysis: The subscription saved is the visible number; the privacy recovered is the durable one. A household that moves its library to Immich on Hostinger pays roughly the same monthly amount but keeps three things Google cannot offer at any tier: the files never train a model, the storage ceiling is whatever disk you own, and the delete button means delete.

Bottom Line: Google Photos is a rental with a landlord who inspects the albums — Immich on Hostinger is ownership with a one-afternoon install.

What Immich Does Better Than Google Photos — and Where It Doesn’t

The honest ledger: Immich wins on cost structure, ownership, and local AI; Google keeps the edge on generative editing, natural-language search depth, and friction-free sharing with relatives who already live inside Google accounts. For the family photo vault use case — backup, organization, faces, recall — the 3.x feature set covers the daily jobs, and this guide’s final section closes the remaining gaps with two habits rather than workarounds.

What You Need Before Starting

Three things. A Hostinger KVM 2 VPS — the standard host for Immich on Hostinger setups (2 vCPU cores, 8GB RAM — the official Immich floor is 6GB and the comfortable recommendation is 8GB, especially during large first imports; KVM 2 introductory pricing runs roughly $7–9/month — the anchor cost of Immich on Hostinger). A domain you control (optional but recommended for easy access — a free DuckDNS subdomain also works). And about 90 minutes. The storage math scales with the family: a household with three phones and a 180GB library needs a 250GB VPS disk or larger — plan for two years of growth, not the current size. Start from the Hostinger plan you already use for your websites if it is a KVM plan; a fresh KVM 2 instance keeps the photo stack isolated from anything else you host.

Bottom Line: KVM 2 is the sweet spot — 8GB RAM covers the machine-learning container’s import spike, and the price stays below any 2TB cloud tier.

Step 1 — Create the Immich on Hostinger VPS

In hPanel: VPS → Create New Server → KVM 2. Choose a datacenter physically near the family (Singapore for the Philippines), Ubuntu 24.04 as the OS with Docker preinstalled, or bare Ubuntu 24.04 and install Docker yourself in Step 2. Set a root password from the password manager, not your head. When the instance finishes provisioning (2–3 minutes), copy its public IP, then in the Hostinger DNS (or your domain’s registrar) point an A record — photos.yourdomain.com — at that IP. Propagation takes minutes to hours; the install continues while DNS settles.

Step 2 — Install Docker and Prepare the Directory

SSH in as root and run the official installer, then create the Immich directory tree:

curl -fsSL https://get.docker.com | sh
mkdir -p /opt/immich /opt/immich/uploads /opt/immich/database
cd /opt/immich

Immich runs as a four-service Docker stack (server, machine learning, PostgreSQL with the VectorChord vector extension, and Valkey for caching — Valkey replaced Redis in the 2026 releases). You do not clone the whole repository; the two files in the next step are the entire deployment.

Step 3 — The Two Files That Deploy Immich

Create /opt/immich/.env — change both secrets to long random values (a password manager generator produces them):

DB_PASSWORD=CHANGE-ME-to-a-long-random-string
DB_USERNAME=immich
DB_DATABASE_NAME=immich
UPLOAD_LOCATION=/opt/immich/uploads
IMMICH_VERSION=release
TYPESENCE_ENABLED=false

Create /opt/immich/compose.yaml:

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    volumes:
      - ${UPLOAD_LOCATION}:/data
    ports:
      - "2283:2283"
    depends_on:
      - immich-database
      - immich-valkey
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - /opt/immich/model-cache:/cache
    restart: always

  immich-valkey:
    container_name: immich_valkey
    image: valkey/valkey:8
    restart: always

  immich-database:
    container_name: immich_database
    image: ghcr.io/immich-app/postgres:14-vectorchord
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
    volumes:
      - /opt/immich/database:/var/lib/postgresql/data
    restart: always

Two details this compose file gets right, where most guides fail. The database image is the project’s own postgres:14-vectorchord build — version 3.0 dropped the older pgvecto.rs extension entirely, so any guide still pointing at a generic postgres image produces an instance that cannot run smart search after the 3.x upgrade. And every service pins restart: always, which is what makes the vault survive a host reboot without you touching it.

WorldNgayon Analysis: The compose file is the whole product — four containers, two volumes, one port. Guides that complicate it are adding ceremony, not value; the only genuinely load-bearing choices are the VectorChord database image and the persistent volumes for uploads and the database.

Bottom Line: Two files and one command later, the server side is done — the remaining work is connecting humans to it.

Step 4 — First Run and the Admin Account

Start the stack and create the first user:

docker compose up -d
docker compose logs -f immich-server   # wait for "Immich Server is listening"

Open http://YOUR-VPS-IP:2283 in a browser, create the admin account (this is the parents’ account), and stop there — every other family member gets an ordinary account from inside Settings, so the admin stays with the person who runs the server. In Administration → Settings, confirm the Machine Learning toggle is on (it powers faces and CLIP search) and set Storage Template off unless you have a folder convention you already love — the default is fine and simpler to migrate away from later.

Step 5 — Connect Every Phone in the Family

Install the Immich app (iOS and Android), point it at http://photos.yourdomain.com:2283 or the raw IP, sign in, then set three things: Backup → Select Albums (Camera Roll, WhatsApp Images if the family archives chats there), Background backup on, and — after the first full upload completes — Free Up Space to clear already-backed-up originals off the phone. The worked example, with the numbers a real household faces: Maria in Riyadh shares the server with her mother in Batangas and two siblings in Cebu; the four phones hold 180GB combined. On a KVM 2 with a 250GB disk, the first import runs about an hour per 60GB on the household’s upload speed, the machine-learning container processes faces at roughly 2,000 photos per minute once the model cache warms, and after the first weekend every phone’s camera roll is searchable by face, place, and phrase — with Maria’s monthly cost at the price of one Google One 2TB seat, covering four users instead of one.

For access from outside the household without exposing a raw port, two clean paths: put the VPS hostname behind Cloudflare Tunnel (free, gives real HTTPS), or run Tailscale on the phones and reach Immich over the private network — the zero-exposure option for families who only need access from their own devices — the same private-network pattern as our Nextcloud on Hostinger cloud.

Bottom Line: The phones are the clients, the VPS is the vault, and the family never thinks about either again after setup week.

Step 6 — the Immich on Hostinger Upgrade Ritual

Immich upgrades inside a major version are genuinely zero-step — docker compose pull && docker compose up -d — but the ritual around that command is what separates households that keep their library forever from the horror stories in the self-hosting forums — the same discipline the Vaultwarden on Hostinger deployment follows. Run it monthly, in this order:

cd /opt/immich
docker compose down
tar czf immich-db-$(date +%F).tgz database/
docker compose pull
docker compose up -d
docker compose logs -f immich-machine-learning   # watch the model cache rebuild

The database backup line is the insurance: album structure, faces, and user settings live in PostgreSQL, and a tested backup turns any upgrade accident into a five-minute restore. Three 2026-specific cautions from the release notes: never jump from 1.x straight to 3.x — the VectorChord migration must finish on 2.x first; the 3.0.3 patch fixed a real album-sharing privilege escalation (CVE-2026-59258, CVSS 8.3), which is the argument for running the ritual monthly instead of yearly; and the machine-learning container’s first start after an upgrade rebuilds its cache — the spike is normal on 8GB, and it settles.

Bottom Line: One monthly command plus one database backup is the entire maintenance contract — ten minutes a month to own the family archive outright.

What Immich Still Cannot Do — and the Two Habits That Cover It

The gaps are known and specific. There is no client-side encryption — files rest in plaintext on the VPS, so the cover is encrypting the volume at the provider level or pairing with an encrypted backup target. There is no collaborative editing — retouching happens elsewhere, Immich is the vault, not the darkroom. Sharing with non-technical relatives remains the softest edge: a link opens fine, but a relative who expects Google’s share sheet needs one app install and one login, once. And Immich is monolithic — one server, no built-in replication. The two habits that close the real risk: the monthly database backup from Step 6, and an off-site copy — the simplest version is a second cheap storage bucket or even a synced external drive in another household member’s home — the redundancy mindset from the Uptime Kuma monitoring stack., updated after every monthly ritual. Photos survive the decade when the vault has a twin.

WorldNgayon Analysis: Every remaining Immich gap is a backup problem or a workflow preference — none is a data-ownership problem. The household that runs the two habits holds an archive strictly more durable than any single cloud account, at a total cost that stops growing when the disk does.

Bottom Line: Own the vault, back it up twice, and the gaps stop mattering — that is the entire difference between self-hosting as a hobby and self-hosting as infrastructure.

The OFW Family Playbook

One paragraph, five moves: one — deploy Immich on Hostinger KVM 2 near the family, not near you; latency is a daily experience for everyone but you. two — one admin (you), ordinary accounts for everyone else; admin stays with the person who runs the upgrades. three — select albums deliberately on each phone, not everything; the vault stays searchable when it is not a landfill. four — after the first full backup, run Free Up Space on the phones with small storage — the 64GB phone that keeps hitting full is the household’s most common photo-loss story, and it ends here. five — calendar the monthly ritual and the off-site sync on the same day, and log the date on the wall file where the family keeps its important papers. The first month after the switch, expect one question from a relative — “why is my gallery asking for a server address” — and never another one after that.

Bottom Line: The playbook costs one afternoon and ten minutes a month; the alternative costs $120 a year per household and a privacy clause nobody reads.

Frequently Asked Questions

Is Immich really free?

Yes — AGPL-3.0 open source with no feature paywall, funded by the nonprofit FUTO. You pay only for the hardware or VPS it runs on; a Hostinger KVM 2 runs Immich on Hostinger comfortably at roughly $7–9 introductory per month, and there is no per-user or per-storage fee ever.

How much RAM does Immich need?

The official floor is 6GB RAM and 2 CPU cores; 8GB and 4 cores is the comfortable recommendation, mainly for the first large import when the machine-learning container spikes. A Hostinger KVM 2 (2 vCPU, 8GB RAM) is the practical Immich on Hostinger minimum for a family library, and KVM 4 removes any ceiling.

Can Immich replace Google Photos completely?

For backup, timeline, faces, and search — yes, and the search runs entirely offline. What you give up is Google’s generative editing and its friction-free sharing with non-technical relatives; what you gain is no storage cap, no training clause, and a delete button that means delete.

Is it safe to expose Immich to the internet?

The 3.0.3 release patched an album-sharing privilege escalation (CVE-2026-59258), which is why running current versions matters. The safest pattern needs no exposure at all: Tailscale for household-only access, or Cloudflare Tunnel in front of the server if relatives need browser links.

How do I migrate an existing Google Photos library?

Use Google Takeout to export the archive, then upload through Immich’s web interface or the CLI in batches; version 3.x’s integrity-check job then scans for untracked files, missing assets, and checksum mismatches — run it after the import and it tells you the migration actually worked, file by file.

Financial Disclaimer

Financial Disclaimer: This article may reference hosting plans and subscription prices for comparison. Prices change and are quoted from providers’ published rates as of September 27, 2026. WorldNgayon.com is not a financial adviser; verify current pricing and terms with the provider before purchasing, and do your own research before any financial commitment.