[webmobdev]

> Personally I'd prefer true pay-as-you-go without hard limits, even if it's a bit more expensive.

Please, a hard no to that. That's the worse aspect of AWS, Azure and all those new huge hosting centers - hard to calculate the real cost and set a budget.

I don't know about Netlify, but the old Linode (before it got acquired), was flexible with its "hard" limits in a plan - for example, if your site got slashdotted / Digged (or was that dug?) and suddenly saw a spike on its resource, exceeding the limits, they were quite accommodating in not charging their users for the unexpected extra usage. Linode even wouldn't mind an occasional surge in resource a few times a year. But if it happened more frequently, they would recommend that you upgrade to a more suitable plan. They earned a lot of goodwill that way from their clients who really appreciated that their server / site wasn't unexpectedly taken offline because of a resource crunch they hadn't paid for and / or anticipated.

[TobyTheDog123]

Like another comment said, different strokes for different folks.

I would much rather pay overage fees than have my site go down due to a hard limit, but I would also like the option to choose the opposite.

That way you appeal to both sides of the scalability-vs-predictability crowd.