The solution is not easy to use. It's not intuitive enough to click anywhere in the solution and make it work. Likewise, Cloudbolt takes a long time to configure and set up properly. If I install an app, I should be able to quickly get it to work without taking a long time to configure and set it up.

The management of SaaS must be improved. It would be great if CloudBolt could also manage SaaS resources.

The area of integrating on-prem and cloud needs improvement. Another area that the solution needs to improve on is the UI. The UI can be much better.

For improvements, I would say that they could maybe increase the number of integrations and add more out-of-the-box work flows and possibly a new or improved user interface. They would all be features that would improve the solution. Currently, the interface is quite good, but an improved one would be better. With regard to billing and charge back, I would really want the platform to have some of those capabilities.

Integration should definitely be included as an additional feature. An advanced level or an enhanced user interface and maybe a good set of new application blueprint out-of-the-box, which any customer can download and use, would be helpful additions.

I had an issue with the scheduling feature of CloudBolt, but I'm not sure if that's been fixed in the new version. For example: I scheduled a job for powering on and powering off the VM, but there were times it didn't work, so I had to create a new job for it. It's only the scheduling feature that needs improvement. The rest of the CloudBolt features are okay for me.

An additional feature I'd like to see in the next release of CloudBolt is costing and the consumption of cloud resources, or how much has been consumed including the cost, should be included in the report to make it easy for us.

Load Balancing (Multiple F5), XaaS Services, Containers, and Parameter Overriding are the only areas left that I have seen that the foundation has been laid for but could use more refinement.

Update: Load Balancing Has Been Rounded Out, Containers are now in, and parameter overriding has been implemented and improved upon several times and XaaS is possible and improved functionality is coming in the next version.

Support for Active Directory groups, currently user management in CloudBolt groupsin managed individually. We had a previous access model that was based on AD groups, and allowed users to be able to use the product with their group membership, so no users were ever added directly to the provisioning system.

Support for containers is basic and needs improvement. If we were to need more today, we could write Python scripts to make API calls as needed.

The system needs more real-time reporting of actual capacity usage, rather than allocated usage. For example, one LOB has a four node Nutanix brick allocated for their development hardware, and we've had to implement outside-of-CloudBolt processes to give them a true representation of their actual via. allocated usage.