Stacks / Sync
Immich
Photos you host. Immich is AGPL-3.0 — Google Photos without the library in someone else's building.
The problem
Google Photos is bundled into a Google account (and then Workspace or storage packs). You wanted backup, mobile upload, and a timeline you can export. Immich is AGPL-3.0: mobile apps, ML tagging, a timeline. This is a photo library — not Drive (/replace/google-drive) and not a Nextcloud files suite.
Replaces
Google Photos
Estimated SaaS saved
$1,200
per year, small team, before lock-in
Start on RailwayNextcloud if this is Drive/files, not a photo timeline
Placeholder: Immich (server + ML + Redis + Postgres) plus a large volume for originals. Machine-learning jobs want RAM; GPU is optional. No one-click template in this repo yet — Start on Railway. File suites stay on /stacks/nextcloud-files.
The stack
- Immich
AGPL-3.0 self-hosted photo and video backup
Cost table
| You stop paying | Typical / year | Self-host instead |
|---|---|---|
| Google Photos / Workspace storage (small family) | $1,200 | Immich + a volume |
Agent setup prompt
Replace Google Photos with Immich (https://immich.app). - Follow Immich's recommended compose: server, microservices, ML, Redis, Postgres, and a volume for the library. - Install the mobile app, upload one camera roll, confirm a timeline. Turn off public sharing until you want it. - Write AGENT_PROMPT.md. Take-out from Google if you still can; do not promise every Google Photos search trick.
Also as markdown: /stacks/immich-photos.md
FAQ
- Why not Nextcloud?
- Nextcloud is the Drive/OneDrive suite (/replace/google-drive). Immich is a photo timeline with mobile backup. Use Nextcloud if people dump folders; Immich if they expect a camera-roll app.
- Does this need a GPU?
- No. Machine-learning jobs (faces, CLIP) run on CPU and are slower. A GPU helps; it is not required to store and browse photos.