Morpheus Reviews

My main use cases for Morpheus include self-service provisioning and automation, with one particular set of catalogs for cloud resources across different providers. A standardized blueprint allows us to have approvals, role-based access controls, and workflows. The second use case is from a cloud governance and guardrails standpoint, where we can put quotas on different business units using the platform. We can have a standard tagging methodology implemented and compliance standards in place. Being an MSP, we can have multi-tenant role-based access control. The third use case is hybrid and multi-cloud orchestration, with unified provisioning across AWS, Azure, GCP, and VMware. Finally, from a day-two operations standpoint, the use case is around lifecycle automation, using the platform for automated scaling and decommissioning.

I can give you a specific example of how I've used Morpheus for self-service provisioning and automation. We had a client who was using public and private cloud. We created a set of standardized blueprints using Morpheus as a platform, where end users could log into the platform and provision a two-tier or three-tier application, which is something they used to do on a day-to-day basis. We created standardized blueprint templates where they could log into the platform and provision those virtual machines using self-service provisioning and workflows. We integrated that with the ITSM, so once the request was completed, we could see all of those changes in the ServiceNow platform.

I have something else to add about my main use cases with Morpheus, particularly the integration environment. The built-in connectors to the cloud APIs available in the platform are really helpful because from an end customer standpoint, it does not disrupt their existing ecosystem but integrates with what is present in their environment and provides value-add on top of that.

Morpheus offers several best features. The multi-cloud abstraction layer is definitely one of the best because there is a single pane of glass for all the different cloud providers. You don't need separate tooling in place. Morpheus is an MSP-friendly platform where we can have multi-tenancy, role-based access control, metering, chargeback, and showback. The user interface of the application is really good. Tenants can easily log in and see their specific environment. We can create white labeling for each of the VMs or deployments. The deployments of VMs are made really easy, and the user interface is appreciated by all new users who log into the platform and see the ease of provisioning a new virtual machine with a predefined template.

Out of those features, the one that has had the biggest impact for my team and clients is, from the MSP perspective, definitely the most helpful because, as an MSP ourselves, we handle multiple end customers and clients. Our teams, because they handle multiple customers, didn't have to switch from one platform to another. They could leverage Morpheus and manage their end customers. The second aspect I would point out is the governance and policy engine functionality, where we could leverage quotas, put in a tagging strategy, and security policies in the environment. That really helped. Third, it also helped to decrease manual workflow because we had created different workflows and policies which were all automated. So it highly reduced the day-to-day activities which our operations teams used to conduct.

Morpheus has positively impacted my organization by really helping to reduce provisioning times from days to minutes, which is one of the value-adds we also tell to our customers. Second, it has allowed our MSP teams to compartmentalize the tenants in a secure fashion. Third, it has decreased all manual workflow overhead which our operations team used to feel. Morpheus policy enforcement aspect has been really helpful because it has helped lower operational risk. Finally, it enables self-service workflow without sacrificing control over the different environments.

Morpheus can be improved, particularly from an analytics standpoint. The cost insight feature is really good, but I think advanced FinOps features could be a bit stronger.

I would like to add more about needed improvements and challenges I've experienced with Morpheus, especially around documentation. Documentation can definitely be improved. It would be good to have more blueprint examples which are comprehensive so that users can create complex blueprints and elaborated workflows. Documentation could be improved.

I have been using Morpheus for about two to three years now.

Morpheus is stable, and I can confirm that the platform is quite stable across different clouds, business units, and large environments. We've had no issues at all from a scalability standpoint.

Morpheus's scalability is impressive as it scales very well for hundreds of cloud accounts and thousands of workloads, especially in a multi-tenant MSP operations standpoint. The scalability overall is good.

Morpheus customer support is really good. We've had no issues. In the past, if we required any support from a configuration standpoint or if anything broke, we used to get really quick and easy customer support.

I previously used a different solution, specifically a set of infrastructure as code and manual automation tools along with VMware vRealize Automation.

I switched from those tools to Morpheus because Morpheus provided a mix of governance, multi-cloud abstraction, and automation flexibility without really heavy custom coding capabilities.

My experience with pricing, setup cost, and licensing is that the setup was really smooth. Out of the box provisioning was quite quick. We had advanced workflows available, and we could experiment with them. Self-service catalog creation was really smooth, and the policies and ITSM integration were also smooth because of the vast ecosystem which was already available. From a pricing standpoint, I think that was competitive for an enterprise-grade cloud management platform.

I have seen a return on investment, and I can share relevant metrics with you. For example, the provisioning time of new resources came down by 40 to 50%. There were fewer people required from a manual operations standpoint who would be leveraging day-two lifecycle operations using the platform, probably about 30 to 40% fewer people required. Morpheus return on investment was usually realized within 6 to 12 months.

