[sungrokshim]

As long as the cloud providers of the world keep inevitably converging to, often against their own will, a single standard for each piece of the infrastructure (e.g. k8s, postgres, S3), most things that you deploy on the cloud will remain portable. You are never truly locked-in.

Similarly, if you want to, you can move away even from a PaaS that is explicitly designed to lock you in to another cloud provider. And as I mentioned in the post, this is exactly what we've done for countless companies that wanted to move from a PaaS to the big 3 cloud providers.

The more important question is: what is the switching cost? Why do companies so rarely switch hosting providers and if they do, why does it take months and sometimes years for them to move?

We want the process of moving from Porter Cloud to one of the hyperscalers as arbitrary as a click of a button.

[latchkey]

> We want the process of moving from Porter Cloud to one of the hyperscalers as arbitrary as a click of a button.

What I don't understand is why someone would start with Porter Cloud.

[mitchitized]

Small startup with brand new team, no devops/infrastructure/security. Most engineers are mid-level and not really strong on infrastructure, they are hired to build features and backend.

In this environment something like Porter Cloud would make it far simpler to deploy apps as they were being built and know that there is a chance of scale (at least to a certain degree). Otherwise you get to watch engineering grind to a halt while everyone learns how ECS/AIM/SSM/XYZ works.

[latchkey]

Spend some time understanding what Cloud Functions has to offer. There really isn't much to it at all. A http handler function is all you need. No infrastructure or need to do much deeper than that.