The News
At KubeCon + CloudNativeCon Europe 2026, emma Technologies announced Brownfield Onboarding, a new capability designed to bring existing VMware environments, Kubernetes clusters, and public cloud instances under unified governance without requiring migration, rebuilds, or disruption to running workloads. The announcement expands emma’s cloud operations platform beyond greenfield provisioning, positioning the company around a more practical question for enterprises already deep into hybrid and multi-cloud operations: how to govern what they already run while still preparing for AI, sovereignty, and cost pressures.
Analysis
Multi-Cloud Reality Is Outpacing Operational Models
The application development market has moved well beyond a simple cloud-first conversation. Our research shows that 54.4% of organizations primarily operate in hybrid deployment models, while 61.8% identify hybrid as their primary deployment model in application readiness research. At the same time, 70.4% of organizations rank AI/ML among top spending priorities, 62.7% prioritize security and compliance, and 65.9% prioritize cloud infrastructure investment. That combination is pushing platform and operations teams into a more complicated world where brownfield infrastructure, sovereignty requirements, and newer AI-oriented environments all have to coexist.
That broader shift came through clearly in emma’s KubeCon + CloudNativeCon Europe 2026 briefing. Derk Alshuth said the market is no longer really asking for a generic cloud management layer, but rather “that operations platform that helps organizations to first of all, distribute their cloud infrastructure and also manage it once it is distributed.” He also framed the company’s positioning in distinctly practical terms: “Do not put us in the drawer of being like, oh, you’re a FinOps tool. No, we’re not. You’re a cloud management or cost management platform? No, we’re not. You’re a networking tool? No, we’re not. There’s a lot of all those things coming together.” That is an important signal for the market. Developers and platform teams are increasingly dealing with infrastructure decisions that span cost, compliance, workload placement, and networking at the same time, not as separate buying categories.
emma Pushes Governance Into the Existing Estate
The strongest part of emma’s announcement is that it aims to address the operational gap many vendors avoid: existing infrastructure. As the press release puts it, most platforms govern only what they provision, while emma is extending governance to infrastructure that is already live across on-premises, hyperscaler, regional, and AI-focused environments. That is highly relevant in a market where modernization is increasingly constrained by what enterprises already have in production.
In the briefing, Alshuth described this directly, saying, “One of the things that we also launching now basically is brownfield onboarding. So that means discovery of brownfield resources, selective imports into visibility into Emma, and starting that governance process.” He later added that “brownfield and greenfields, traditional cloud or AI, will sit and live together under the same dashboard.” That is the core market message. emma is not asking teams to discard existing investments or force everything into a net-new operating model. Instead, it is trying to create a unified layer where current estates and future deployments can be managed together.
This lands at a moment when infrastructure fragmentation is becoming more expensive to ignore. 76% of organizations are very familiar with cloud-native principles, 76.8% already use GitOps, and 76.8% have integrated infrastructure as code into pipelines, yet complexity and cost remain among the top challenges in cloud-native readiness. That tells us the problem is no longer simple adoption. It is coordination across diverse environments, tools, and governance models.
Market Challenges and Insights
Developers and platform teams have usually handled these business challenges through a mix of native consoles, separate cost tools, custom networking, and manual inventory exercises. That approach worked when the environment was smaller and more centralized, but it has become harder to sustain as infrastructure sprawls across clouds, on-premises platforms, and newer AI-oriented environments. It is also creating visibility gaps at exactly the wrong moment. Our research shows that 50.7% of organizations cite limited tools as a challenge in securing infrastructure configurations, while 48.3% cite compliance requirements and 41.1% cite lack of expertise.
emma is speaking directly to that strain. In the briefing, Alshuth said customers want “the flexibility to bring their infrastructure wherever they need it based on cost, based on sovereignty, based on performance, based on latency.” He also emphasized that this is not just about provisioning new environments, but understanding and optimizing what is already there: “Make sure that you have that discovery. Make sure that you have that inventory. And then take a good look at how can we optimize that.” That reflects a broader market reality Paul Nashawaty has been highlighting across AppDev research: 2025 was heavily shaped by experimentation, but 2026 is increasingly about implementation, control, and extracting value from existing investments rather than endlessly adding new ones.
Another useful detail in emma’s story is its refusal to dictate a single tooling path. Alshuth noted, “We do not dictate how customers should work,” and explained that emma works with Terraform and Ansible providers while allowing customers to keep using preferred tooling and workflows. That openness matters because integration friction remains one of the biggest challenges in modern platform environments. Teams rarely want to rip out their current stack just to gain better governance.
Why This Could Change How Developers Handle Distributed Infrastructure
Looking ahead, emma’s announcement could matter most if brownfield governance becomes a normal requirement for platform engineering rather than a specialized migration task. The built-in logic around selective import, non-destructive operations, and visibility-first onboarding is a more realistic fit for enterprises that cannot afford to disrupt live environments just to modernize governance. It also aligns with a world where AI workloads are adding more infrastructure destinations, not fewer.
The company’s broader pitch is that brownfield discovery should become a control point for future optimization. Alshuth put it plainly: “Do not throw away the investment you already made, but take a very good look at it and valorize this against the new challenges.” He also described the next step as right-sizing, relocating, or shutting down resources based on actual need, rather than historic placement decisions. For developers and platform teams, that could eventually mean an operating model where infrastructure placement is less fixed and more continuously evaluated across cost, compliance, performance, and sovereignty boundaries.
That said, the market will likely judge emma on execution. The value proposition is strong because it acknowledges enterprise reality, but success will depend on how well the platform actually integrates into existing workflows, exposes useful insights through APIs and adjacent tools, and keeps governance flexible rather than heavy-handed. If emma can do that, it may help organizations move from fragmented multi-cloud operations toward a more policy-driven, developer-aware operational model without forcing a lift-and-shift mindset.
Looking Ahead
The infrastructure market is moving into a phase where brownfield is no longer the exception. It is the operating baseline. Enterprises are trying to support AI initiatives, meet regional sovereignty and compliance requirements, and optimize cost across estates that were never designed to function as a single system. That makes unified operations less of a convenience feature and more of a structural requirement.
emma Technologies used KubeCon + CloudNativeCon Europe 2026 to make that case clearly. Brownfield Onboarding suggests the company sees the market shifting away from greenfield-centric cloud stories and toward platforms that can bring existing infrastructure into a modern governance and optimization model. If that direction holds, emma could find a meaningful role with organizations that want enterprise-grade control without the overhead of rebuilding everything they already have.
Edge Intelligence Moves From Experimentation to Production Scale
Open Kubernetes Meets AI Infrastructure in a More Composable Stack
Kubernetes Rightsizing Shifts From Cost Math to Operational Trust
OpenSearch Expands Its Role in AI Infrastructure and Open Collaboration
Local Cloud Development Emerges as the Missing Layer for AI-Driven AppDev