Before choosing Morpheus, I evaluated other options, including vRealize Automation, Turbonomic, and CloudBolt.

Morpheus advice I would give to others looking into using the product is to focus on building your blueprints one by one. Don't rush into building all of the blueprints. Align your governance and cost reporting as soon as possible in the beginning. Automate your lifecycle events for real cost control. For example, if you're not using a virtual machine or any resource, leverage the decommissioning functionality so that you don't have shadow IT. Also start with a strong tagging and role-based access control policies.

Morpheus is a really good product. Organizations who are using multi or hybrid cloud platforms and looking to scale up their environment and reduce the pressure on the operations team can definitely leverage this. Morpheus is deployed in my organization using a hybrid cloud. I would rate this review an eight out of ten.

My main use case for Morpheus is to create automation scripts, create service catalogs for products, and manage administration or development.

For example, with Morpheus, I can prepare auto-populate fields or automate a series of actions with emails. This is one example of what is possible.

From my perspective, the best feature Morpheus offers is the service catalog.

The service catalog stands out for me because it allows me to prepare or develop something for a client to automate or clearly prepare forms for a client who may not be familiar with more specific details of the product, such as the provision of virtual machines.

In my organization, Morpheus is a very useful tool to automate processes. For example, provisioning new virtual machines reduces the time required, and every action is very fast using Morpheus, allowing me to prepare new environments for testing or proof-of-concept projects.

I think that adding artificial intelligence or a large language model inside Morpheus would be very useful for clients.

I would suggest adding integrated tools such as FinOps or other management tools as improvements to Morpheus.

I have been using Morpheus since I started three years ago.

Morpheus is stable in my experience.

I think that Morpheus's scalability is good. We can start with one node and extend to three nodes as needed.

I have interacted with Morpheus customer support many times, creating new use cases for support and submitting new tickets.

Positive

We were using another tool branded by VMware, but now we are only using Morpheus.

I would rate Morpheus a nine out of ten.

I choose nine out of ten because I think that more plugins or better integration would make it a very powerful tool in the market.

I advise others considering Morpheus to think of it as a tool that helps improve processes and reduces time for operations such as provisioning new virtual machines. It is not the same as tools like Amazon or GCP, but it has many capabilities that allow management from one place instead of continuously switching between multiple public clouds.

We use Morpheus for blueprints, automation, and self-service.

Morpheus is an intuitive solution that is very easy to use. People with less scripting skills or technical skills can still use the solution.

The solution's pricing and customization need to improve. Customization in Morpheus is all set up like a cookie cutter. Although it's got a lot of flexibility, I cannot change the method given by the solution to do something. In CloudBolt, I can go into the back end and make some changes to how the solution does something. That kind of customization is absent in Morpheus.

I have been using Morpheus for two to three years.

I rate Morpheus eight and a half out of ten for stability.

The solution's scalability is pretty good.

I rate Morpheus an eight or nine out of ten for scalability.

If the customer is looking for cost optimization, I prefer CloudBolt over Morpheus.

The solution’s initial setup is easy.

The solution's deployment is very easy and doesn't take much time.

The solution is cheaper if you have less number of servers, but it becomes very expensive for a large number of servers. For example, a customer with more than 50,000 servers recently got excited about what Morpheus does as a solution. However, as soon as they saw the cost, they refused to proceed with the solution.

I am using the latest version of Morpheus.

The solution has got a lot of integrations, and it recently added the capability to build some custom outside of its main tool, whereby you can add on plugins. I would encourage them to build those plugins.

Overall, I rate Morpheus an eight out of ten.

It is our primary cloud management tool. We've implemented it, and it runs in two labs in a production environment. 

We are using its latest version.

We have 40 data centers around the country, and we use Morpheus as a way for people to log in and manage their virtual machines, cloud resources, containers, and just anything that they need to log in to and manage. It supports multitenancy. So, different groups can log in, but they see only their resources. They don't see other groups' resources.

It supports many features, and it also supports some of the automation that Cloudify supports. So, in addition to just giving you basic platform management—such as the ability to deploy virtual machines and have multitenancy to log in and perform all of your basic platform management tasks—it also supports automation. You can, for example, spin up three virtual machines, and you can have each virtual machine configure each other. You can do service chaining with it. You can run scripts in Dash and Python, or you can use tools like Ansible, Puppet, or Chef. All of this is just built into the tool. It is a very powerful tool.

The automation capabilities in Morpheus are just astonishing, and it also supports a lot of third-party integrations out of the box. So, you don't need to write code. If you have a backup solution, such as Avamar, instead of you having to write all of the scripting and coding to make that work, they have plugins. You just install the plugin, and it snaps right into their GUI and works out of the box.

