

Alright so this is a feature that a homelab user can actually use - backups. Could you expand on how you will be managing this feature / plan to implement it once it is offered?
Very good question, the backup/restore processes are under development. We would like to use the Borg backup for and prepared the backup services for access each others both local network and vpn network. You can find it takeing a look at the source code of the framework-scheduler repository (https://github.com/safeboxnetwork/framework-scheduler/blob/main/scripts/scheduler/entrypoint.sh # it is started at line 1339)
I’m happy to answer — I am one of the developers of Safebox. First question: the store. It’s not finished yet, but if you visit our original gitea site (https://git.format.hu/safebox/default-applications-tree) and check the template examples, you’ll see that any application that can run in Docker can be added. I will soon move this repository to GitHub so it can be freely forked and you can add your own. You can already try adding one on an earlier (uglier) interface that we experimented with: http://<the IP address or hostname of your Safebox>:8080/manage_old.html. Click Settings, and the first menu item is the option to add another repository.
Second question: remote access is not subscription-based, and it does not require VPN. If you have a public IP address, install Safebox there, register a domain name somewhere (point it to your IP address as an A record, wildcard is also possible), and the proxy service will work. (But be aware: Safebox will also be accessible on port 8080, and there is no authentication protection for now!)
Third question: I wasn’t very familiar with Podman when I started working on this (I only had to learn it for the RedHat exam…)