Apache CloudStack vs. Quali CloudShell

Whether our clients are VPS hosting providers or operate private cloud infrastructure for their internal enterprise requirements, CloudStack provides solutions in an easy to implement and operate way that is simple to provide training for. The learning curve for our customesr adopting CloudStack for the management of their cloud infrastructure is shallow, enabling our clients to come up to speed quickly without having to outsource their administrative functions any longer than necessary

• LaaS
• IaaS
• PaaS
• CRaaS
• Training
• DevOps
• DevSecOps
• Demo Portals
• TaaS

Almost any workflow and any infrastructure are supported.

• Low-cost solution
• Open-source
• Engaged community
• Solid documentation
• Is a very reliable tool for orchestration with good usability

Incentivized

• Self service single pane of glass for any workflow and infrastructure
• Complete lifecycle management of your workflow and infrastructure
• Vendor agnostic cloud, service, application, appliance support

• Sometimes you can find undocumented bugs that can compromise the entire infrastructure.
• [If] you don't have an official support channel, you have try to find out the source of the problem by yourself.
• Volume size limitation. Other players allow you to create volumes up to 64TB while ACS allows only 2TB volumes

• Requires SME to get the full ROI first year
• Requires a culture change for Agile Automation
• Price could be less (not cheap)

The tool can automate almost any workflow and infrastructure consumption. It has state of the art develop and support with great online training, online full manual set, and a comprehensive support team and network of SIs/VARS that are very qualified.

The University, my first large implementation, had a big issue with 149 small data centers spread on São Paulo State, this data centers costs to university were very high, the consolidation idea in two data centers were awesome, but were worried with the management, so we adopted ACS to management of all 576 physical hosts. Now a days the university is delivering IaaS for all staff, students, teachers and researchers, they are using these resources to delivery services to their clients and have a great results in research area

VMware is too hard to use, too expensive to support, and not a full lifecycle tool for workflows and Infrastructure (no support of physical either). AWS or Azure or Google solutions are good if you are only in the cloud and only using their tools. Not good if you have on-prem or non-Cloud based tools/infrastructure. Build it yourself automation frameworks can be good for people with unlimited funds, but they are not the best way to go and missing many capabilities typically.

• Low-cost solution (free and open-source)
• More than 2000 users using it simultaneously
• Stable and reliable
• Up and running since 2012

Incentivized

• Our customers have an average ROI of less than 6 months.
• Our customers renew their maintenance almost 100% of the time.
• It has allowed us to build specific solutions across many use cases enabling us to profit.