It is very easy to set up, and it is extremely simple to do an upgrade. It is one of the best upgradable solutions I've come across.

The tool could support virtual network functions better. It is really good at doing enterprise-type of things, but one of the things on which we're working with them is loading very complex virtual machines with it, such as Juniper SRX routers. It needs to support more complex virtualized resources a little bit better. Aside from that, it is a terrific tool. We really like it.

We have been using it for about a year. So, it is fairly new.

It is very stable. We haven't had it crash, and we've been running it for a year.

It is absolutely scalable. You can add new cluster nodes to it and scale horizontally. You can also scale vertically if you need to. You can break the database out of it and put it on a different machine. It is very modular.

We have a team of six administrators, and then we probably have 50 customers using it.

They're very good at listening to the feedback and offering us the new features that we need. They are very proactive.

Positive

We pivoted to Morpheus when we realized that Cloudify couldn't meet all of our requirements for cloud management. We had a consultant who came in and mentioned it to us. So, we brought them in and did a proof of concept. We found that it does just about everything we need and more. So, we're now using it as our primary cloud management tool.

It is very easy to set up. Installing it is quite simple. Doing a greenfield install is pretty easy to do, and the upgrade process is also amazingly simple. I've never had an upgrade go wrong.

We have absolutely seen an ROI. We haven't run an extensive business case to distinctly quantify the savings, but the savings have to do with reduced OpEx costs.

The license is based on the number of virtual machines that Morpheus is managing. So, it is a pay-as-you-grow model.

The advice I would give to others is to explore integrations and exercise automation. Its automation capabilities are very good, and it also supports a lot of third-party integrations out of the box. So, you don't need to write code. 

I would rate Morpheus a 10 out of 10.

By utilizing Morpheus as a multi-tenant portal, users can access and interact with their virtual machines, reset them, and connect to them remotely. Moreover, the automation engine allows us to upload playbooks, written in Python, PowerShell, Ruby, and Bash scripts, to carry out desired tasks and generate interesting results.

The number one reason we chose Morpheus over Nutanix Home was that we needed a replacement for the OpenStack Horizon dashboard when we moved off of OpenStack into VMware. We didn't have a license for vRA and vCloud Director. It was expensive. So we wound up choosing Morpheus for that. And what that allows us to do, allows us to take different groups within our organization, the groups can come to us and say, we want to deploy fifty virtual machines, for example. We can provision that group, and set some policies on that group. And then once they log in, they can have varying degrees of self-service that we can allow for them so that they can deploy virtual machines, tare them down, and reconfigure them. We generally take care of the networking. We have NSXT as the networking SDN, So we take care of all the networking requirements for everybody, but they can log in and plug their virtual machines into various networks, they can restart them, console into them, and deploy new VMs if they want to. They can add or reduce the CPUs, and memory. They can run automation on all their workloads. There's a workflow engine within the solution that allows us to run automation at various points within the life cycle of a machine. And it also has a future-proof capability of running clusters, so we can deploy Kubernetes clusters, but there are other kinds of clusters that are also supported. We can deploy these clusters and then deploy containerized workloads into Morpheus if we so choose to gravitate toward that aspect of our deployments. Other than a couple of test cases that we've created, we don't have anybody deploying any containers into Morpheus at the moment. What our group is responsible for is deploying firewalls, routers, and networking workloads. These are the very last to containerize because they're very difficult to containerize.

The user interface of the application is exceptional. Tenants can easily log in and see their sandbox, with different logos for each VM. Deployment of virtual machines is made easy and the user interface is highly praised by all those who use it. Multi-tenancy, or the ability to sandbox or partition various user groups, was the primary basis for selecting this application.

The upgrades are seamless.

We've been facing some challenges with Morpheus due to its design for public cloud usage. Their main focus is on allowing customers to deploy virtual machines to Azure, Google Cloud, AWS (and other private or public clouds they support). They provide features such as guidance and cost optimization. However, we're using Morpheus for on-prem v center clouds, which is probably not the user base norm. We are very pleased with the dashboard and multi-tenancy capabilities, but there are some challenges when deploying and configuring the more complex Telco workloads that have advanced networking.

