Try our new research platform with insights from 80,000+ expert users

Cloudify vs IBM Turbonomic comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Cloudify
Ranking in Cloud Management
35th
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
12
Ranking in other categories
No ranking in other categories
IBM Turbonomic
Ranking in Cloud Management
4th
Average Rating
8.8
Reviews Sentiment
7.4
Number of Reviews
205
Ranking in other categories
Cloud Migration (5th), Virtualization Management Tools (5th), IT Financial Management (1st), IT Operations Analytics (11th), Cloud Analytics (1st), Cloud Cost Management (1st), AIOps (15th)
 

Mindshare comparison

As of March 2026, in the Cloud Management category, the mindshare of Cloudify is 1.6%, down from 1.7% compared to the previous year. The mindshare of IBM Turbonomic is 4.1%, down from 5.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Management Mindshare Distribution
ProductMindshare (%)
IBM Turbonomic4.1%
Cloudify1.6%
Other94.3%
Cloud Management
 

Featured Reviews

Mark Wittling - PeerSpot reviewer
Cloud Architect at Cox communications
Works very well for advanced service chaining requirements and has extremely advanced engineers for support
We had a manager who thought that Cloudify could be used as a replacement for Horizon in OpenStack, but we found that Cloudify lacked the user interface or GUI for doing multitenancy and basic platform management tasks. Cloudify was really good at launching, for example, firewalls and configuring them and doing service chaining and rather advanced things like that, but it didn't meet the requirements for a basic platform management solution. It is something that seems to work better as a bolt-on or an augmented solution. It is a bit mis-marketed as a Cloud Management solution. It is not that. It is more of a service orchestration and automation tool. It is very good at doing that, but it fails to meet basic platform management requirements. Once you have it running, you can't really do anything with it without writing code and scripts. It requires a full-time DevOps person to use it. We deployed a Palo Alto firewall with it. That's basically what the project was for us, and it worked flawlessly once we got it finished, but it took another 12 weeks to get all of the automation and everything else coded, tested, and working. There is certainly a place for this technology, but when we got rid of OpenStack and moved to VMware, we either had to go with the vRealize Automation Suite to do this kind of automation, or we had to find an alternative solution to manage the private cloud. So, we put Cloudify in, but we really couldn't find it useful for basic platform administration tasks.
reviewer1446966 - PeerSpot reviewer
Senior Systems Engineer at a university with 1,001-5,000 employees
The solution reduced our operational expenditures and is able to identify points before we even noticed them
The management interface seems to be designed for high-resolution screens. Somebody with a smaller-resolution screen might not like the web interface. I run a 4K monitor on it, so everything fits on the screen. With a lower resolution like 1080, you need to scroll a lot. Everything is in smaller windows. It doesn't seem to be designed for smaller screens. When I change the resolution to 1080, I only see half of what I would on my big 4K monitor. It would be annoying to have to scroll to see the flow chart. They have a flow chart that goes top to bottom like a tree. On a lower resolution, it might be nice if that scrolls horizontally because it's long, narrow, and tall. It's only three icons wide, but it's 15 icons tall. I think it would be helpful to have the ability to change that for a smaller screen and customize the widget.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It enables a single platform to communicate with the entire infrastructure."
"Cloudify works in cases where you have very advanced service chaining requirements. It really works well there, and it fits the best. They have a standardized markup that's based on TOSCA, which is a standard. I like the fact that they're standards-based. Their solution works extremely well if you have the talent and the manpower to write TOSCA descriptors to deploy and interchange services or to automate the configuration and turn up of services."
"Valuable features are auto-scaling and load balancing."
"Cloudify provides the infrastructure-as-code, as well as operational action capabilities (orchestrated startups or upgrades, and more)."
"Extensible internal functions and plugins. Can implement custom plugins to fit your scenario. Python based plugins."
"You can use only what you need. You can remove certain Cloudify functions from the framework to create a "minified" version of what you need. This might only consist of the messaging delivery system, and the orchestration functions."
"Product has given us the ability to catch early scaling issues that many companies hit on with private clouds."
"TOSCA model allows modeling the application rather than the automation. It is a machine-readable representation of the application and its infrastructure, which can be used for other things too, not just for the orchestration (e.g. enterprise architecture big picture, who connects to whom)."
"In our organization, optimizing application performance is a continuous process that is beyond human scale. We would not be able to do the number of actions that Turbonomic takes on a daily, weekly, and monthly basis. It is humanly impossible with the little micro adjustments that it can make. That is a huge differentiator. If you just figure each action could take anywhere very conservatively from five to 10 minutes to act upon, then you multiply that out by thousands of actions every month, it is easily something where you could say, "I am saving a couple of FTEs.""
"Rightsizing is valuable. Its recommendations are pretty good."
"With over 2500 ESX VMs, including 1500+ XenDesktop VDI desktops, hosted over two datacentres and 80+ vSphere hosts, firefighting has become something of the past."
"My favorite part of the solution is the automation scheduling. Being able to choose when actions happen, and how they happen..."
"The most valuable features are the cluster utilization reports and the resource capacity planning. We can simulate how much capacity we can add to the current resources. The individual DM reports and VM-facing recommendations report are also helpful."
"Using this product helps us to reduce performance risk because it shows us where resources are needed but not yet allocated."
"The tool provides the ability to look at the consumption utilization over a period of time and determine if we need to change that resource allocation based on the actual workload consumption, as opposed to how IT has configured it. Therefore, we have come to realize that a lot of our workloads are overprovisioned, and we are spending more money in the public cloud than we need to."
"The ability to monitor and automate both the right-sizing of VMs as well as to automate the vMotion of VMs across ESXi hosts."
 

