I would generally advise against using GCP. I agree it's actually a great product, a better product even. But you're playing with fire. Google is a company tha

I would generally advise against using GCP. I agree it's actually a great product, a better product even. But you're playing with fire. Google is a company that automates everything and never picks up the phone. That's not 100% true, but it is in their nature. As a search engine that's all well and good. But for a cloud provider it's brutal. You want somebody who is going to lean into that more classic idea of customer service. Amazon is the classic one people point to because of their fantasism about customer service. You really can get someone on the phone at AWS, though not a happy person. These things are not disconnected by the way. As an engineer go work at Google. As a customer go spend at amazon. Or any of the others. Microsoft does customer service just fine. Even an unconventional option like kubernetes clusters built on linode or digital ocean. A trick I've learned over the years is to appreciate companies for what they are and partner with them for their strengths but also recognize their weaknesses. Is Google going to announce one day that they are going to Shutter GCP after all and that everyone has 6 months to migrate off? No of course not! But there's also a reason you have to be a little nervous about making that joke. More to the point with some of your other examples, all Google's tech is ai powered. To the extent that it can be. AI makes mistakes, some days you'll be that mistake. You have to appreciate too with Google the old "I don't know how to count that low" joke. What might for you turn into a multimillion dollar business Google could conceivably shutoff and never really notice. Maybe GCP has got better at this sort of thing too but my intuition is to not hold out for that.