The integration of the NSX-T needs to be refactored. As I have been working on the API, there are some issues with the workflow engine in the automation that need to be addressed. For example, I need to be able to flag a task as fail or continue on fail if something goes wrong in the workflow. Currently, if one of the tasks in a twenty-task workflow fails, the remaining nineteen are not run, which can be a problem if one of those tasks is critical, such as when patching or doing security tasks. Thus, workflow enhancements and improvements are necessary. Morpheus desires the ability to control the full life cycle of a virtual machine from beginning to end. We have many vendors who want to establish virtual machines, but we want users to access them through Morpheus. We want the VMs to be provisioned from an external system and then be managed in Morpheus so users can only perform limited activities without being able to delete or provision them. We are currently working on resolving this issue, which I refer to as reconciliation. I have asked the developers to implement multi-tenancy, where each tenant has their own landing page at a unique URL. However, we are using groups, not tenants, so there are features we can do with tenants that we cannot do with groups. Specifically, I am trying to get the developers to add notifications support so that when a group member logs in to the Morpheus portal, they can be informed of their VMs' maintenance schedule at a specific time. This is a feature I have requested them to add. We are generally pleased with Morpheus, however, due to some restraints and restrictions, we are utilizing it differently than the majority of its users. This creates some difficulty.

We are currently using the solution.

I have not had any upgrades that have gone bad, and I run a cluster system too. The cluster has only gone down once or twice in the two-year period that I've been running Morpheus. The solution is rock solid. I give the stability a nine out of ten.

The vendor uses Percona for the database clustering so we better know what we're doing with that if that were to get corrupted, but that hasn't happened for us. The proxy we are running in front of Morpheus is carrier-grade, and it's gone down before Morpheus has. The solution is very resilient and solid, but it takes an enormous amount of memory and resources to run Morpheus. Those Morpheus servers get busy, and we keep adding more CPU and RAM to them. And we're not even running a lot of workloads yet. So that's something that I'm looking at.

I cannot rate the scalability of this solution high as they are already running busy and we have yet to run any workloads. I give the scalability a seven out of ten.

We have 100 people using the solution.

The Morpheus development team has been incredibly helpful and responsive to our requests. We are able to quickly let them know when we run into a problem, and they make an effort to resolve it as soon as possible.

Positive

We were using OpenStack previously, and we were looking for a replacement for the OpenStack Horizon Dashboard.

I give the initial setup a ten out of ten. The documentation is perfect. Everything is tested before we deploy. 

Installing and configuring a single deployment may take up to half a day while setting up and verifying a cluster could take a full day. This includes utilizing the graphical user interface to adjust settings and ensure that everything is working correctly.

The deployment requires four people. We have one person who is great at networking, another who is highly skilled in servers and storage, a third who is a VMware specialist, and then I'm the dev ops specialist who integrates it all together.

The implementation is completed in-house and I do all the configuration, administration, and even the coding and automation too.

We are currently in negotiations with the vendor regarding the pricing model, which is based on the number of inventory nodes, including those that are not running and containers/pods. Initially, the license may seem like a good deal, but as we grow, it becomes costly. For instance, with the cloud, we don't want to include inventory in our license as it would be too expensive.

At first, Morpheus was a more cost-efficient option than VMware VRA. However, as we continue to add new hypervisors and virtual machines, the advantages of using VMware VRA have become more pronounced. I am not keen on switching to VRA as I don't want to have to grapple with many of the complexities associated with PowerShell scripting and I feel that we already have too much VMware in our shop. I'm advocating against my organization utilizing VRA, as they are currently in negotiations with Morpheus regarding licensing costs. If they are unable to reach agreeable terms, they may find the expense of using VRA to be too great. Now, as part of the negotiations, we are not utilizing many of the advanced features Morpheus has to offer. As we know, Morpheus works best when there is a large number of workloads to be put into the public cloud. This is what the vendor is hoping for, as their primary objective is to reduce costs by utilizing their guidance feature and cost optimization algorithms. We will not be doing this, however; we will simply use Morpheus as a portal for an on-prem v center based on the on-prem cloud system. For us, it's mainly a portal with some automation, which is part of the talks we're having with potential customers. People who like to buy telcos typically want references, so we have to have a different model than those who are offering managed cloud services.

We initially explored Cloudify and Nutanix, but Cloudify was more of an automated provisioning tool and not a full-scale tenant environment (we felt). We liked the Morpheus UI and Automation capabilities, and it provided that one-stop-shop user-friendly portal that allowed users to interact with their virtual machine environment. The fact that Morpheus supported Kubernetes and Containers was also a plus, as it gave us a future-proof path for Cloud Native.

I give the solution an eight out of ten.

Users need to have a clear understanding of which clouds they are connecting to and their network requirements.

We used Morpheus to provide customers with public cloud services.

The most valuable feature of Morpheus is its strong integration with vSphere Cloud.

There is room for improvement in the user interface, which is complicated and not very user-friendly, particularly for non-tech-savvy users like customers. Additionally, there is room for enhancement in integrating Morpheus with other solutions. For the next Morpheus release, I would like to see more options for managing deployed virtual machines, such as additional features like ISO detection and better handling of copy-paste functionality. The current console interface can be challenging, especially when dealing with tasks like opening a console or entering passwords.