Cons

"Install of the product itself could be improved and I would like to see better event monitoring."
"Certainly the UI could use some intensive work, but nevertheless, overall, it’s a complete product with its 3.4 version and much better features are available with 4.0."
"Unlike the Docker environment, Cloudify takes time for configuration and its learning curve."
"It lacked the user interface for multitenancy and basic platform management tasks. It is a leader in the niche area that they like to perform in, but it only does about 30% of top-tier advanced functions of platform management. It doesn't meet about 70% of what you need to manage a private cloud platform."
"The solution is a bit of a headache because mistakes happen in the blueprint every time we deploy and they require modifications."
"The upgrading process could be simplified."
"Error handling could be improved; GUI is lacking with respect to user privileges and connectivity."
"Before IBM bought it, the support was fantastic. After IBM bought it, the support became very disappointing."
"The management interface seems to be designed for high-resolution screens. Somebody with a smaller-resolution screen might not like the web interface. I run a 4K monitor on it, so everything fits on the screen. With a lower resolution like 1080, you need to scroll a lot. Everything is in smaller windows. It doesn't seem to be designed for smaller screens."
"The reporting needs to be improved. It's important for us to know and be able to look back on what happened and why certain decisions were made, and we want to use a custom report for this."
"The implementation could be enhanced."
"The planning and costing areas could be a little bit more detailed. When you have more than 2,000 machines, the reports don't work properly. They need to fix it so that the reports work when you use that many virtual machines."
"It would be good for Turbonomic, on their side, to integrate with other companies like AppDynamics or SolarWinds or other monitoring softwares. I feel that the actual monitoring of applications, mixed in with their abilities, would help. That would be the case wherever Turbonomic lacks the ability to monitor an application or in cases where applications are so customized that it's not going to be able to handle them. There is monitoring that you can do with scripting that you may not be able to do with Turbonomic."
"The old interface was not the clearest UI in some areas, and could be quite intimidating when first using the tool."
"There is an opportunity for improvement with some of Turbonomic's permissions internally for role-based access control. We would like the ability to come up with some customized permissions or scope permissions a bit differently than the product provides."
 

Pricing and Cost Advice

"I wasn't involved in the pricing of it because we were just doing prototype work with it, but I was told by the upper management team that it was quite expensive. That was another reason we switched to Morpheus."
"Licensing is per socket, so load up on the cores rather than a lot of lower core CPUs."
"I consider the pricing to be high."
"You should understand the cost of your physical servers and how much time and money you are spending year over year on expanding your virtual farm."
"It is an endpoint type license, which is fine. It is not overly expensive."
"I don't know the current prices, but I like how the licensing is based on the number of instances instead of sockets, clusters, or cores. We have some VMs that are so heavy I can only fit four on one server. It's not cost-effective if we have to pay more for those. When I move around a VM SQL box with 30 cores and a half-terabyte of RAM, I'm not paying for an entire socket and cores where people assume you have at least 10 or 20 VMs on that socket for that pricing."
"IBM Turbonomic is an investment that we believe will deliver positive returns."
"It was an annual buy-in. You basically purchase it based on your host type stuff. The buy-in was about 20K, and the annual maintenance is about $3,000 a year."
"I know there have been some issues with the billing, when the numbers were first proposed, as to how much we would save. There was a huge miscommunication on our part. Turbonomic was led to believe that we could optimize our AWS footprint, because we didn't know we couldn't. So, we were promised savings of $750,000. Then, when we came to implement Turbonomic, the developers in AWS said, "Absolutely not. You're not putting that in our environment. We can't scale down anything because they coded it." Our AWS environment is a legacy environment. It has all these old applications, where all the developers who have made it are no longer with the company. Those applications generate a ton of money for us. So, if one breaks, we are really in trouble and they didn't want to have to deal with an environment that was changing and couldn't be supported. That number went from $750,000 to about $450,000. However, that wasn't Turbonomic's fault."
report
Use our free recommendation engine to learn which Cloud Management solutions are best for your needs.
883,692 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
13%
Comms Service Provider
8%
Performing Arts
8%
Financial Services Firm
6%
Financial Services Firm
10%
Computer Software Company
10%
Manufacturing Company
9%
Insurance Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Large Enterprise6
By reviewers
Company SizeCount
Small Business41
Midsize Enterprise57
Large Enterprise147
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Turbonomic?
It offers different scenarios. It provides more capabilities than many other tools available. Typically, its price is set as a percentage of the consumption of some of our customers' services. The ...
What needs improvement with Turbonomic?
The implementation could be enhanced.
What is your primary use case for Turbonomic?
We use IBM Turbonomic to automate our cloud operations, including monitoring, consolidating dashboards, and reporting. This helps us get a consolidated view of all customer spending into a single d...
 

Also Known As

No data available
Turbonomic, VMTurbo Operations Manager
 

Interactive Demo

Demo not available
 

Overview

 

Sample Customers

Proximus Partner Communications (Israel) VMware NTT Data Metaswitch Spirent Communications Lumina Networks Atos Fortinet
IBM, J.B. Hunt, BBC, The Capita Group, SulAmérica, Rabobank, PROS, ThinkON, O.C. Tanner Co.
Find out what your peers are saying about Cloudify vs. IBM Turbonomic and other solutions. Updated: March 2026.
883,692 professionals have used our research since 2012.