Sounds good.
Rclone acts very much like scp or rsync, so there isn't a need for a database. We will need some additional parameters in the fw_env: the remote to use and the root path in the remote.
This might be one parameter such as:
rclone_remote: "gdrive:garden/2017/"
which will be split by the code to use the "gdrive" remote, copying the launch to garden/2017/launch_"
Moving files to the remote using rclone is: rclone copy <file> <remote>:<path>
Getting them is: rclone copy <remote>:<path><file> <file>
The only potential problem here is that this will require subprocess calls and not intrinsic python calls.