HPE Morpheus Enterprise

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.

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 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.

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.

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.

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.

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.