Do you have a strategy for that situation? Your old Ansible branch hopefully is still there and compatible with your recent production code changes. And your sqlite DB is replicated to an external storage and your data is reachable even if you have lost control over “your” PaaS account.
You have found a hosting provider where this is not a risk?
Fly is different enough that moving to or from it takes much more time and effort.
Your level of abstraction may vary. I stick to VMs after realising how much overhead I had with the cloud as a one-person shop.
Teams can interface with k8s which is also standard nowadays, taking you can spawn a cluster fast.
It is? Fly seems to be only docker containers. You can't get much more standard than that these days!
Have you actually used fly? It's pretty vanilla. Having migrated to and from fly I don't think your assessment is accurate.
It uses Docker files or Heroku style procfiles - not particularly exotic. Your apps live in a private network, which is managed for you.
a) Cloud providers; b) Hosting providers; c) Collocation; d) On-prem;
The only things that help protect you against this are (1) having named contacts on your account who will vouch internally at a supplier; (2) negotiating these clauses in contracts to prevent instant suspension in all but the most serious cases; and (3) utilising multiple suppliers.
I agree that in all cases, you depend on someone, but you can lower the risk to the point where other dangers that threaten your business become more probable.