cloudControl vs Stackato: What are the differences?

Developers describe cloudControl as "Deploy and scale any app in Java, PHP, Python, Ruby and more". The cloudControl PaaS supports multiple languages and their ecosystems natively and without vendor lock-in through open source buildpacks. Native support means you can continue to use the tools you know and love for development and simply push your code to the cloudControl platform. A buildpack is run on each push and prepares your app for deployment. E.g. compiling source code, minifying CSS and Javascript assets, pulling in dependencies with Maven, Composer, PIP, Bundler and more. On the other hand, Stackato is detailed as "Enterprise ready private PaaS based on the Cloud Foundry open-source project and Docker". Stackato runs on top of your cloud infrastructure, and is the middleware from which your applications are launched. Developers simply upload their application source files to Stackato via IDE or command-line. Stackato automatically configures the required language runtimes, web frameworks, and data and messaging services.

cloudControl and Stackato belong to "Platform as a Service" category of the tech stack.

Some of the features offered by cloudControl are:

• Develop and push code in any language- Native support for Java, PHP, Python, Ruby and more without vendor lock-in.
• Deploy and scale your apps easily- Launch new versions without downtime and use horizontal or vertical scaling.
• Use the flexible and secure runtime environment- Run your code in secure Linux containers and easily use Add-on services to add databases and more.

On the other hand, Stackato provides the following key features:

• Web console
• Activity timeline
• Multi-tenancy