Lambda and GCP Cloud Functions do have cost controls. You can specify the maximum number of instances that can be spun up at any given point. I think the UX ca

Lambda and GCP Cloud Functions do have cost controls. You can specify the maximum number of instances that can be spun up at any given point. I think the UX can make it more friendly to specify the types of traffic and cost you’re expecting but most erroneous spikes are the result of a customer misconfiguration or a legitimate spike in traffic. It’s the former which are problematic for customers. They can request a credit and we (GCP) try and accommodate. It’s not a feature designed for profit. But it also tends to fall below the cut line for prioritization to fix. But it’s in the backlog and doesn’t go unnoticed. (Former PM on GCP Cloud Functions)