Thread

1. joshdavham · 1791078994 · focus · HN ↗

   It’s incredible that in 2026, AWS and GCP are only just now introducing this. It’s possibly one of the most obviously needed features for a cloud provider.

   Also, does anyone know why it’s taken this long? I suspect it’s a technical reason. While one could be cynical, I doubt it’s an intentional business/product decision. Hard spending caps are both excellent product differentiators and could possibly save these providers money as they don’t have to forgive their users when they accidentally over-use a service.

   1. twoodfin · 1791079268 · focus · HN ↗

      This is one of those features that customers think they want without having thought it through:

      “Never let me spend more than $X” also means, “Shut down my business-critical app/service/solution at 2 am on a Sunday morning because Joel in IT forgot to plan for the new report runs.”

      The product design work to let customers have the first thing without risk of major pain from the second thing is non-trivial.

      1. simonw · 1791079715 · focus · HN ↗

         I don't really understand that argument. This seems pretty obvious to me, as a customer. Is this really something that companies don't understand?

         Sending an email when your budget gets low shouldn't be a big lift.

         1. kasey_junk · 1791080458 · focus · HN ↗

            Big companies have thousands of budgets. An email is _worthless_. In fact, it would probably cause me to lose faith in a cloud that provided that as the control.

Unofficial Hacker News client; not affiliated with Y Combinator.