The Image Depot: 25 Years of Photo Management
The Problem
Everyone’s photo library is a disaster. Ours certainly is. Twenty-five years of digital cameras, phone upgrades, cloud syncs, kids, friends sharing albums, a DSLR that dumps raw files into a folder called DCIM, and iCloud doing whatever iCloud decides to do. At some point we stopped being able to answer basic questions like “which kid’s birthday party was that?” and “are those even my kids?”
Our library currently lives on Zenfolio, which worked great - until the volume and chaos overwhelmed us. Photos arrive from too many directions: shared albums from friends, iCloud sync, local imports from the camera, screenshots, school photos emailed as PDFs for some reason. No single platform handles all of that well, and the organizational work we’ve done is locked inside whichever service we happened to use that year.
The Idea
The Image Depot is the system we want to build: self-hosted photo management focused on a single principle - the organizational work should belong to you, not to a platform.
Import from anywhere. Tag, curate, organize into collections. The metadata stays with the images in standard formats. If you move to a different system five years from now, you take everything with you - not just the pixels, but the context.
The Hard Problem
The real challenge in photo management isn’t storage or display - it’s the pipeline. Photos arrive from different sources in different formats with inconsistent metadata. Some have GPS coordinates. Some have EXIF dates that are wrong because the camera clock wasn’t set. Some are duplicates from three different backup strategies. Some are screenshots that shouldn’t be in the library at all.
A proper import pipeline normalizes all of this: deduplication, metadata extraction, date correction, format normalization. By the time a photo lands in the library, it’s clean. That upfront investment in data quality pays off every time you search.
Why Self-Hosted
Control and longevity. We’ve already been through cloud photo service shutdowns and terms-of-service changes that made us nervous. A self-hosted system on hardware we own means the only thing that can deprecate our photo library is us.
The trade-off is real: no AI-powered face recognition out of the box, no automatic “memories” features, no seamless phone sync. But those are features we can add on our own terms, with our own data, without a service agreement that changes annually.
Why Now (Almost)
Our hind brain has been chewing on this problem for a very long time. The difference now is that AI is finally at a place where we can implement some of our most ambitious ideas - smart tagging, natural-language search across decades of photos, automatic event grouping - without spending years learning every API and JS framework first. The technical barrier between “we know exactly what this should do” and “it actually does it” has collapsed.
The Throughline
This is one of the oldest projects in the portfolio - the problem statement hasn’t changed since we got our first digital camera. The constant is the conviction that photo organization is too personal and too long-lived to delegate to a platform.
Current Status
In the backlog, but actively designed. This is a project I want to do right - not rush. The architecture is thought through, the problem space is deeply understood, and AI has made the implementation timeline realistic. It’s next in line when I have the time to give it the attention it deserves.