---
# source: src/content/solutions/en/morpheus.md
# route:  /en/solutions/morpheus/
title: Morpheus
tags: [cloud, automation, devops]
vendors: [morpheus]
summary: A self-service layer across several platforms. Development teams order, operations keeps hold of policy and cost.
photoNeed: The Morpheus self-service catalogue on screen, with someone provisioning from it
stub: false
draft: false
kind: product
addon: false
vendorName: Morpheus Enterprise
status: current
practice: >
  Draft, not yet reviewed. The value nearly always shows up on the second use case rather than the first. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that is close to free.
practiceReview: true
---

## What it is

Morpheus puts an ordering and management layer over the platforms already in place.
vSphere, a hyperscaler and Kubernetes appear in the same catalogue. What a team may
order, how it gets named and what it costs are defined once.

## What it is for

Estates with more than one target platform and more than one team asking for things.
That is exactly where the effort it removes comes from: same request, different routes,
no shared rule.

With one platform and one team, rolling it out does not pay for itself.

## What to watch

An automation layer encodes the processes you have. Where no rule exists, it makes the
absence visible, and that is the uncomfortable part of any rollout. Those decisions
belong to the operating model, not to the product.