cloudControl vs Cloud Foundry: 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, Cloud Foundry is detailed as "Deploy and scale applications in seconds on your choice of private or public cloud". Cloud Foundry is an open platform as a service (PaaS) that provides a choice of clouds, developer frameworks, and application services. Cloud Foundry makes it faster and easier to build, test, deploy, and scale applications.

cloudControl and Cloud Foundry can be primarily classified as "Platform as a Service" tools.

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, Cloud Foundry provides the following key features:

• Application and services centric lifecycle API
• High performance dynamic routing
• Buildpack support

Cloud Foundry is an open source tool with 605 GitHub stars and 532 GitHub forks. Here's a link to Cloud Foundry's open source repository on GitHub.