HPE Morpheus

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: hpe/hpe-morpheus locale: en labels: vendor: HPE Morpheus Software capability/cloud: 1.98 capability/automation: 1.82 capability/devops: 3.52 vendor/hpe: 1.97 vendor/morpheus: 3.63 annotations: source: src/content/solutions/en/hpe/hpe-morpheus.md route: /en/solutions/hpe/hpe-morpheus/ schema: /nerd/schema/solutions.json markdown: /en/solutions/hpe/hpe-morpheus.mdspec: title: HPE Morpheus tags: [cloud, automation, devops] vendors: [hpe, morpheus] summary: >- A self-service layer across several platforms. Development teams order, operations keeps hold of policy and cost. An HPE product since the Morpheus Data acquisition. photoNeed: >- The Morpheus self-service catalogue on screen, with someone provisioning from it stub: false draft: false kind: platform formerly: Morpheus Cloud Management Platform addon: false sourceNote: >- HPE product page for HPE Morpheus Software, read 2026-08-30, which calls it a hybrid cloud platform and states per-socket licensing vendorName: HPE Morpheus Software 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 sections: - heading:

What it is

body: | 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. It installs on Linux, on-premises or in a public cloud, and it reaches the systems around it through integrations rather than through code: load balancers, backup, DNS and IPAM, ITSM, and the DevOps tools a team already runs, Ansible, Terraform, Puppet and Jenkins among them. Scripts that exist keep working, from disk or from a Git repository. - heading:

What changed

body: | Morpheus was an independent company. HPE acquired Morpheus Data, and the product is HPE Morpheus Software now. That is not only a badge: it sits at the top of an HPE software family, with Morpheus VM Essentials underneath it as the virtualization tier, and HPE licenses both **per socket** rather than per core. Per socket is the part worth reading twice if you are costing a way out of a per-core licence. - heading:

What it is for

body: | 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. - heading:

What to watch

