DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get solution/hpe/hpe-morpheus -o yaml$ soultec get solution/hpe/hpe-morpheus -o json$ soultec get solution/hpe/hpe-morpheus -o toml$ soultec get solution/hpe/hpe-morpheus -o xml$ python3 hpe/hpe-morpheus.pyPS> ./hpe/hpe-morpheus.ps1$ go run hpe/hpe-morpheus.go$ node hpe/hpe-morpheus.js

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: hpe/hpe-morpheus locale: en labels: vendor: HPE Morpheus Software capability/cloud: 1.92 capability/automation: 1.81 capability/devops: 3.16 vendor/hpe: 1.99 vendor/morpheus: 3.48 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 from the second use case onward. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that reuses them. 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. 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. - heading:

What it is for

body: | Estates with more than one target platform and more than one team asking for things. Without Morpheus, the same request takes different routes there and follows 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. Those processes should therefore be settled before it is rolled out.status: corpus: 315 services: - {ref: services/orchestration-automation, score: 0.89} - {ref: services/cloud, score: 0.50} - {ref: services/linux-container, score: 0.39} - {ref: services/it-architecture, score: 0.29} posts: - {ref: posts/hpe-vm-essentials-part-2, score: 0.46, via: solutions/hpe/hpe-morpheus/vm-essentials} - {ref: posts/hpe-vm-essentials-part1, score: 0.46, via: solutions/hpe/hpe-morpheus/vm-essentials} - {ref: posts/morpheus-cloud-management-plattform, score: 0.68} experts: - {ref: experts/christian-schnyder, score: 0.49} - {ref: experts/marco-mattei, score: 0.45} - {ref: experts/tobias-waelti, score: 0.45} neighbours: - {ref: solutions/hpe, relation: parent} - {ref: solutions/vmware/vmware-cloud-foundation/vcf-automation, score: 0.58} - {ref: solutions/hpe/hpe-private-cloud-business-edition-pcbe, score: 0.46} - {ref: solutions/hpe/hpe-morpheus/vm-essentials, score: 0.42} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "hpe/hpe-morpheus", "locale": "en", "labels": { "vendor": "HPE Morpheus Software", "capability/cloud": 1.92, "capability/automation": 1.81, "capability/devops": 3.16, "vendor/hpe": 1.99, "vendor/morpheus": 3.48 }, "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 from the second use case onward. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that reuses them.\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. It sits at the top of an HPE software family, with Morpheus VM\nEssentials underneath it as the virtualization tier, and HPE licenses both **per socket**\nrather than per core." }, { "heading": "

What it is for

", "body": "Estates with more than one target platform and more than one team asking for things.\nWithout Morpheus, the same request takes different routes there and follows no shared\nrule.\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. Those processes should therefore be\nsettled before it is rolled out." } ] }, "status": { "corpus": 315, "services": [ { "ref": "services/orchestration-automation", "score": "0.89" }, { "ref": "services/cloud", "score": "0.50" }, { "ref": "services/linux-container", "score": "0.39" }, { "ref": "services/it-architecture", "score": "0.29" } ], "posts": [ { "ref": "posts/hpe-vm-essentials-part-2", "score": "0.46", "via": "solutions/hpe/hpe-morpheus/vm-essentials" }, { "ref": "posts/hpe-vm-essentials-part1", "score": "0.46", "via": "solutions/hpe/hpe-morpheus/vm-essentials" }, { "ref": "posts/morpheus-cloud-management-plattform", "score": "0.68" } ], "experts": [ { "ref": "experts/christian-schnyder", "score": "0.49" }, { "ref": "experts/marco-mattei", "score": "0.45" }, { "ref": "experts/tobias-waelti", "score": "0.45" } ], "neighbours": [ { "ref": "solutions/hpe", "relation": "parent" }, { "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.58" }, { "ref": "solutions/hpe/hpe-private-cloud-business-edition-pcbe", "score": "0.46" }, { "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.42" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "hpe/hpe-morpheus"locale = "en"[metadata.labels]vendor = "HPE Morpheus Software""capability/cloud" = 1.92"capability/automation" = 1.81"capability/devops" = 3.16"vendor/hpe" = 1.99"vendor/morpheus" = 3.48[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 from the second use case onward. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that reuses them.'''practiceReview = true[[spec.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.'''[[spec.sections]]heading = "

What changed

"body = '''Morpheus was an independent company. HPE acquired Morpheus Data, and the product is HPEMorpheus Software now. It sits at the top of an HPE software family, with Morpheus VMEssentials underneath it as the virtualization tier, and HPE licenses both **per socket**rather than per core.'''[[spec.sections]]heading = "

What it is for

"body = '''Estates with more than one target platform and more than one team asking for things.Without Morpheus, the same request takes different routes there and follows no sharedrule.With one platform and one team, rolling it out does not pay for itself.'''[[spec.sections]]heading = "

What to watch

"body = '''An automation layer encodes the processes you have. Those processes should therefore besettled before it is rolled out.'''[status]corpus = 315search = "/en/search.json"[[status.services]]ref = "services/orchestration-automation"score = "0.89"[[status.services]]ref = "services/cloud"score = "0.50"[[status.services]]ref = "services/linux-container"score = "0.39"[[status.services]]ref = "services/it-architecture"score = "0.29"[[status.posts]]ref = "posts/hpe-vm-essentials-part-2"score = "0.46"via = "solutions/hpe/hpe-morpheus/vm-essentials"[[status.posts]]ref = "posts/hpe-vm-essentials-part1"score = "0.46"via = "solutions/hpe/hpe-morpheus/vm-essentials"[[status.posts]]ref = "posts/morpheus-cloud-management-plattform"score = "0.68"[[status.experts]]ref = "experts/christian-schnyder"score = "0.49"[[status.experts]]ref = "experts/marco-mattei"score = "0.45"[[status.experts]]ref = "experts/tobias-waelti"score = "0.45"[[status.neighbours]]ref = "solutions/hpe"relation = "parent"[[status.neighbours]]ref = "solutions/vmware/vmware-cloud-foundation/vcf-automation"score = "0.58"[[status.neighbours]]ref = "solutions/hpe/hpe-private-cloud-business-edition-pcbe"score = "0.46"[[status.neighbours]]ref = "solutions/hpe/hpe-morpheus/vm-essentials"score = "0.42"

<?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.92</entry> <entry key="capability/automation">1.81</entry> <entry key="capability/devops">3.16</entry> <entry key="vendor/hpe">1.99</entry> <entry key="vendor/morpheus">3.48</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 from the second use case onward. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that reuses them. </practice> <practiceReview>true</practiceReview> <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. It sits at the top of an HPE software family, with Morpheus VMEssentials underneath it as the virtualization tier, and HPE licenses both **per socket**rather than per core. </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.Without Morpheus, the same request takes different routes there and follows no sharedrule.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. Those processes should therefore besettled before it is rolled out. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <services> <item> <ref>services/orchestration-automation</ref> <score>0.89</score> </item> <item> <ref>services/cloud</ref> <score>0.50</score> </item> <item> <ref>services/linux-container</ref> <score>0.39</score> </item> <item> <ref>services/it-architecture</ref> <score>0.29</score> </item> </services> <posts> <item> <ref>posts/hpe-vm-essentials-part-2</ref> <score>0.46</score> <via>solutions/hpe/hpe-morpheus/vm-essentials</via> </item> <item> <ref>posts/hpe-vm-essentials-part1</ref> <score>0.46</score> <via>solutions/hpe/hpe-morpheus/vm-essentials</via> </item> <item> <ref>posts/morpheus-cloud-management-plattform</ref> <score>0.68</score> </item> </posts> <experts> <item> <ref>experts/christian-schnyder</ref> <score>0.49</score> </item> <item> <ref>experts/marco-mattei</ref> <score>0.45</score> </item> <item> <ref>experts/tobias-waelti</ref> <score>0.45</score> </item> </experts> <neighbours> <item> <ref>solutions/hpe</ref> <relation>parent</relation> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/vcf-automation</ref> <score>0.58</score> </item> <item> <ref>solutions/hpe/hpe-private-cloud-business-edition-pcbe</ref> <score>0.46</score> </item> <item> <ref>solutions/hpe/hpe-morpheus/vm-essentials</ref> <score>0.42</score> </item> </neighbours> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "hpe/hpe-morpheus", "locale": "en", "labels": { "vendor": "HPE Morpheus Software", "capability/cloud": 1.92, "capability/automation": 1.81, "capability/devops": 3.16, "vendor/hpe": 1.99, "vendor/morpheus": 3.48, }, "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 from the second use case onward. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that reuses them.\n" ), "practiceReview": True, "sections": [ { "heading": "

What it is

", "body": ( "Morpheus puts an ordering and management layer over the platforms already in place.\n" "vSphere, a hyperscaler and Kubernetes appear in the same catalogue. What a team may\n" "order, how it gets named and what it costs are defined once.\n" "\n" "It installs on Linux, on-premises or in a public cloud, and it reaches the systems around\n" "it through integrations rather than through code: load balancers, backup, DNS and IPAM,\n" "ITSM, and the DevOps tools a team already runs, Ansible, Terraform, Puppet and Jenkins\n" "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\n" "Morpheus Software now. It sits at the top of an HPE software family, with Morpheus VM\n" "Essentials underneath it as the virtualization tier, and HPE licenses both **per socket**\n" "rather than per core." ), }, { "heading": "

What it is for

", "body": ( "Estates with more than one target platform and more than one team asking for things.\n" "Without Morpheus, the same request takes different routes there and follows no shared\n" "rule.\n" "\n" "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. Those processes should therefore be\n" "settled before it is rolled out." ), }, ], }, "status": { "corpus": 315, "services": [ { "ref": "services/orchestration-automation", "score": "0.89", }, { "ref": "services/cloud", "score": "0.50", }, { "ref": "services/linux-container", "score": "0.39", }, { "ref": "services/it-architecture", "score": "0.29", }, ], "posts": [ { "ref": "posts/hpe-vm-essentials-part-2", "score": "0.46", "via": "solutions/hpe/hpe-morpheus/vm-essentials", }, { "ref": "posts/hpe-vm-essentials-part1", "score": "0.46", "via": "solutions/hpe/hpe-morpheus/vm-essentials", }, { "ref": "posts/morpheus-cloud-management-plattform", "score": "0.68", }, ], "experts": [ { "ref": "experts/christian-schnyder", "score": "0.49", }, { "ref": "experts/marco-mattei", "score": "0.45", }, { "ref": "experts/tobias-waelti", "score": "0.45", }, ], "neighbours": [ { "ref": "solutions/hpe", "relation": "parent", }, { "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.58", }, { "ref": "solutions/hpe/hpe-private-cloud-business-edition-pcbe", "score": "0.46", }, { "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.42", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Solution' metadata = [ordered]@{ name = 'hpe/hpe-morpheus' locale = 'en' labels = [ordered]@{ vendor = 'HPE Morpheus Software' 'capability/cloud' = 1.92 'capability/automation' = 1.81 'capability/devops' = 3.16 'vendor/hpe' = 1.99 'vendor/morpheus' = 3.48 } annotations = [ordered]@{ 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 = [ordered]@{ 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 from the second use case onward. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that reuses them.'@ practiceReview = $true sections = @( [ordered]@{ 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.'@ } [ordered]@{ heading = '

What changed

' body = @'Morpheus was an independent company. HPE acquired Morpheus Data, and the product is HPEMorpheus Software now. It sits at the top of an HPE software family, with Morpheus VMEssentials underneath it as the virtualization tier, and HPE licenses both **per socket**rather than per core.'@ } [ordered]@{ heading = '

What it is for

' body = @'Estates with more than one target platform and more than one team asking for things.Without Morpheus, the same request takes different routes there and follows no sharedrule.With one platform and one team, rolling it out does not pay for itself.'@ } [ordered]@{ heading = '

What to watch

' body = @'An automation layer encodes the processes you have. Those processes should therefore besettled before it is rolled out.'@ } ) } status = [ordered]@{ corpus = 315 services = @( [ordered]@{ ref = 'services/orchestration-automation' score = '0.89' } [ordered]@{ ref = 'services/cloud' score = '0.50' } [ordered]@{ ref = 'services/linux-container' score = '0.39' } [ordered]@{ ref = 'services/it-architecture' score = '0.29' } ) posts = @( [ordered]@{ ref = 'posts/hpe-vm-essentials-part-2' score = '0.46' via = 'solutions/hpe/hpe-morpheus/vm-essentials' } [ordered]@{ ref = 'posts/hpe-vm-essentials-part1' score = '0.46' via = 'solutions/hpe/hpe-morpheus/vm-essentials' } [ordered]@{ ref = 'posts/morpheus-cloud-management-plattform' score = '0.68' } ) experts = @( [ordered]@{ ref = 'experts/christian-schnyder' score = '0.49' } [ordered]@{ ref = 'experts/marco-mattei' score = '0.45' } [ordered]@{ ref = 'experts/tobias-waelti' score = '0.45' } ) neighbours = @( [ordered]@{ ref = 'solutions/hpe' relation = 'parent' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/vcf-automation' score = '0.58' } [ordered]@{ ref = 'solutions/hpe/hpe-private-cloud-business-edition-pcbe' score = '0.46' } [ordered]@{ ref = 'solutions/hpe/hpe-morpheus/vm-essentials' score = '0.42' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": map[string]any{ "name": "hpe/hpe-morpheus", "locale": "en", "labels": map[string]any{ "vendor": "HPE Morpheus Software", "capability/cloud": 1.92, "capability/automation": 1.81, "capability/devops": 3.16, "vendor/hpe": 1.99, "vendor/morpheus": 3.48, }, "annotations": map[string]any{ "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": map[string]any{ "title": "HPE Morpheus", "tags": []any{"cloud", "automation", "devops"}, "vendors": []any{"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 from the second use case onward. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that reuses them.\n", "practiceReview": true, "sections": []any{ map[string]any{ "heading": "

What it is

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

What changed

", "body": "Morpheus was an independent company. HPE acquired Morpheus Data, and the product is HPE\n" + "Morpheus Software now. It sits at the top of an HPE software family, with Morpheus VM\n" + "Essentials underneath it as the virtualization tier, and HPE licenses both **per socket**\n" + "rather than per core.", }, map[string]any{ "heading": "

What it is for

", "body": "Estates with more than one target platform and more than one team asking for things.\n" + "Without Morpheus, the same request takes different routes there and follows no shared\n" + "rule.\n" + "\n" + "With one platform and one team, rolling it out does not pay for itself.", }, map[string]any{ "heading": "

What to watch

", "body": "An automation layer encodes the processes you have. Those processes should therefore be\n" + "settled before it is rolled out.", }, }, }, "status": map[string]any{ "corpus": 315, "services": []any{ map[string]any{ "ref": "services/orchestration-automation", "score": "0.89", }, map[string]any{ "ref": "services/cloud", "score": "0.50", }, map[string]any{ "ref": "services/linux-container", "score": "0.39", }, map[string]any{ "ref": "services/it-architecture", "score": "0.29", }, }, "posts": []any{ map[string]any{ "ref": "posts/hpe-vm-essentials-part-2", "score": "0.46", "via": "solutions/hpe/hpe-morpheus/vm-essentials", }, map[string]any{ "ref": "posts/hpe-vm-essentials-part1", "score": "0.46", "via": "solutions/hpe/hpe-morpheus/vm-essentials", }, map[string]any{ "ref": "posts/morpheus-cloud-management-plattform", "score": "0.68", }, }, "experts": []any{ map[string]any{ "ref": "experts/christian-schnyder", "score": "0.49", }, map[string]any{ "ref": "experts/marco-mattei", "score": "0.45", }, map[string]any{ "ref": "experts/tobias-waelti", "score": "0.45", }, }, "neighbours": []any{ map[string]any{ "ref": "solutions/hpe", "relation": "parent", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.58", }, map[string]any{ "ref": "solutions/hpe/hpe-private-cloud-business-edition-pcbe", "score": "0.46", }, map[string]any{ "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.42", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Solution", metadata: { name: "hpe/hpe-morpheus", locale: "en", labels: { vendor: "HPE Morpheus Software", "capability/cloud": 1.92, "capability/automation": 1.81, "capability/devops": 3.16, "vendor/hpe": 1.99, "vendor/morpheus": 3.48, }, 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 from the second use case onward. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that reuses them.\n", practiceReview: true, sections: [ { heading: "

What it is

", body: "Morpheus puts an ordering and management layer over the platforms already in place.\n" + "vSphere, a hyperscaler and Kubernetes appear in the same catalogue. What a team may\n" + "order, how it gets named and what it costs are defined once.\n" + "\n" + "It installs on Linux, on-premises or in a public cloud, and it reaches the systems around\n" + "it through integrations rather than through code: load balancers, backup, DNS and IPAM,\n" + "ITSM, and the DevOps tools a team already runs, Ansible, Terraform, Puppet and Jenkins\n" + "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\n" + "Morpheus Software now. It sits at the top of an HPE software family, with Morpheus VM\n" + "Essentials underneath it as the virtualization tier, and HPE licenses both **per socket**\n" + "rather than per core.", }, { heading: "

What it is for

", body: "Estates with more than one target platform and more than one team asking for things.\n" + "Without Morpheus, the same request takes different routes there and follows no shared\n" + "rule.\n" + "\n" + "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. Those processes should therefore be\n" + "settled before it is rolled out.", }, ], }, status: { corpus: 315, services: [ { ref: "services/orchestration-automation", score: "0.89", }, { ref: "services/cloud", score: "0.50", }, { ref: "services/linux-container", score: "0.39", }, { ref: "services/it-architecture", score: "0.29", }, ], posts: [ { ref: "posts/hpe-vm-essentials-part-2", score: "0.46", via: "solutions/hpe/hpe-morpheus/vm-essentials", }, { ref: "posts/hpe-vm-essentials-part1", score: "0.46", via: "solutions/hpe/hpe-morpheus/vm-essentials", }, { ref: "posts/morpheus-cloud-management-plattform", score: "0.68", }, ], experts: [ { ref: "experts/christian-schnyder", score: "0.49", }, { ref: "experts/marco-mattei", score: "0.45", }, { ref: "experts/tobias-waelti", score: "0.45", }, ], neighbours: [ { ref: "solutions/hpe", relation: "parent", }, { ref: "solutions/vmware/vmware-cloud-foundation/vcf-automation", score: "0.58", }, { ref: "solutions/hpe/hpe-private-cloud-business-edition-pcbe", score: "0.46", }, { ref: "solutions/hpe/hpe-morpheus/vm-essentials", score: "0.42", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 90 lines · YAML · validated at build# 134 lines · JSON · validated at build# 141 lines · TOML · validated at build# 160 lines · XML · validated at build# 158 lines · Python · read back at build, equals the JSON record# 156 lines · PowerShell · read back at build, equals the JSON record# 160 lines · Go · read back at build, equals the JSON record# 145 lines · JavaScript · read back at build, equals the JSON record · served at /en/solutions/hpe/hpe-morpheus.md

Solution · HPE

HPE Morpheus

formerly Morpheus Cloud Management Platform

The vendor calls it: HPE Morpheus Software

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.

HPE Gold Partner

Topics Cloud 1.92 Automation 1.81 DevOps 3.16

Vendors HPE 1.99 Morpheus 3.48

04Services

03Posts

03Capabilities

315Corpus

photograph wantedThe Morpheus self-service catalogue on screen, with someone provisioning from it

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.

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.

What changed

Morpheus was an independent company. HPE acquired Morpheus Data, and the product is HPE Morpheus Software now. 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.

What it is for

Estates with more than one target platform and more than one team asking for things. Without Morpheus, the same request takes different routes there and follows 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. Those processes should therefore be settled before it is rolled out.

What we do with it

Draft, unreviewed

Draft, not yet reviewed. The value nearly always shows up from the second use case onward. One ordering path seldom justifies the setup. Once naming, entitlements and teardown live in one place, though, every path after that reuses them.

This paragraph is a draft and nobody at soulTec has confirmed it yet. Everything above it describes the product and is checkable against the vendor.

Products 1

Morpheus VM Essentials

HPE's own hypervisor with a control plane that runs it beside vSphere. Licensed per socket, on one, three or five year terms.

VirtualizationMigrationCloud

Posts about it

HPE VM Essentials – Part 2

6 May 2025

Part 1 covered where VME stood in mid-February. A few weeks on, a fair amount has changed, and we built a three-node VME cluster in our lab.

Virtualization 1.42

HPE VM Essentials – Part 1

26 Feb 2025

HPE's own hypervisor, HPE VM Essentials, has been available in Europe since mid-February. Through the Morpheus Data acquisition, HPE has a proven KVM-based hypervisor.

Virtualization 1.42

Morpheus Cloud Management Platform

1 Sep 2022

As a Morpheus partner with certified specialists on the team, we want to take a moment to show what Morpheus is and how it makes your life in your infrastructure easier.

Cloud 1.92 Automation 1.81