I have used Morpheus for a year.

I would rate the stability of the solution as a six out of ten.

I would rate the scalability of the solution as a six out of ten.

I would rate the technical support of Morpheus as a seven out of ten.

Neutral

Deploying Morpheus was straightforward. 

The pricing of Morpheus is fair.

For those evaluating Morpheus, my advice is to thoroughly research its suitability for your specific needs and consider how well it integrates with your existing solutions. Pay attention to potential challenges in integration, and ensure it aligns with your overall requirements. Overall, I would rate Morpheus as a six out of ten.

Morpheus is a cloud management platform with a lot of feature sets. It can provision almost any cloud features you can think of. 

Morpheus is an application-centric product, they are very good with the orchestration of hardware. When I use Morpheus, I do not need OCI or Cisco's orchestrate on top of Cisco hardware. Sometimes, I don't need specific top-of-the-rack switches, which are generally required in a legacy network. If I can build a software-defined network, I can provision it to Morpheus.

Morpheus is also good with other features that they mention in their documentation. 

Before we started using Morpheus, we faced an issue with its statements on the website. It claimed that Morpheus works with Huawei and some other clouds, which turned out to be slightly misleading. Although Morpheus worked with the Huawei public cloud, it was unable to work with Huawei's private cloud. When we dug deeper, we realized that the problem was on Huawei's side, not on Morpheus's side. Nevertheless, the statement was slightly misleading. 

We worked back and forth with Morpheus to resolve the issue, but Morpheus was not able to provide any support. None of their partners anywhere in the world have any kind of resolution or support for this issue because Pakistan, especially in this zone, is deeply embedded with Huawei products. You cannot discount the amount of equipment, storage, and already pre-installed network, which is worth around fifteen million dollars. You can't put that on a site and build a completely new Greenfield infrastructure for any cloud. It's a new, preexisting IT market. However, we did find a solution with Morpheus, which can work. But Morpheus was very resistant to the idea, even if it was their product. We have a lot of engineers sitting in Pakistan, developing Morpheus and working with Morpheus. We found a solution and notified Multi Assessment that this issue could be resolved by working with Morpheus and Huawei just like it works with VMware or other clouds. 

Unfortunately, we did not get a very positive or happy response from our peers about including this product in their range as well.

When you approach support, they may not be able to support these products. Although Morpheus's technical engineers say that they can support these products because they have worked with them, the support issues are that they cannot. 

So that was very strange for us to realize that Morpheus support may be lacking the resource tools that they should have. We now have almost the same number of certified engineers in Pakistan working with us as the number claimed by Morpheus to have - a hundred certified developers. Maybe that is why we reached that conclusion very quickly. But this is an issue we faced - that Morpheus's support may have been unwilling or unable.

There were limitations in their knowledge level when it came to purely technical support and understanding of the whole solution as a cost-effective one.

They were unable to guide you on how to use the maximum resources with minimum input. Because every end-user wants that, they don't want to buy licenses that are not needed. But Morpheus was unable to support in that case. Although they have documented it on their website, it is still very difficult for Morpheus support to provide you with any such guidance. You have to be very vigilant and resourceful and learn about Morpheus to do that kind of thing. Otherwise, you will always be used either under or over resources.

I don't think that Morpheus is heading in a very positive direction. Morpheus is deteriorating gradually day by day. However, the product is improving with every new version. Many changes are being made, which are bringing in support and help. The product could improve its own marketplace by reviewing its policy of Huawei. Huawei is already deployed in some parts of the bank's infrastructure in Pakistan, and it will be a private or hybrid cloud. We cannot take that out of the equation. We have found a resolution to work with that. However, this private cloud is also open source. The whole Huawei private cloud version is open source. They all have the same bug, which is causing all the problems for every OEM that does not support Huawei's private cloud. Huawei public cloud is okay with them. 

If Morpheus can understand that this bug exists and we have to work around it, there will be a huge market, including the number of users in Hong Kong, India, the Middle East, or Pakistan. If this bug can be resolved or acknowledged, and the way we have resolved it, we have put a solution to that, and it is also Morpheus. We have orchestrated Morpheus in a way that it started working around that part, and now it is working. Even the bank is satisfied that if Morpheus doesn't come for support for this, we have local engineers, and they will continue providing it. That's why they are going for an RSP, which might be 10,000 to 20,000 instances or more safe licenses, which is a good number. I do believe that Morpheus will be very happy once they see that the product specification mostly revolves around their solution. The required specification, although Flexera will be just as good to code in, Flexera doesn't have the right level of partners here in Pakistan. They will face the challenge that they might not be technically suitable to deploy at this time because we acquired a Morpheus partnership, but we did not get similar platinum partners for our partnership from Flexera. We are unable to get discounts for the OEMs, and the end-users cannot ask us to provide them with these tier one or tier two principal support. If Flexera comes in directly to participate, it is even better for the bank because then the OEMs will be responsible for everything themselves. We looked at all these things and found that without partners, Morpheus cannot survive. 