body: | 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.status: corpus: 295 services: - {ref: services/orchestration-automation, score: 0.89} - {ref: services/cloud, score: 0.49} - {ref: services/linux-container, score: 0.40} - {ref: services/platform, score: 0.30} posts: - {ref: posts/morpheus-cloud-management-plattform, score: 0.66} - {ref: posts/my-solution-to-share-powershell-scripts, score: 0.51} - {ref: posts/breaking-and-fixing-gitlab, score: 0.34} - {ref: posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change, score: 0.29} - {ref: posts/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself, score: 0.28} experts: - {ref: experts/christian-schnyder, score: 0.58} - {ref: experts/fabian-faessler, score: 0.39} - {ref: experts/patrick-pletscher, score: 0.39} neighbours: - {ref: solutions/hpe/hpe-private-cloud-business-edition-pcbe, score: 0.46} - {ref: solutions/hpe/hpe-greenlake, score: 0.41} - {ref: solutions/hpe/hpe-private-cloud-ai, score: 0.41}

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "hpe/hpe-morpheus", "locale": "en", "labels": { "vendor": "HPE Morpheus Software", "capability/cloud": "1.98", "capability/automation": "1.82", "capability/devops": "3.52", "vendor/hpe": "1.97", "vendor/morpheus": "3.63" }, "annotations": { "source": "src/content/solutions/en/hpe/hpe-morpheus.md", "route": "/en/solutions/hpe/hpe-morpheus/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/hpe/hpe-morpheus.md" } }, "spec": { "title": "HPE Morpheus", "tags": [ "cloud", "automation", "devops" ], "vendors": [ "hpe", "morpheus" ], "summary": "A self-service layer across several platforms. Development teams order, operations keeps hold of policy and cost. An HPE product since the Morpheus Data acquisition.", "photoNeed": "The Morpheus self-service catalogue on screen, with someone provisioning from it", "stub": false, "draft": false, "kind": "platform", "formerly": "Morpheus Cloud Management Platform", "addon": false, "sourceNote": "HPE product page for HPE Morpheus Software, read 2026-08-30, which calls it a hybrid cloud platform and states per-socket licensing", "vendorName": "HPE Morpheus Software", "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.\n", "practiceReview": true }, "sections": [ { "heading": "

What it is

", "body": "Morpheus puts an ordering and management layer over the platforms already in place.\nvSphere, a hyperscaler and Kubernetes appear in the same catalogue. What a team may\norder, how it gets named and what it costs are defined once.\n\nIt installs on Linux, on-premises or in a public cloud, and it reaches the systems around\nit through integrations rather than through code: load balancers, backup, DNS and IPAM,\nITSM, and the DevOps tools a team already runs, Ansible, Terraform, Puppet and Jenkins\namong them. Scripts that exist keep working, from disk or from a Git repository." }, { "heading": "

What changed

", "body": "Morpheus was an independent company. HPE acquired Morpheus Data, and the product is HPE\nMorpheus Software now. That is not only a badge: it sits at the top of an HPE software\nfamily, with Morpheus VM Essentials underneath it as the virtualization tier, and HPE\nlicenses both **per socket** rather than per core.\n\nPer socket is the part worth reading twice if you are costing a way out of a per-core\nlicence." }, { "heading": "

What it is for

", "body": "Estates with more than one target platform and more than one team asking for things.\nThat is exactly where the effort it removes comes from: same request, different routes,\nno shared rule.\n\nWith one platform and one team, rolling it out does not pay for itself." }, { "heading": "

What to watch

", "body": "An automation layer encodes the processes you have. Where no rule exists, it makes the\nabsence visible, and that is the uncomfortable part of any rollout. Those decisions\nbelong to the operating model, not to the product." } ], "status": { "corpus": 295, "services": [ { "ref": "services/orchestration-automation", "score": "0.89" }, { "ref": "services/cloud", "score": "0.49" }, { "ref": "services/linux-container", "score": "0.40" }, { "ref": "services/platform", "score": "0.30" } ], "posts": [ { "ref": "posts/morpheus-cloud-management-plattform", "score": "0.66" }, { "ref": "posts/my-solution-to-share-powershell-scripts", "score": "0.51" }, { "ref": "posts/breaking-and-fixing-gitlab", "score": "0.34" }, { "ref": "posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change", "score": "0.29" }, { "ref": "posts/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself", "score": "0.28" } ], "experts": [ { "ref": "experts/christian-schnyder", "score": "0.58" }, { "ref": "experts/fabian-faessler", "score": "0.39" }, { "ref": "experts/patrick-pletscher", "score": "0.39" } ], "neighbours": [ { "ref": "solutions/hpe/hpe-private-cloud-business-edition-pcbe", "score": "0.46" }, { "ref": "solutions/hpe/hpe-greenlake", "score": "0.41" }, { "ref": "solutions/hpe/hpe-private-cloud-ai", "score": "0.41" } ] }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "hpe/hpe-morpheus"locale = "en"[metadata.labels]vendor = "HPE Morpheus Software""capability/cloud" = "1.98""capability/automation" = "1.82""capability/devops" = "3.52""vendor/hpe" = "1.97""vendor/morpheus" = "3.63"[metadata.annotations]source = "src/content/solutions/en/hpe/hpe-morpheus.md"route = "/en/solutions/hpe/hpe-morpheus/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/hpe/hpe-morpheus.md"[spec]title = "HPE Morpheus"tags = ["cloud", "automation", "devops"]vendors = ["hpe", "morpheus"]summary = "A self-service layer across several platforms. Development teams order, operations keeps hold of policy and cost. An HPE product since the Morpheus Data acquisition."photoNeed = "The Morpheus self-service catalogue on screen, with someone provisioning from it"stub = falsedraft = falsekind = "platform"formerly = "Morpheus Cloud Management Platform"addon = falsesourceNote = "HPE product page for HPE Morpheus Software, read 2026-08-30, which calls it a hybrid cloud platform and states per-socket licensing"vendorName = "HPE Morpheus Software"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[[sections]]heading = "

What it is

"body = '''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 mayorder, how it gets named and what it costs are defined once.It installs on Linux, on-premises or in a public cloud, and it reaches the systems aroundit through integrations rather than through code: load balancers, backup, DNS and IPAM,ITSM, and the DevOps tools a team already runs, Ansible, Terraform, Puppet and Jenkinsamong them. Scripts that exist keep working, from disk or from a Git repository.'''[[sections]]heading = "

What changed

"body = '''Morpheus was an independent company. HPE acquired Morpheus Data, and the product is HPEMorpheus Software now. That is not only a badge: it sits at the top of an HPE softwarefamily, with Morpheus VM Essentials underneath it as the virtualization tier, and HPElicenses both **per socket** rather than per core.Per socket is the part worth reading twice if you are costing a way out of a per-corelicence.'''[[sections]]heading = "

What it is for

"body = '''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.'''[[sections]]heading = "

What to watch

"body = '''An automation layer encodes the processes you have. Where no rule exists, it makes theabsence visible, and that is the uncomfortable part of any rollout. Those decisionsbelong to the operating model, not to the product.'''[status]corpus = 295[[status.services]]ref = "services/orchestration-automation"score = "0.89"[[status.services]]ref = "services/cloud"score = "0.49"[[status.services]]ref = "services/linux-container"score = "0.40"[[status.services]]ref = "services/platform"score = "0.30"[[status.posts]]ref = "posts/morpheus-cloud-management-plattform"score = "0.66"[[status.posts]]ref = "posts/my-solution-to-share-powershell-scripts"score = "0.51"[[status.posts]]ref = "posts/breaking-and-fixing-gitlab"score = "0.34"[[status.posts]]ref = "posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change"score = "0.29"[[status.posts]]ref = "posts/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself"score = "0.28"[[status.experts]]ref = "experts/christian-schnyder"score = "0.58"[[status.experts]]ref = "experts/fabian-faessler"score = "0.39"[[status.experts]]ref = "experts/patrick-pletscher"score = "0.39"[[status.neighbours]]ref = "solutions/hpe/hpe-private-cloud-business-edition-pcbe"score = "0.46"[[status.neighbours]]ref = "solutions/hpe/hpe-greenlake"score = "0.41"[[status.neighbours]]ref = "solutions/hpe/hpe-private-cloud-ai"score = "0.41"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>hpe/hpe-morpheus</name> <locale>en</locale> <labels> <vendor>HPE Morpheus Software</vendor> <entry key="capability/cloud">1.98</entry> <entry key="capability/automation">1.82</entry> <entry key="capability/devops">3.52</entry> <entry key="vendor/hpe">1.97</entry> <entry key="vendor/morpheus">3.63</entry> </labels> <annotations> <source>src/content/solutions/en/hpe/hpe-morpheus.md</source> <route>/en/solutions/hpe/hpe-morpheus/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/hpe/hpe-morpheus.md</markdown> </annotations> </metadata> <spec> <title>HPE Morpheus</title> <tags> <item>cloud</item> <item>automation</item> <item>devops</item> </tags> <vendors> <item>hpe</item> <item>morpheus</item> </vendors> <summary>A self-service layer across several platforms. Development teams order, operations keeps hold of policy and cost. An HPE product since the Morpheus Data acquisition.</summary> <photoNeed>The Morpheus self-service catalogue on screen, with someone provisioning from it</photoNeed> <stub>false</stub> <draft>false</draft> <kind>platform</kind> <formerly>Morpheus Cloud Management Platform</formerly> <addon>false</addon> <sourceNote>HPE product page for HPE Morpheus Software, read 2026-08-30, which calls it a hybrid cloud platform and states per-socket licensing</sourceNote> <vendorName>HPE Morpheus Software</vendorName> <status>current</status> <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. </practice> <practiceReview>true</practiceReview> </spec> <sections> <section> <heading>

What it is

</heading> <body>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 mayorder, how it gets named and what it costs are defined once.It installs on Linux, on-premises or in a public cloud, and it reaches the systems aroundit through integrations rather than through code: load balancers, backup, DNS and IPAM,ITSM, and the DevOps tools a team already runs, Ansible, Terraform, Puppet and Jenkinsamong them. Scripts that exist keep working, from disk or from a Git repository. </body> </section> <section> <heading>

What changed

</heading> <body>Morpheus was an independent company. HPE acquired Morpheus Data, and the product is HPEMorpheus Software now. That is not only a badge: it sits at the top of an HPE softwarefamily, with Morpheus VM Essentials underneath it as the virtualization tier, and HPElicenses both **per socket** rather than per core.Per socket is the part worth reading twice if you are costing a way out of a per-corelicence. </body> </section> <section> <heading>

What it is for

</heading> <body>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. </body> </section> <section> <heading>

What to watch

</heading> <body>An automation layer encodes the processes you have. Where no rule exists, it makes theabsence visible, and that is the uncomfortable part of any rollout. Those decisionsbelong to the operating model, not to the product. </body> </section> </sections> <status> <corpus>295</corpus> <services> <item> <ref>services/orchestration-automation</ref> <score>0.89</score> </item> <item> <ref>services/cloud</ref> <score>0.49</score> </item> <item> <ref>services/linux-container</ref> <score>0.40</score> </item> <item> <ref>services/platform</ref> <score>0.30</score> </item> </services> <posts> <item> <ref>posts/morpheus-cloud-management-plattform</ref> <score>0.66</score> </item> <item> <ref>posts/my-solution-to-share-powershell-scripts</ref> <score>0.51</score> </item> <item> <ref>posts/breaking-and-fixing-gitlab</ref> <score>0.34</score> </item> <item> <ref>posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change</ref> <score>0.29</score> </item> <item> <ref>posts/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself</ref> <score>0.28</score> </item> </posts> <experts> <item> <ref>experts/christian-schnyder</ref> <score>0.58</score> </item> <item> <ref>experts/fabian-faessler</ref> <score>0.39</score> </item> <item> <ref>experts/patrick-pletscher</ref> <score>0.39</score> </item> </experts> <neighbours> <item> <ref>solutions/hpe/hpe-private-cloud-business-edition-pcbe</ref> <score>0.46</score> </item> <item> <ref>solutions/hpe/hpe-greenlake</ref> <score>0.41</score> </item> <item> <ref>solutions/hpe/hpe-private-cloud-ai</ref> <score>0.41</score> </item> </neighbours> </status></manifest>

What it is

What changed

What it is for

What to watch

What it is

What changed

What it is for

What to watch

What it is

What changed

What it is for

What to watch

What it is

What changed

What it is for

What to watch

What it is

What changed

What it is for

What to watch

What we do with it

Posts about it

Morpheus Cloud Management Platform

share powershell scripts on-site

Breaking and Fixing

Intelligent Hub on macOS Not Synchronizing After an Active Directory User Name Change

Fix Windows Server Internet Access When the Default Route Points to Itself

Who works with it

Christian Schnyder

Fabian Fässler

Patrick Pletscher