---
# source: src/content/services/en/orchestration-automation.md
# route:  /en/services/orchestration-automation/
title: Orchestration
group: infrastructure
audience: [enterprise, provider]
order: 8
tags: [automation, devops, cloud]
vendors: [vmware, morpheus, microsoft]
summary: Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more.
photoNeed: "Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration"
stub: false
draft: false
---

## The common assumption, and why it is wrong

Many organisations only automate a process once it runs constantly. We see it differently,
for a concrete reason.

A procedure that happens twice a year is the most error-prone one there is. It needs
knowledge nobody has to hand, it gets looked up again every time, and it gets done
differently every time. That is where automation returns most: not in time saved, but in
repeatability.

## What it covers

Provisioning virtual machines and containers, the processes around operating them, and
connections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud.

That gives one place to manage what otherwise lives in several consoles, keeps cost in
view, and turns the question of where a workload runs most cheaply into something you can
answer rather than estimate.

On top of that comes the part users see: a self-service portal where common and uncommon
requests sit as catalogue items. Whoever needs something fills in a form instead of
writing a ticket for somebody else to work through by hand.

Approvals can be tied to parameters: what stays under a limit is provisioned directly, what
exceeds it goes for approval.

## What we build it with

With products that have earned their place in this field:

- **Morpheus Data** as a multi-tenant, multi-cloud management platform
- **Microsoft MECM**
- **VCF Automation**
- **Ansible** and Ansible Tower

Morpheus ships with more than 80 native integrations. Where those fall short, we go through
the APIs that modern software offers anyway.

We are happy to show this in a live demo in our lab and work through the use cases you
actually have.

## What to watch

Automation encodes the processes you have. Where no rule exists, that shows up during the
rollout and the rule has to be written first. Those decisions belong in the operating model
and get taken there.