There are quite a lot of cases where you could find yourself facing a large bill unexpectedly. Forgetting about a server you spun up to try something out, with may platforms having your server hacked (or even DDoSed) could result in huge bills for bandwidth. With Dply you only pay what you pay up-front if you choose to add time to a server. There are no bills racking up. The flip side is that if you forget about it, it could vanish on you. Automating your deployment with something like a user-data script that pulls your code from Github would make this less of a concern. Permanent services on Dply are certainly possible but not the primary use case for most users.

It's definitely a worry, but to their credit AWS at least are pretty nice about accidentally racking up a big bill. Last month I forgot to shut down a GPU instance I'd been experimenting with on my personal account and got hit with $150 I hadn't been expecting, but on explaining the situation to support they cancelled the bill from the previous month and applied a credit to my account to cover the time it had been active this month. I'm going to guess that's a one time thing, but the gesture was very much appreciated.