Immich is useful to study because the thing it manages can be difficult to replace. People entrust photo software with original files and the information that makes those files usable. Its current FAQ describes an AGPL-licensed project supported through product-key purchases. A May 2024 announcement documented the core team joining FUTO to work on the project full-time. Those are observable arrangements; they do not reveal margins or predict whether another developer can reproduce the model.
Follow the data beyond the upload button
The official backup guide makes a crucial distinction: a database backup contains metadata, while original photos and videos need their own file backup. Recovery depends on keeping the relevant parts together. For an independent builder, that is a product-design question. What exactly survives a broken server, an accidental change, or the decision to leave your service?
An AI-assisted research archive has a similar shape. Original documents, annotations, permissions, and generated summaries may live in different stores. Regenerating a thumbnail or a summary is often possible. Reconstructing a lost original, a source reference, or a customer’s access decision can be much harder. Write a small inventory that distinguishes irreplaceable inputs from reproducible outputs.
Design a recovery demonstration
Use a disposable collection containing files you own and fictional account details. Create a manifest of the originals, their hashes, the metadata needed to find them, and the application version. Decide where a separate backup copy will live before making the application the only place that holds the collection.
- Back up the complete state using the selected project’s documented procedure. Record which files and databases the backup includes.
- Restore into a separate test environment with no connection to the original storage. Avoid destructive commands against the working instance.
- Open a known item, locate it through its metadata, and check that an authorized test account has the expected access.
- Record missing items, manual repair, elapsed recovery time, and any version constraint. A backup file existing is only the start of this check.
The checkpoint is a usable recovered collection with a traceable manifest. Do not replace the original service until the result has been inspected. If the procedure requires undocumented knowledge, turn that knowledge into the next improvement and repeat the isolated demonstration.
Explain what the purchase supports
Immich’s funding history offers a separate lesson: describe the relationship between payment and ongoing work accurately. A founder may be charging for software, a managed service, migration assistance, or a support commitment. These create different obligations. A license badge alone does not tell a customer who will answer a failed-restore request or maintain an integration.
When researching an offer, ask which responsibility the buyer wants to hand over and which they expect to retain. Keep the written answer with the pilot scope. Do not infer willingness to pay from downloads, enthusiastic comments, or the existence of a successful open-source project.
Set the failure boundary early
Stop accepting irreplaceable customer data if the recovery demonstration fails or the backup excludes an essential component. Continue with a limited pilot when ownership, recovery, and support responsibilities are understandable. This is a proposed research method informed by Immich’s documentation, rather than a report of an Immich deployment or a guarantee about a new archive business.