Answers by Ryan Campbell and Spike WashBurn, Architects at CloudBees.
A. Both DEV@cloud and RUN@cloud are available for free today. DEV@cloud pricing is available here. RUN@cloud pricing is available here.
A. No - you will work with CloudBees and not have to deal with two accounts.
A. Although, CloudBees today runs on Amazon EC2 - it is designed from ground up to be IaaS-agnostic. This means that as a developer, you will have the flexibility to choose a IaaS platform and not be tied to a particular IaaS vendor. In addition, CloudBees believes that PaaS is beyond just a deployment platform - developers should be leveraging the cloud to build and deploying their applications. With DEV@cloud and RUN@cloud - developers can just do that - develop, build and deploy to the cloud.
A. Yes it is. You can setup your DEV@cloud environment to push to RUN@cloud.
A. Currently we have no plans for IntelliJ and PostgreSQL. We are considering support for Sonar.
A. Google App Engine white lists APIs. CloudBees does not white list API's. In addition, CloudBees believes that PaaS is beyond just a deployment platform - developers should be leveraging the cloud to build and deploy their applications. With DEV@cloud and RUN@cloud - developers can just do that - develop, build and deploy to the cloud.
A. CloudBees has separate teams focusing on DEV@cloud, RUN@cloud and Jenkins Enterprise by CloudBees. Jenkins Enterprise by CloudBees is a priority for us - Jenkins founder Kohsuke Kawaguchi is on the CloudBees team leading the Jenkins Enterprise by CloudBees development efforts.
A. I'd love to do that if there's enough interest! Please send us your thoughts at: info@cloudbees.com for topics we should present in the future.
A. DEV@cloud works just as Jenkins would handle these issues. This means that as a developer, you can configure to poll the source code management for changes or builds periodically.