Morpheus has enabled its partners more than other OEMs. However, its support and documentation on the website regarding the version are quite good. But when you ask the same question from the support, it is terrible. They can make it easier for the end-user to understand the documentation because, at some levels, it is difficult to understand for the first-time user or for the normal end-user, not very technical.

It's just been one year, a little less than one year actually, as for overall. We have a few deployments of Morpheus, and they are being tested. Some of them are licensed, and some are used as open source, which provides like 25 instances or 22 instances, or something like that. But those are just test cases in the small university block or campuses. Students working on them, we provide them with training and access as well. 

The last version we deployed was 5.1.2. That was the version we had acquired a license for and used to build the demo cloud.

We keep in connection with Morpheus about stability. They always advise us to keep one step behind the latest version for increased stability, and it has been stable. However, we only have one year of experience in a specific environment, and it has not been thoroughly tested or load tested as a public cloud. It is not being provisioned publicly, so we can't predict what we will face when the World Bank opens it up for 43 or 44 million students. We have no idea what will happen when 44 million students are concurrently working on it, thinking from their own heads and doing things we did not expect. The stability will be tested then. Currently, it is not being load tested like that, and it has been good for us so far.

For now, the stability is very good, definitely an A+. I would rate it a nine out of ten. We haven't had a single crash, so it's very stable for us. However, we haven't tested it with the whole user base. But so far, we have done a lot of intensive testing, and the release version is very limited.

Morpheus is scalable. It provides options for both upscaling and down-scaling. Morpheus provides a feature where you can buy a limited number of licenses and upscale from there as long as you want. And when you stop using them, they reduce it, and it doesn't create a problem. But then the support issue comes in. If you're using one thousand licenses and managing everything with just a little bit of human effort, getting good Morpheus support might not be easy. 

However, when you buy a lot of licenses, they provide support, and sometimes you don't need support because everything and every instance are already documented and part of a provisioning platform. 

So I can probably say that Morpheus, in that case, becomes easier to use for the end-user with a slightly additional cost. But scaling up and down on Morpheus is very simple. Morpheus provides a very easy and one-click solution to scaling up and down. Scalability is a ten. It's very good, and I'm absolutely happy with it. I can't be happier, so it's ten out of ten for scalability. It's just perfect.

The customer service and support team is good but you have to push for it. When you buy a good number of licenses, Morpheus provides very good support. But when you are using it on a smaller scale when you are not a corporate or big customer with Fort Knox, and using only less than one thousand licenses or something like that, then Morpheus does provide support, but it is slightly harder to get.

Morpheus is very, very good in some cases, but the support is far away and comes from Asia Pacific Australia. There could be some second language barrier because Austrians speak English, and a lot of Pakistanis sometimes are not too good with the English language. The second thing would be that the Australian accent is much stronger than the general English accent, which people in Pakistan would understand. Maybe that is one part of the support we have seen create an issue because you need an English translator when you're working with the Australian. In the longer run, I even recommended Morpheus because now they have more than a hundred certified Morpheus engineers and office administrators. So we built a resource pool as well. Because there was a language barrier. English is a second language, which may have caused difficulties in understanding each other. They had good technical knowledge, but overall not so good. 

Neutral

The initial setup is very easy. Even someone with very basic technical knowledge can start using it. It's not difficult at all. It would have been slightly difficult if we were not the technical guys in the right domain. I would rate it a nine out of ten because of the lack of support that becomes a part of it when you're doing the initial setup. So I can't say it's easy to set up, especially if you're not too technical in the right kind of technology.

It only took us two days to deploy the solution entirely. Actually, it was initially a very green field on which it was deployed. So it didn't take very long. And once it was deployed, then it took a long time to fine-tune it with the brownfield. The reason was that we were unable to decide what to use and what not to use. Once it was deployed and we integrated it with the Brownfield, we found out that there were so many instances that we had forgotten about for years because the Brownfield had been running up and running for years. And hundreds of thousands of virtual machines were useless, not working, probably not needed, or duplicated. So those were found and eliminated, and it took a long time to fine-tune. It will still take a long time because every day, a student creates one instance, then creates another instance, forgets about the first instance, or something goes wrong. And because the student is provided with the facility, it's not too costly. So universities usually let the students do some work on it. They create multiple instances, three of which are not being used for three months, and only one is being used. We keep those resources a lot, so Morpheus can find that, but tuning is always needed. 

