> But unlike in traditional PaaS, there is no framework that restricts what you can code (language, libraries, etc). I'm not sure how traditional PaaSes are li

> But unlike in traditional PaaS, there is no framework that restricts what you can code (language, libraries, etc). I'm not sure how traditional PaaSes are limited in that sense. Heroku accepts a wide variety of software through the buildpacks mechanism. Cloud Foundry supports both buildpacks and docker images, with clean extension points to add further mechanisms -- for example, .NET-on-Windows deployments, which is under development. Disclaimer: I've worked on Cloud Foundry and I'm employed by Pivotal.