September 2026 TWN Systems
Immich as a company photo drive: the library becomes a business system
A private photo library can reduce cloud dependence. A company still needs roles, retention, backups, sharing rules, and someone who owns recovery.
Immich can be a useful home for company photos and videos when a team wants more control over storage and access. The decision is bigger than replacing a shared folder. Photos can contain client information, staff information, locations, and commercial records. Treat the library as a system with owners and a recovery plan.
Define the work first
Ask what the team needs to do with the files. Upload from phones? Share an album with a client? Find a person or project? Keep an original? Remove a file after a retention period? Export the library when a project ends? Each answer changes access, storage, and support needs.
- Roles for upload, search, share, delete, and administration
- Client or contractor access and how links are revoked
- Mobile upload, remote access, and device replacement
- Retention, consent, location data, and personal information
- Export, restore, and support when sync stops
The database and the files are both important
Immich uses a database for paths, metadata, and user information. The photos and videos live in storage. A database-only copy cannot restore the library. Back up both parts and test a restore before the team depends on the system.
Privacy comes with administration
A self-hosted library can keep files under your organisation's control and reduce dependence on a consumer platform. It also puts admin accounts, remote access, backups, devices, and sharing links in your responsibility. A private server with a weak admin account is not a private operating model.
Pilot one real project
Choose one project with mixed uploads and several users. Test upload, search, sharing, removal, export, database backup, file backup, and restore. Watch storage growth for a few weeks. Only then decide whether the system is ready for the whole company.