2026.09.12
Lychee: A Self-Hosted Home for Your Photo Library
Lychee is an open-source photo-management system for uploading, organizing, and sharing images on your own server. This overview covers deployment options, audience, and adoption risks.
What it is
Lychee is an open-source photo-management system that runs on a server or web space. Its documented purpose is to upload, manage, and share photos. That makes it a candidate for individuals, photographers, families, and small teams that want their photo library on infrastructure they control, rather than relying exclusively on a hosted gallery service.
The repository metadata identifies the project as MIT-licensed and not archived. That does not by itself confirm the licensing terms of every bundled or external component, so organizations should review dependencies and deployment images before production use.
Features and deployment options
The README describes photo uploading, management, and sharing. It lists Docker as the recommended installation path and provides a minimal Docker Compose setup with a separate worker container for background jobs. Container images are available through GitHub Container Registry and Docker Hub. The README distinguishes latest, described as the latest stable release, from edge, described as a development build.
Those labels should not replace release management. For a production installation, pinning an approved release, testing upgrades, and keeping a rollback plan are sensible operational steps. The provided sources do not establish CPU, memory, storage, database-size, or performance requirements, so no minimum hardware recommendation can be made here.
A source installation requires PHP 8.4 or newer, Composer, and npm according to the README. The supplied material does not confirm the full database-support matrix, required PHP extensions, reverse-proxy configuration, permission model, or queue requirements. These should be checked in the official documentation before choosing a deployment architecture.
Limits and adoption considerations
Self-hosting moves responsibility to the operator. Photo files, database contents, logs, application keys, and configuration need appropriate protection, backups, and recovery testing. The provided sources do not support a blanket security or compliance claim. Teams planning public sharing should define authentication, authorization, HTTPS, domain, email, storage, and backup procedures before exposing the service.
Upgrades deserve particular attention. The README warns that version 7.0 introduced significant Docker-image changes. A migration from an older installation should therefore be tested in a disposable or staging environment, with the database and upload directories backed up and a rollback path prepared.
The supplied official release notes identify v7.8.3 as published on September 1, 2026. They list changes including preventing edits to pictures that have not yet been validated and fixing replayed uploads within the same chunk. These are release-note entries, not independent evidence of overall security or reliability.
Who should consider it
Lychee is worth evaluating if you want a server-hosted photo library and are prepared to maintain containers, databases, storage, backups, and updates. It is a weaker fit for users who do not want operational responsibility, need a hosting provider to own recovery obligations, or require capabilities not confirmed by the supplied sources. A small pilot and a review of the official documentation should precede a larger migration.
Sources
Sources checked: 2026-09-12