Cloud Architect at a tech services company with 11-50 employees
MSP
Top 20
Aug 14, 2025
Enhancements for CloudStack can focus on integrating more hypervisors, as mentioned regarding current features. We're working on a new feature that will allow for certain limited functions, but over time, it will improve to achieve full integration with various hypervisors. That's one key area of ongoing development within the community. Additionally, there's notable activity shifting from VMware to KVM. We have successfully migrated a few customers, but some challenges were encountered with complex networks or intricate VMs. The community is addressing these hiccups, and improvements are on the roadmap. Furthermore, there's a GPU functionality feature that is forthcoming, which is an essential improvement and will be included in the next few releases. Customization freedom already exists because it's a community-driven platform. If I could suggest one improvement, it would be regarding containers. While we currently support the orchestration of container hardware or worker nodes, I want to add the ability to control the containers themselves.
CloudStack lacks a billing solution which would complete it as a full 360-degree product. Additionally, more themes and drag-and-drop interfaces could enhance the user experience. Improved documentation separating admin and user parts is needed for easier use.
The product had some limitations. So, I decided to write my own stack from scratch. The product does not have an easily implementable payment gateway. It must provide a payment gateway hook in future releases.
The market keeps changing, and so does technology. I think that container technology in CloudStack is an area that needs to be improved. Regarding container technology, Kubernetes is something many people want to use and something which, as of now, many are using currently. However, there is still room for improvement in Kubernetes, particularly with networking functionality and network virtualization. When it comes to what needs to be improved in CloudStack, I would say that it should stay the way it is currently. It should continue being a stable product that people can rely on since many may be inclined to follow the latest trends and hype, which is not always good for a solution's stability. It is crucial to prioritize stability, which is a key factor that companies seek. In my view, the platform could benefit from adding more metrics. More metrics would offer more insights and data on the platform's performance, utilization, and usage. Overall, I believe that having more metrics available would be highly desirable.
Senior Consultant at a tech services company with 201-500 employees
Real User
Feb 14, 2023
The number of contributors to this solution is relatively small compared to other solutions. However, if more frequent users of CloudStack contribute to the open-source community, it will significantly enhance the overall community experience and make it more useful for everyone involved. There is room for improvement when it comes to maintenance options in CloudStack, particularly with regard to rolling maintenance for multiple Hypervisors. CloudStack does offer this option, but it has not always worked as expected. However, I believe that this largely depends on our expectations for the solution and how we want it to work. As an example, CloudStack maintains a list of Hypervisors where we can host our virtual machines, and we may need to update these Hypervisors on a regular basis, such as every month or every two weeks. Instead of having to perform manual updates, it would be helpful if there were options to automatically perform live migration and update the Hypervisors properly. While there are improvements being made in this area, I believe that there is still some work to be done. Ultimately, the effectiveness of these maintenance options depends on our specific requirements and how we expect the solution to function.
My teammates have complained about the upgrade. The source code had massive files that had to be merged with our own development to upgrade to the latest version of CloudStack. It was quite painful for them. CloudStack could add some cost management tools to give me some control over the costs associated with the number of users of my services.
We recognize that CloudStack is an easy-to-use cloud management platform and, in my opinion, there have been a lot of improvements in the past few years, particular when it comes to the modern UI and overall ease of management. However, I believe that CloudStack needs to grow their marketing in the commercial side. They don't have a great piece of market share right now. For now, we have two versions per year, one being the LTS (Long Term Support) version, and the other is just for development. It's a very good platform for us at the moment, but one feature I would like to see is CloudStack for edge zones. This would enable us to use it for cloud edge computing, as well as enable search providers to use it to provide cloud service in edge zones, for example.
Architect - Cloud Serviced at a computer software company with 501-1,000 employees
MSP
Top 10
May 9, 2019
One area that needs improvement is the stability. It is stable, but there are issues. It is related to the lack of support for an open source product. It comes down to needing more active people in the product's open source user community. There are release notes with the product, but I would like to see more documentation. For example, it would be nice to have instructions on how to integrate with DPDK (Data plane developer kit) because it would make it much easier. I would like to see support for native VLAN, and fault-tolerance.
Senior System Engineer at a tech services company with 11-50 employees
Real User
May 23, 2018
There are some minor things that can be improved even more such as, perhaps, a bit more polishing on the GUI side to catch up with the API possibilities (which are really extensive) but otherwise nothing critical. New features are being developed daily and the product is constantly improved with new features and bug fixes. Currently, one interesting thing that is being seriously improved is the redundant virtual router capability, which enables zero downtime for customers during certain maintenance operations and cloud version upgrades.
CloudStack offers an easy-to-manage platform compatible with multiple hypervisors, enabling seamless networking and efficient workload scaling. Its advanced APIs and open-source nature facilitate automation and customization, making it ideal for extensive cloud environments.CloudStack is recognized for ease of setup, robust networking, and hypervisor compatibility. Supporting a range of workloads, it scales efficiently, offering flexible features like VM migration, private networking, and...
Enhancements for CloudStack can focus on integrating more hypervisors, as mentioned regarding current features. We're working on a new feature that will allow for certain limited functions, but over time, it will improve to achieve full integration with various hypervisors. That's one key area of ongoing development within the community. Additionally, there's notable activity shifting from VMware to KVM. We have successfully migrated a few customers, but some challenges were encountered with complex networks or intricate VMs. The community is addressing these hiccups, and improvements are on the roadmap. Furthermore, there's a GPU functionality feature that is forthcoming, which is an essential improvement and will be included in the next few releases. Customization freedom already exists because it's a community-driven platform. If I could suggest one improvement, it would be regarding containers. While we currently support the orchestration of container hardware or worker nodes, I want to add the ability to control the containers themselves.
CloudStack lacks a billing solution which would complete it as a full 360-degree product. Additionally, more themes and drag-and-drop interfaces could enhance the user experience. Improved documentation separating admin and user parts is needed for easier use.
The product could improve by embracing newer technologies like GPU virtualization.
The product had some limitations. So, I decided to write my own stack from scratch. The product does not have an easily implementable payment gateway. It must provide a payment gateway hook in future releases.
The market keeps changing, and so does technology. I think that container technology in CloudStack is an area that needs to be improved. Regarding container technology, Kubernetes is something many people want to use and something which, as of now, many are using currently. However, there is still room for improvement in Kubernetes, particularly with networking functionality and network virtualization. When it comes to what needs to be improved in CloudStack, I would say that it should stay the way it is currently. It should continue being a stable product that people can rely on since many may be inclined to follow the latest trends and hype, which is not always good for a solution's stability. It is crucial to prioritize stability, which is a key factor that companies seek. In my view, the platform could benefit from adding more metrics. More metrics would offer more insights and data on the platform's performance, utilization, and usage. Overall, I believe that having more metrics available would be highly desirable.
The number of contributors to this solution is relatively small compared to other solutions. However, if more frequent users of CloudStack contribute to the open-source community, it will significantly enhance the overall community experience and make it more useful for everyone involved. There is room for improvement when it comes to maintenance options in CloudStack, particularly with regard to rolling maintenance for multiple Hypervisors. CloudStack does offer this option, but it has not always worked as expected. However, I believe that this largely depends on our expectations for the solution and how we want it to work. As an example, CloudStack maintains a list of Hypervisors where we can host our virtual machines, and we may need to update these Hypervisors on a regular basis, such as every month or every two weeks. Instead of having to perform manual updates, it would be helpful if there were options to automatically perform live migration and update the Hypervisors properly. While there are improvements being made in this area, I believe that there is still some work to be done. Ultimately, the effectiveness of these maintenance options depends on our specific requirements and how we expect the solution to function.
My teammates have complained about the upgrade. The source code had massive files that had to be merged with our own development to upgrade to the latest version of CloudStack. It was quite painful for them. CloudStack could add some cost management tools to give me some control over the costs associated with the number of users of my services.
We recognize that CloudStack is an easy-to-use cloud management platform and, in my opinion, there have been a lot of improvements in the past few years, particular when it comes to the modern UI and overall ease of management. However, I believe that CloudStack needs to grow their marketing in the commercial side. They don't have a great piece of market share right now. For now, we have two versions per year, one being the LTS (Long Term Support) version, and the other is just for development. It's a very good platform for us at the moment, but one feature I would like to see is CloudStack for edge zones. This would enable us to use it for cloud edge computing, as well as enable search providers to use it to provide cloud service in edge zones, for example.
One area that needs improvement is the stability. It is stable, but there are issues. It is related to the lack of support for an open source product. It comes down to needing more active people in the product's open source user community. There are release notes with the product, but I would like to see more documentation. For example, it would be nice to have instructions on how to integrate with DPDK (Data plane developer kit) because it would make it much easier. I would like to see support for native VLAN, and fault-tolerance.
A technology upgrade is one item which could be improved upon a lot.
There are some minor things that can be improved even more such as, perhaps, a bit more polishing on the GUI side to catch up with the API possibilities (which are really extensive) but otherwise nothing critical. New features are being developed daily and the product is constantly improved with new features and bug fixes. Currently, one interesting thing that is being seriously improved is the redundant virtual router capability, which enables zero downtime for customers during certain maintenance operations and cloud version upgrades.