"I'm curious about your view of the hybrid deployment model many of our users prefer with an on-prem instance that can be deployed to multiple service providers

"I'm curious about your view of the hybrid deployment model many of our users prefer with an on-prem instance that can be deployed to multiple service providers." I see these as 2 separate things: - By "on-prem instance" I'm guessing you're referring to a local VM which mimics the remote deployment target? I think that is a cool and useful feature in the "nice-to-have" category. - By "can be deployed to multiple service providers", I guess you mean that the portability between cf-enabled providers frees developers from lock-in? In my opinion this solves a non-existing problem. Developers can already deploy to multiple service providers with almost zero effort, because all service providers rely on open standards for deploying web applications. As a result portability is incredibly good between dotCloud, Heroku, Cloudfoundry and almost everybody else. Of course it's up to the developer to not lock themselves into proprietary APIs which are only available on certain service providers (eg. App Engine).