Taking those steps wouldn't really solve the core issue anyway, a single dependency requiring a newer versions of the container would make the app fail. Thus forbidding huge portions of the rapidly evolving gems one can find out there for web development.

Sorry PaaS, you already put me off by having to install your own tools just to be able to upload an application, which both with Heroku and OpenShift gave me a headache early on.

What clients need is bare infrastructure, no provider can maintain the numerous combination of versions an application might need to run at best. This business is *not* about solving real problems, it solves some and create a whole bunch of new ones. In particular for production applications.

IaaS is an infrastructure I have full control over, that's what we need. Not a restricted environment where the provider decides which versions to run. It defeats the very purpose of PaaS claims: Getting ride of cumbersome maintenance.

Also, all of this run on hardware provided by other IaaS provider. So, even considering the economy of scale, I'm being charged your service + the service of the IaaS provider, right ?

I will pay for the goods right from the source, EC2, Azure, whatever. No middle men thank you.