duplicity vs SpiderOak

Data is encrypted locally before being sent, and kept encrypted by a key that is never stored on the remote machine. So you might even store your data on a public space, people would still need your key or brute force it.

Duplicity uses the rsync algorithm so only the changed parts of files are sent to the archive when doing an incremental backup. For instance, if a long log file increases by just a few lines of text, a small diff will be sent to and saved in the archive. Other backup programs may save a complete copy of the file.

You can retrieve older versions or files you recently deleted locally even after having updated your backup.

Licensed under GNU GPL v2.

Duplicity does not make many demands on its archive server. As long as files can be saved to, read from, listed, and deleted from a location, that location can be used as a duplicity backend. Besides increasing choice for the user, it can make a server more secure, as clients only require minimal access.

Docker allows to run programs on any Linux without having to really install them, and allows to manage versions so it runs exactly the same on different machines.

Thus you have a single service for all of the things.

The Spideroak client is available for Linux, MacOS, Windows, Android and iOS.

SpiderOak updates only that part of the file that has changed, saving bandwidth and time.

Data is locally encrypted before uploading to Spideroak. They cannot recover your data even if they wanted to since it is stored in encrypted state on their servers.