Immich is extremely good, and has amazing features ( like identifying objects and faces ) which make it very easy to search for photos if you have a very large library.
However you should run it on a server you trust (so you should selfhost it instead of using a vps or any public server ) and hide it behind a VPN if you want to have access to it through internet when you’re not at home.
It’s open source. It’s lacking e2ee but it’s fine if you’re selfhosting it. (Depends on your threat model)
Thanks for sharing that. Personally I pretty much stopped caring for self-hosting as with my Nextcloud journey and self-hosting email I very well learned this isn’t for everyone. Now I can fix those issues, but that’s not feasible for normal users. During this time also more and more good solutions have become available. I kinda lost my belief that everyone should have their own server and federate. That would be ideal, just not realistic. Instead, now I am more focussing on companies that build good alternatives. Ente pretty recently opened up for self-hosting, so documentation might change, but still a lot of work to maintain your own instance, compared to just paying them for doing it.
Immich is self hosted software. In that context E2EE is not usually necessary.
Why do you feel E2EE is a hard requirement for self hosted software? E2EE is most relevant in contexts where you don’t trust the service provider or infrastructure, but in this case you are your own service provider and the infrastructure is yours.
Yeah, I am not quite agreeing here. People do host on public cloud/private could. Thinking they are doing self-hosting. This may only apply if you have your own hardware, and you control every bit of that. Then you still e.g. need physical security to the place. There is a lot to consider. E2EE is a way more efficient security measure. E2EE is not only about service provider, but also a measure against theft, interception, etc.
Adding to that, pictures contain a lot of sensitive information, which can basically reveal anything about you. You should also treat it as such with the appropriate security requirements. For me there are not many differences I make there between pictures and securing my passwords.
This seems to be more of an argument against self-hosting (or “non-self”-hosting in the case of using a cloud provider/VPS). But that is different topic I think.
Where I agree with you:
Most people probably shouldn’t self-host
Using a cloud provider for “”“self”“” hosting, is a different context with more threats and risk to consider, and shouldn’t be confused with actually self-hosting.
All other things being equal, E2EE is usually preferable from a security/privacy point of view.
Where I don’t agree:
I think Self-hosting is a valid approach for some people, and E2EE in that context isn’t strictly mandatory.
Then you still e.g. need physical security to the place
You do, but you need this anyway. If someone can physically steal your home server, they can physically steal your personal devices.
Where physical theft (or seizure) is a risk, traditional physical security, strong passwords, and encryption at rest is important (for servers and for personal devices). A primary use for both Ente and Immich is backing up photos from a phone or personal device, if your server isn’t at greater risk of physical theft and compromise than your personal devices, I don’t think you are fundamentally less secure by self hosting.
E2EE is a way more efficient security measure
Depends what the goal is. E2EE is a minimum requirement for me in many/most contexts, but it does limit or complicate things in other ways, and can add complexity. Proton (also Signal) is a good example, they make great products, but otherwise not too complicated features that non-privacy focused companies trivially build out, can sometimes take Proton years to get around to, Not all of that relates to difficulties related to E2EE but some of it does. Proton and Signal are cloud based solutions, so the tradeoff makes sense in that context, but in the context of self-hosting the benefits of E2EE seem a lot smaller and those costs in complexity are still present. I’m not saying E2EE has no value in a self-hosted context, just that the cost/benefit is a lot different.
E2EE is not only about service provider, but also a measure against theft, interception, etc.
It does offer robust protection in those contexts. But its not the only valid approach.
FDE/at-rest encryption is a much more common approach against theft/seizure.
And there are various approaches to protecting against interception that don’t involve e2ee (also, for most of us, I think targeted interception of our photos is out of scope for our threat models). If you trust Wireguard to protect your connecting to a commercial VPN, I don’t see why you wouldn’t trust it on your own hardware.
I think we are agreeing broadly that E2EE is usually desirable and good in most ways and a really elegant and desirable feature, but disagreeing in the specific context of self-hosting (on your own hardware), I understand preferring E2EE but I don’t think it should be anywhere near a hard requirement.
FWIW, the E2EE requirement in the Photo Management Section seems intentionally written to apply to cloud providers and exclude self hosted options:
Summary
Cloud-hosted providers must enforce end-to-end encryption.
And from the github discussion:
For Cloud based photo management products, that can not be self-hosted, we can borrow points from Cloud Storage section.
Yeah i sont think there is much disagreement here. I would just rather not recommend tools that don’t have it. To just protect people from making the mistakes here. Aso because we try to target everyone and not just technical peopl. Those people will find there way to these situations anyway I think.
Actually when you put it this way, what your wrote here is the same logic I use to support my (personal) opinion that Arch shouldn’t be one of the recommended distros (vast majority of people, including a majority of Arch users in my opinion, won’t and can’t secure their system to the same degree that they would get out of the box with one of the other recommended distros).
On the other hand, I don’t think it would be a good idea to just be totally silent on self-hosted solutions and tools. Since we do have a community and an audience that does skew towards the somewhat technical side. On the whole I think PG does a pretty great job of finding the balance between being technical and nuanced without being overly technical and inaccessible to less technical users. I guess I think self-hosting should be acknowledged as a valid approach to privacy but not go so far as to encourage self-hosting. I think how Arkenfox is presented would be a good template for how self-hosted (or more advanced options more broadly) can be framed
Ente Photos is incredibly simple and lacks half of most basic features such software usually can do. I would never recommend it just because it is e2ee now. Yes, biased and happy Immich user, no issues for year and a half allready. But really, they are not even close to compare.
For many, the most important item on the list is the “Stable release”. Prior to a stable release, we have a list of tasks that we are actively working on. Those include the following:
Mobile-server synchronization rewrite
Mobile database migration (Isar to SQLite)
Mobile backward compatibility strategy
Server migration from TypeORM to Kysely
Change the default UPLOAD_LOCATION from /usr/src/app/upload to /data
A new asset visibility field (something like { visibility: 'hidden' | 'archived' | 'private' })
Svelte 5 migration
With that said, we are now expecting to have a stable release in early 2025.
Hard to know exactly where these are at, but it does seem like they are closing in on the 2.x. There seems to be a bit of ironing out that came with some of the sync changes as Alex mentioned in the most recent release:
The road-to-stable is bumpy, but at least, we have made memories together with the recent changes and issues with the new memories implementation
I think this one will be a very exciting one to add to the PG list once they hit a stable release as it is a much more solid non-e2ee option than Photoprism. Amidst some of their breaking change releases it’s not even been that difficult to update my server and apply the fixing migrations.
Anyways, just a reminder that this is getting closer and bump it back up on the list and everyone’s minds.
We are thrilled to announce the stable release of Immich!
This has been a journey long in the making. So much has changed since the first commit on the project, all the way back in February, 2022. The project and team continue to grow, and today we’re proud to announce v2.0.0, our stable release. Stable signifies that we have now resolved a significant amount of technical debt. It also means we will be prioritizing compatibility and less effort will be required to keep Immich up-to-date. Finally, it means that the warning banner on the website has been removed!
I got bitten by their migration bug and now none of the photos and videos load.
I got my files out of the TrueNAS server but its a pain to recreate. I dont know if I want to go back again and deal with this.
Yeah to be fair that was the risk we knew we were taking but I totally get the pain. Perhaps see others experience as time goes on now that tthe claim is forward compatibility.
I think I had looked at Ente a while back before they had open sourced their server and didn’t have really good mobile upload options for ios so my family couldn’t use it. Those are all resolved now so from a feature perspective I entirely agree with you. In fact having that e2ee might make Ente a no brainer for some use cases and one in particular is providing a photo service for others with zero trust model in place.
That said, Immich is a very popular feature rich alternative that removes complexity where e2ee isn’t needed (sticking Immich behind a VPS for a small handful of users like a family).
Ente’s product is the cloud, that is effortless to consume.
We don’t look at Immich as competition. Ente is serving customers who don’t have the energy / technical expertise to maintain a reliable storage infrastructure. While Immich serves a segment that understands technology and loves to tinker. I’d like to believe that both projects are making the world a better place, but in different ways.
Even on the self hosting front, I would assume that Immich has made design decisions that are better suited for a home-server setup, while we’ve optimized to run in an untrusted environment. For example, we’ve designed Ente to be end-to-end encrypted (ente.io/architecture) and to maintain multiple replicas (ente.io/reliability). These are decisions that will affect your experience as a server admin.
Taking a step back, what I meant is, the core products for both the projects are different, and the customers we’re seeking to serve are different.
In this light, I would replace photoprism with Immich as the best photos app to run in a local trusted environment with greater ease of development for customization, and I would suggest Ente as the default choice for untrusted envionments, especially multi-tenany and publicly accessible services.
Yeah here we very much disagree. You put this on a VPS. That is not quite self hosting. At that point you have to trust the provider they don’t snoop at your photo’s, in essence not any different from trusting any other cloud storage provider. Even if you would run it on your own hardware Ente seems way more robust. I do also wonder how you arrange for offside back ups?
Immich also repeatedly has said that e2ee is not possible, Ente proofed them wrong. It just comes down to architectural choices and Ente here has actually done privacy and security by design here unlike Immich. I don’t actually believe Immich to be more populair than Ente but regardless of that that should not be a criteria for recommending it. We also do not recommend putting mailcow on a VPS if it would be more popular than Proton Mail.