You have to do a manual intervention and keep looking as an administrator at what is happening with the cloud underneath. Otherwise, Morpheus doesn't take too long. It takes a very short time if it's a very green field.

Initially, there were just four engineers who were able to understand Morpheus. However, we have now increased the number to more than a hundred engineers. It's worth noting that the team of engineers who initially worked on the sizing of the infrastructure and virtualization were separate from us. They had already provided us with the input of everything we needed, such as the virtual environment, integration requirements, functionality, and what would eventually be provisioned. If we had to do that work ourselves, it would take a long time. It's a long process, approximately six months.

Although we have trained a lot of office engineers. Currently, just two of them are looking after maintenance. We are not facing any issues, which proves that maintenance is not a very intensive job and can be managed easily.

Currently, we are building a hybrid cloud that will function as a private cloud for education. It will be based on the Pakistan Education Research Network and serve 300 universities. On top of this, it will be integrated with different virtual environments like Azure, Google, AWS, and Huawei, so all its services will be available to students and faculty.

Therefore, there were a lot of silos. It is quite a complicated setup because each university has almost 50 campuses, and all of them need to be brought into one common cloud with its financials and backfilling. 

A very good thing about Morpheus is the back billing. Morpheus provides an extensive back billing solution to help with the integrated final billing solution. We integrated it capably, and it is functioning very efficiently. It is working great.

We are using it with every cloud provider. For example, only the computation might be done on Azure, and the storage and everything will be done locally. So there will be a lot of cost savings from both ends and an advantage of technology. Whatever is available locally will be provisioned from here, and what is not available locally will be provided from out there. High-performance computing was made a part of it. So when the students require very compute-intensive jobs, like GIS, they can do it on the cloud, Oracle Cloud, or the local resident cloud. It's a very promising and good thing appearing now as time passes.

Morpheus has a very flexible pricing structure. With our X solution, Morpheus cuts down the price of any other cloud by two or three hundred times when compared to VMware Cloud because we can provision the cloud from vCenter without needing vCloud foundation or director, which are expensive licenses. Morpheus licenses can cost from two to ten dollars, depending on various factors like the number of cloud instances. When the number of instances is low, it can be expensive, but when it's high, it becomes very lucrative. It overall cuts millions of dollars out of the equation. So, the license cost is not too much, around two or three dollars a month, or ten dollars a month maximum. For a new user who doesn't want to use more than a hundred licenses, that could be the price. But even with that, Morpheus still cuts down the cost of other licenses that are not needed because of CMP, which is huge. So, I think it's good enough.

You can get a license on a monthly basis as well. Basically, they go for a year contract. But when we have worked on separate models with them, we have told them that World Bank is not a very common end-user, and they might need the licenses for that very week or that very day and not ever again. So how would you license or how would you provision them? So they can provide it for a very short time as well. They can provide it for thirty days, and the number of days you can even be less than that. I know because I have worked with the license portal myself as well. However, as a policy, I don't think they go beyond and beyond the minimum threshold of the license time. But Morpheus can do it because it also has a minute's license-providing capability. So they can even provide you with in minutes.

I would rate the pricing model a four out of ten, with ten being the most expensive and one being the least expensive.

Overall, I'd rate it as an eight. It's a good product and provides a good overall experience. However, we had to put in much effort ourselves since Morpheus's support wasn't always available to help us.

I recommend that a new user have at least two or three certified resources in-house since it can sometimes be difficult to get support from Morpheus, especially if you don't have a strong technical team. If you need support and Morpheus support isn't available for a few days, it can cause problems.

We use Morpheus for the heavy lifting in building curated marketplaces for MSPs, delivering a hybrid solution to their clients. Imagine a single marketplace that can deliver any product into any infrastructure, public or private.

We don't use it for DevOps automation. We use it for API integration with public cloud vendors. If they've already done the API integration with AWS, for example, then we use their APIs instead of doing our own.

The most beneficial features for us were the API integrations with various cloud vendors like Nutanix, VMware, AWS, Azure, and GCP. It saved us the effort of doing that work ourselves. 

However, 95% of the products developed since 2017 has not really been of value to us.  For example, we don't use the self-service catalog. We build a different catalog that sits on top of it. So, we don't really use the product for what it's designed for today.

Moreover, multi-cloud integration is not relevant to our IT strategy. We are 100% AWS and don't have a multi-cloud strategy ourselves. However, we're aware that mid to large corporates have a multicloud, hybrid strategy, which is why we developed a product.

The product has become overly complex. The biggest problem is that we find a bug, they fix the bug, but then another one pops up. We can never really deliver on the vision we had using Morpheus.

We had issues with the Jupiter service plan in Azure, which made us unable to use Azure. 

