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. handoflixue · 1791080224 · focus · HN ↗

         The alternate conversation is "the new report run had a bug and cost us $1,000,000 over the weekend" and I think that one's usually worse.

         But one could just have two categories of service - the default capped plan, and a special Enterprise one where you sign a contract making it clear you understand the consequences of not having a budget limit.

         Also, if your average usage is $900, set your hard limit at $2,000, not $1,000. Then when the report runs $500 over expected, you get a soft limit email and still have your report. Even a "business critical" run is probably not actually worth more than double your average spend.

         1. Gigachad · 1791081658 · focus · HN ↗

            Even if you set your cap at $10,000 it would be better than nothing.

            The price cap should be the number you’d be willing to spend to avoid an outage vs when you’d rather kill everything and work out what happened.

            1. twoodfin · 1791082400 · focus · HN ↗

               This is the right perspective, but the folks who would be setting this cap for the customers that matter likely have no idea how to price that, or the price would be so absurd as to make the cap meaningless.

               How much would a hospital pay to avoid unexpected downtime of their software systems?

               1. Gigachad · 1791082609 · focus · HN ↗

                  I would think once you reach the scale that this becomes an issue you can afford someone or a team to be monitoring the system 24/7 able to respond to a price spike.

                  Price caps are for small scale stuff where you wake up on Monday and see 1000x the normal bill.

                  1. twoodfin · 1791083025 · focus · HN ↗

                     I imagine that the product folks at places like AWS are averse to introducing discontinuities in the experience based on scale. Little customers get the same experience as big customers who get the same experience as mega customers.

                     Obviously they’ve changed their mind about cost management in light of the scale and dynamism of agents, which isn’t too surprising.

Unofficial Hacker News client; not affiliated with Y Combinator.