Speaking with TFiR, Dirk Alshuth of emma explained how multi-cloud fragmentation creates operational blind spots and how emma’s centralized governance model addresses policy enforcement across heterogeneous infrastructure without forcing migration.

What Is Multi-Cloud Fragmentation?

Alshuth identified infrastructure fragmentation as the core challenge enterprises face managing distributed environments. Different cloud providers operate with different tooling ecosystems for cost optimization, security enforcement, and compliance monitoring. Point solutions address specific providers but leave blind spots across the full estate.

Dirk Alshuth: “The challenge is in the fragmentation. What we see today is there are so many different needs a business has to serve by sourcing new infrastructure, by bringing in new skills for new infrastructure. Different providers, different environments also have different ways of managing it and optimizing it. There are so many tools out there that do one thing at a time, sometimes for a couple of providers, but not for all of them. So that’s the fragmentation which always leaves companies with blind spots in their operations.”

Broader Context

emma’s cloud operations platform addresses fragmentation through centralized governance. Policies, guardrails, security groups, and role-based access control are defined once at the organizational or project level and applied automatically across all infrastructure—greenfield sovereign cloud deployments, brownfield hyperscaler workloads, VMware estates, and Kubernetes clusters.

Dirk Alshuth: “emma is a centralized process. That means that for an organization or for specific projects, governance is defined. Policies are defined, and whatever happens within those projects, those policies are auto-applied. These are guardrails. These are security groups. There are specific policies also around—talking about sovereignty—the possibility to say, within a specific project, you cannot use specific cloud providers or specific regions. Or based on role-based access control, you can also limit the access to certain projects. All of that is centralized, all of that is managed by administrators.”

Alshuth emphasized that sovereignty policies can restrict infrastructure deployment to specific providers or regions based on data sensitivity. For example, an organization can define that certain projects cannot deploy workloads on non-European cloud providers, enforcing GDPR compliance at the governance layer rather than relying on manual enforcement.

Workflow visibility is also controlled centrally. While all workflows are visible to administrators, only workflows approved for specific projects are available to users within those projects. This prevents accidental or unauthorized use of deployment capabilities that violate organizational policies.

emma’s unified governance model eliminates the need for migration or re-provisioning. Existing brownfield infrastructure—VMware estates, Kubernetes clusters, hyperscaler workloads—can be brought under centralized governance alongside new greenfield deployments without disruption. Policies apply uniformly regardless of when infrastructure was deployed or which provider hosts it.

Watch the full TFiR interview with Dirk Alshuth here.