SQLite doesn't save you from losing your data when the instance goes away. One requires a backup to avoid that scenario. Sure one can opt for offline manual backups, but then one might as well use a static site generator that doesn't require any of that.

Why would you do manual backups? Just schedule cronjob to periodically upload the database somewhere. You can save it anywhere - other $5 server (not $15), to s3, even on google drive. I don't know if there is threat of database being corrupted midbackup due to writing in it, but if you don't want to risk it, just use sqlite online backup api.