The ability to manage most clouds is helpful, especially with extremely large organizations where we have multiple cloud providers, and we cannot centralize management. It was one of the areas that really helped us, especially with managing and mapping resources. We also used CloudBolt to find a shadow IT resource. Nobody knew what they were doing or who was responsible for them.

The product takes care of a hybrid cloud environment and it helps me maintain control and insight across various cloud platforms. With regard to the application blueprint, if I'm able to create that using the platform then they are cloud agnostic, so I don't need to create different blueprints for different cloud providers. I just need to create one blueprint and I can select the target cloud myself. 

We were able to collapse over 95% of our orchestration directly into Chef and CloudBolt as opposed to having well over 300+ steps of orchestration in vCO and multiple scripts to call out to other self developed API's to do that same thing. Our delivery of VM's went form 19-23 minutes to 8-13 minutes depending on the cloud. The willingness of the CloudBolt team to improve their product at a very rapid pace has resulted in a delivery of over 130+ RFE's in less than 6 months to enhance the compatibility with company services, functionality and aesthetics.

Update: We are up to over 200 features in the last year and a half.

The ability of our tier one and two teams to support CloudBolt was >80% on day 3. Tier III and Architects spent up to 40% of the project time supporting our previous cloud management platform; with CloudBolt we were able to reduce product support to less than 3% of work time spent.

We only recently (last 12 months) started to build and automation platform. We focused first on platform automation, as we already had a bevy of Jenkins driven scripts in to deploy our applications.

CloudBolt's ease of use, coupled with our initial focus on fully automating infrastructure deployment, has won accolades from our internal stakeholders. A specific development director for one LOB has been our biggest advocate, lauding his ability to provision and destroy multi-server environments on-demand in step with his application releases.

We also took this opportunity to transition to a full infrastructure-as-code model, implementing Puppet Enterprise at the same time, driving a new level of consistency to those deployed environments.