Cryptomator vs Rclone Crypt or something else?

Looking at Crypt, I saw the following, which was not something I was aware of:

The obscured password is created using AES-CTR with a static key. The IV (nonce) is stored verbatim at the beginning of the obscured password. This static key is shared between all versions of rclone.

As for your question, there are options like borg and restic as well (Deja Dup a.k.a. Gnome Backups uses restic on the backend). It depends what is more comfortable for you between crypto and rclone. I haven’t heard of too many people using rclone crypto, so I would nudge a bit towards cryptomator here. I assume for rclone your cloud provider would have to listed on their provider list for it to be able to connect to it and push your files there.

Personally, I jump between borg and DejaDup (Gnome Backups). Now, to provide a heads up about borg and Dejadup (which uses restic), they both work off of “versioning” meaning that you will have older versions of your files there as well. This will mean a bigger backup. In the case your backup is too big down the line, I would recommend deleting the output from borg or Deja and just doing a clean new backup, just to cover the files you currently have without any previous versions. With that being said, my command for borg has been: borg create --verbose --filter AME --list --stats --files-cache=mtime,size --show-rc --compression=lz4 --exclude-caches /home/user/Downloads/borg_backup::Cloud ~/Documents. I would definitely use the man-pages to understand what it does. To not take up so much text, I have the commands surrounding it in my cheat cheatsheet: Codeberg - cheatsheets/borg.

As for Deja Dup, it is simple in its GUI. I point it towards another folder somewhere on my system (hypothetically ~/Desktop/backups/) and then have it do its sync. The first time takes the longest and then the rest are much quicker as they work off of delta syncs.

For both, I just upload the folders as-is to the cloud once I am done.

I hope that answers your question a bit.

Also, 100s of GBs is a lot of data. I would recommend ranking your data and uploading the most valuable data to the cloud. This would save on time and network bandwidth. A backup locally (before you upload) would take up about 95% space of the full data (depending on compression method), meaning you will need that disk space locally as well.