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.

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.

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

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

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.

We used Morpheus to provide customers with public cloud services.

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.

Morpheus provides multi-cloud functionalities and integration. 

Morpheus is a powerful self-service engine to provide enterprise agility, control, and efficiency. Quickly enable on-prem private clouds, centralize public cloud access, and orchestrate change with cost analytics, governance policy, and automation. Create private clouds, manage public clouds, and consolidate Kubernetes deployment. Provision applications from an on-demand catalog, API/CLI, ITSM, or infrastructure-as-code. Simplify authentication, set policies, and manage security posture.