Why NOT choose custom backup scripts and cron jobs and choose SimpleBackups instead?
The problem with custom scripts is that there are many failure points and a lot of components of the script can go wrong.
For example, if you forget to update your database credentials in your script after you change them or if you don't have enough disk space or if your remote storage API or credentials change for any reason, all of these cases will break your script.
Backups won't be taken and in many cases you won't even be notified unless you have also added backup notifications to your script, which will also need you to maintain the integration of the notification tool or email.
Why NOT choose cloud provider snapshots and choose SimpleBackups instead?
In fact, for this one, we recommend that you actually have both, your own database and file backups in addition to snapshots of your web.
So you have a virtual machine snapshot.
All server providers offer automated backups of your entire server for a fee, but what happens when you delete your server by mistake?
Or if some files were deleted by mistake from your site?
Certainly you are not going to restore your entire server snapshot just to get the files back.
Additionally, server snapshots do not really back up your database (unless it's on the same server, but to restore a database you will need to restore the entire server snapshot on a new instance) and won't allow an individual database restore.
You can only restore snapshots of the entire server, not individual files.