DE · EN

Call us

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: morpheus locale: en labels: vendor: Morpheus Enterprise capability/cloud: 1.94 capability/automation: 1.78 capability/devops: 3.42 vendor/morpheus: 3.67 annotations: source: src/content/solutions/en/morpheus.md route: /en/solutions/morpheus/ schema: /nerd/schema/solutions.json markdown: /en/solutions/morpheus.mdspec: 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 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. - 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: 267 services: - {ref: services/orchestration-automation, score: 1.00} - {ref: services/cloud, score: 0.48} - {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.28} - {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/vmware/vmware-cloud-foundation, score: 0.31} - {ref: solutions/vmware/vmware-cloud-foundation/vcf-automation, score: 0.31} - {ref: solutions/vmware, score: 0.24}

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "morpheus", "locale": "en", "labels": { "vendor": "Morpheus Enterprise", "capability/cloud": "1.94", "capability/automation": "1.78", "capability/devops": "3.42", "vendor/morpheus": "3.67" }, "annotations": { "source": "src/content/solutions/en/morpheus.md", "route": "/en/solutions/morpheus/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/morpheus.md" } }, "spec": { "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.\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." }, { "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": 267, "services": [ { "ref": "services/orchestration-automation", "score": "1.00" }, { "ref": "services/cloud", "score": "0.48" }, { "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.28" }, { "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/vmware/vmware-cloud-foundation", "score": "0.31" }, { "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.31" }, { "ref": "solutions/vmware", "score": "0.24" } ] }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "morpheus"locale = "en"[metadata.labels]vendor = "Morpheus Enterprise""capability/cloud" = "1.94""capability/automation" = "1.78""capability/devops" = "3.42""vendor/morpheus" = "3.67"[metadata.annotations]source = "src/content/solutions/en/morpheus.md"route = "/en/solutions/morpheus/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/morpheus.md"[spec]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 = falsedraft = falsekind = "product"addon = falsevendorName = "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[[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.'''[[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 = 267[[status.services]]ref = "services/orchestration-automation"score = "1.00"[[status.services]]ref = "services/cloud"score = "0.48"[[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.28"[[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/vmware/vmware-cloud-foundation"score = "0.31"[[status.neighbours]]ref = "solutions/vmware/vmware-cloud-foundation/vcf-automation"score = "0.31"[[status.neighbours]]ref = "solutions/vmware"score = "0.24"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>morpheus</name> <locale>en</locale> <labels> <vendor>Morpheus Enterprise</vendor> <entry key="capability/cloud">1.94</entry> <entry key="capability/automation">1.78</entry> <entry key="capability/devops">3.42</entry> <entry key="vendor/morpheus">3.67</entry> </labels> <annotations> <source>src/content/solutions/en/morpheus.md</source> <route>/en/solutions/morpheus/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/morpheus.md</markdown> </annotations> </metadata> <spec> <title>Morpheus</title> <tags> <item>cloud</item> <item>automation</item> <item>devops</item> </tags> <vendors> <item>morpheus</item> </vendors> <summary>A self-service layer across several platforms. Development teams order, operations keeps hold of policy and cost.</summary> <photoNeed>The Morpheus self-service catalogue on screen, with someone provisioning from it</photoNeed> <stub>false</stub> <draft>false</draft> <kind>product</kind> <addon>false</addon> <vendorName>Morpheus Enterprise</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. </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>267</corpus> <services> <item> <ref>services/orchestration-automation</ref> <score>1.00</score> </item> <item> <ref>services/cloud</ref> <score>0.48</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.28</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/vmware/vmware-cloud-foundation</ref> <score>0.31</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/vcf-automation</ref> <score>0.31</score> </item> <item> <ref>solutions/vmware</ref> <score>0.24</score> </item> </neighbours> </status></manifest>

Solution · Morpheus

Morpheus

The vendor calls it: Morpheus Enterprise

A self-service layer across several platforms. Development teams order, operations keeps hold of policy and cost.

Morpheus Platinum Partner

Topics Cloud 1.94 Automation 1.78 DevOps 3.42

Vendors Morpheus 3.67

04Services

05Posts

03Capabilities

267Corpus

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.

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.

What we do with it

Draft, unreviewed

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.

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.

Posts about it

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.94 Automation 1.78

share powershell scripts on-site

18 Jul 2017

If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.

Automation 1.78 DevOps 3.42

Breaking and Fixing

9 Aug 2018

Today I realized that my GitLab server was severely out of date and the underlying ubuntu (17.10) was end-of-life.

DevOps 3.42

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

14 Jul 2026

After changing a user's name in Active Directory, the new information may already be visible in Workspace ONE UEM and Omnissa Access while Intelligent Hub on the Mac still displays the old name.

Automation 1.78 Modern Workplace 2.11