So, we waited for them to fix the bug, but then they fix that bug, and we have another bug with NSX-T (since people shifted from NSX-B). Then, to make things even better, AWS changed their APIs, which broke our Morpheus integration and stopped us from provisioning into AWS. 

We just seem to be constantly chasing our tails. We fix one bug, and then another appears. Eventually, you just say, "Okay, I won't use NSX-T, I won't use Azure, I won't use AWS," and at that point, you effectively have a broken product.

I have been using this solution since 2015. 

Stability is a big challenge. I can't make everything work. I've been working with Morpheus for about nine years, feeling like a beta tester the entire time. 

The problem is the abstraction layer Morpheus sits on has many moving parts. Their biggest challenge is maintaining these parts to effectively deliver the solution, which is where they struggle.

Morpheus as a product is scalable, but the scalability comes from the infrastructure vendor. The software itself is indifferent; it's designed to scale based on memory, compute, and storage needs. However, scaling the product from a usability perspective presents challenges.

We work with all types of customers, mainly targeting MSPs. So, it really depends on the MSP's target market.

The customer service and support are good. 

Positive

Other products I've worked with were standalone within their solutions. Morpheus aims to be the central point or the abstraction layer for all cloud services.

So, I have not used anything as heavily integrated as Morpheus.

The complexity of the deployment depends on the deployment method. A single instance is fairly simple, but a cluster is much more complex. 

However, deploying the application is not the difficult part.

Since we build on AWS, it's relatively easy to maintain. The main issue is the admin UI, which is very different from standard admin dashboards. 

So, you need to have a lot of experience to be able to navigate the dashboard And as they've layered on more and more features within the product, you've got more and more complexity.

Morpheus doesn't directly support cost optimization, but its API integration can facilitate resource optimization. It doesn't dynamically optimize resources like an aeronautic system would; it operates step by step. 

Morpheus is more of a cloud ops product rather than a FinOps product.

We've been a Morpheus customer since the early days. I know what they're trying to sell now, and you'd really need a strong use case to justify the cost.

From what we were trying to use it for, or what we are trying to use it for, I would rate the solution a six out of ten.

If you are an end client looking for a limited subset of what we're trying to use it for, it's probably going to be higher. 

This is half the battle. They've got a developer-led strategy, which is not in the right direction. They're building complexity in the product, and we're not even off first base yet. 

If you can't provision into AWS, then you're not even off first base, so there's no point in that. I would rather see stability with the core functionality than keep adding features that I don't need.

The cloud-integration and user administration are my primary use cases. I have used the system to set up the cloud and envision VMware and AWS.

I was the only one using the product at my company.

The most valuable feature for me was cost optimization. We could check and get alerts if we should downsize or upsize it.

Another feature I like is that we can use multiple cloud services simultaneously. The way we can use it as a catalogue makes it very accessible and user-friendly. The overall experience of using Morpheous was very smooth.

I faced a few problems while deploying or provisioning AWS because there were several fields that I needed to fill in, which I couldn’t figure out. I didn’t know what to fill in it, and sometimes I didn’t have access to the fields. They could have provided a suggestion or documentation for the initial setup process.

I have worked with Morpheus data management for four months, from April 2022 to July 2022. I used the public cloud version.

I have not faced any issues with the stability of this solution.

The product is scalable.

I did not escalate any questions to the service and support team.

I have not worked with any other product that offers the same features as managing multiple cloud software on the same platform, whether private or public.

The initial setup was complex.

One must know the concepts of cloud before jumping into Morpheus. Otherwise, it will be a complicated process. I will rate it an eight out of ten.

Morpheus provides multi-cloud functionalities and integration. 

I like the flexibility of Morpheus; the agent, the automation, and the API-based integration. Morpheus can integrate the API of other platforms and it also provides an automation platform. The solution has good support for VMware, Center, and SIS with a multi-tenant panel. 

The service is limited and somewhat lacking. Integration is good but to make it work requires an added level of understanding that takes time to learn and is quite complex. You can switch on everything and do it all at the administrator level, but if you're providing it for a customer, it requires segregation which makes it more difficult. You have to be a Morpheus administrator for that and there is a learning curve involved. The GUI should be more user-friendly. 

I've been using this solution for a couple of months. 

The solution is very stable.

Morpheus is very scalable because it can be distributed on the service level. Dashboard services can be created on an individual server and that is scalable. Also, the infrastructure can be scaled in various ways.

There is a learning curve with the setup if you're dealing with multiple nodes and so we had Morpheus do that for us. If there's just a single server the setup is very easy. The deployment took two or three days. If everything from the infrastructure level is ready to go, then one person is enough to set up. They have good documentation for that. 

It's a great platform, but there is a steep learning curve that requires an understanding of the target platform and the GUI. 

I'm deducting two points for the GUI and rate this solution eight out of 10.