One use case for CloudBold is creating blueprint templates for multiple clouds. Another is cost management or optimization. There is a piece that comes along with CloudBolt called Kumolus, and there is a lot of interest in that side of cost management.

We used the solution to manage a pretty substantial financial institution’s IaaS infrastructure. We were also using it to manage the infrastructure as a service of a government area. It was pretty good.

We use the solution to provide self-service to end users in our virtual environment.

Our primary use case for this product is for a mixed set of services, including providing IT, multi-cloud management, single pane of glass control panel, providing metering and charge-back capability, role-based access control, and other things. It's a long list. My focus specifically is with regard to the data center and cloud. Enterprise businesses are using this solution. 

We use this solution ourselves as well as for our clients. We're a partner with CloudBolt and I am a solution specialist/product manager of cloud and data center services.

CloudBolt is very useful for a customer currently using the multi-cloud model, and wants to manage everything on a single console, e.g. GCP, AWS, Azure, or their VMware infrastructure.

There are also multiple things we can do through CloudBolt which are important. One thing we can do is to schedule power on and power shutdown so those processes are automated. I was able to implement it even in the trial version of the platform. They have a free trial for some servers where the license is not required, so I implemented it on my test environment and that worked fine with me.

Another thing we can use CloudBolt for is VM deployment on the cloud. We need to install the Ansible tower and configure it, but through CloudBolt, we can deploy everything on the cloud.