Here are my two cents, as I am very familiar with this space[1][2]
The problem of trying to position your product as "an easy way to deploy on over GCP" or "an easier way to do K8s" is that your product is always limited by the potential of what the underlying platform directly offers. I know multiple K8s management startups (in the pre-LLM era) that failed because of this.
You are not required to, but will be seduced to build 1:1 mapping to the concepts of the underlying systems. So, anyone using your product has to learn both the underlying platform (E.g., GCP) and your system. And the problem is that all of those concepts have been derived either directly or indirectly from AWS or K8s, both have a focus on SREs much more than software engineers.
The second problem is that there are now two interfaces to change something - one is infra.new, and another is the underlying platform directly. Your system will have to catch the drift in deployment when someone goes and changes the underlying platform.
The only major way to win is to have your deployment system, e.g., an alternative to vercel.com, Render.com, or https://railway.com.
- Vercel - a deployment system for frontend engineers (that's my perception)
- Render/Railway - a deployment system for backend software engineers (that's my perception)
1. - https://github.com/ashishb/gabo
2. - https://ashishb.net/programming/how-to-deploy-side-projects-as-web-services-for-free/