On Cloud Foundry we&#x27;ve found that we get buy-in from both operators and developers.<p>Operators heave a sigh of relief: &quot;Finally, I don&#x27;t have to clean up after devs! They can&#x27;t break the platform for everyone else! I don&#x27;t get 3AM phonecalls to fix someone else&#x27;s mess!&quot;<p>Developers heave a sigh of relief: &quot;Finally, I can just deploy without dealing with suspicious operators! If it breaks I don&#x27;t get berated by an operator who got a 3AM phonecall!&quot;<p>I imagine OpenShift and Heroku guys can tell the same stories.<p>I work for Pivotal Labs, so I get to see projects with PaaSes and projects without PaaSes in a variety of companies, on a variety of platforms, with a variety of goals. But one thing remains constant: PaaS-deployed projects are easier.<p>In a PaaS-deployment project, you set up your credentials, set up CI&#x2F;CD, then you just get on with doing the thing that matters: building a product.<p>In non-PaaS projects, you spend eye-blistering amounts of time and money trying to just deploy the damn software. The whole feedback loop turns into a tangled pile of spaghetti behind somebody&#x27;s bespoke deployment process. Backpressure causes enormous shear stresses throughout the project because development is iterating quickly but there&#x27;s no way to, you know, <i>see if the users like it</i> or to know <i>if it actually works in the real environment</i>.<p>It always boggles my mind that folk are happier to squander amazing amounts of engineering time and salary dollars instead of just renting or installing a PaaS.