Hybrid Self-Hosting (feature request)
I love that ente.io can be self-hosted, and I'd love to do it for myself and my friends, but I don't necessarily trust myself / have the time to have a great redundancy / backup story. Legacy access ("bus factor") is an issue too, especially if I'm hosting for others -- who will keep the infrastructure running long enough after I'm gone so that people can export their data?
I'd love to self-host but still leverage ente's infrastructure as a paid user. It'd be amazing if there was a "hybrid" self-hosted setup where we could additionally still pay for ente storage and keep our files backed up there as well. There'd have to be some API to create family accounts under that plan and upload on behalf of them all from the self-hosted instance.
If there were a large enough number of users on my instance, I'd also love to be able to pay for even larger amounts of storage (i.e. just a scaled-up family plan).
Continuous export and backup from non-self-hosted ente won't work in my case, since I want to provide the self-hosted service scalably for family & friends as well.
After going through the thought process of writing out this feature request, I realize this is a pretty big task. I do believe it would be financially beneficial to ente, however, as it might sway some self-hosted users to keep paying ente for backup storage. There might also be other ways of solving the ultimate goal of this feature request which is essentially to have some legacy recovery story for self-hosted, where the host itself disappears.
I'd love to self-host but still leverage ente's infrastructure as a paid user. It'd be amazing if there was a "hybrid" self-hosted setup where we could additionally still pay for ente storage and keep our files backed up there as well. There'd have to be some API to create family accounts under that plan and upload on behalf of them all from the self-hosted instance.
If there were a large enough number of users on my instance, I'd also love to be able to pay for even larger amounts of storage (i.e. just a scaled-up family plan).
Continuous export and backup from non-self-hosted ente won't work in my case, since I want to provide the self-hosted service scalably for family & friends as well.
After going through the thought process of writing out this feature request, I realize this is a pretty big task. I do believe it would be financially beneficial to ente, however, as it might sway some self-hosted users to keep paying ente for backup storage. There might also be other ways of solving the ultimate goal of this feature request which is essentially to have some legacy recovery story for self-hosted, where the host itself disappears.
Photos