Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If I were fly I’d implement spending caps just to filter out unserious operators.

My implementation of that feature would be when you turned it on fly would just kick you off.

No serious operator wants a provider to turn their system off. So if you want that it’s pretty clear you are hosting a silly system. Which likely costs more to support and drives less margin.



The real solution is to make it simpler to set up billing alerts. If my hobby project is ever projected to cost more than $0.50/hr, let me know. Billing alerts should be part of onboarding for all cloud providers, especially for individuals that don’t want surprises.


No serious operator would choose a provider with your implementation of that feature.


I agree that no serious operator would choose a provider whose spending cap feature was "enable this feature and we kick you off the platform".


People will pay to be abused: c.f. Oracle


Hu? For any business having a due to a cap throttled service is better than losing the money straight away due to an accidental cloud bill explosion.


And yet every single cloud let's you scale from zero and play and experiment. They know today's tinkerers are tomorrow's CTO decision makers.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: