Why Unified Orchestration Is Becoming Its Own Category

Enterprise automation grew up one domain at a time, leaving most organizations with a patchwork of cron jobs, glue code, decades-old schedulers, and modern cloud tools that rarely see each other. The patchwork holds on most days. But when a process breaks at a handoff between systems, no team can say which system owned the failure, and AI agents now taking action across those same seams raise the cost of that blind spot.

Mitch Ashley and Brad Shimmin speak with Kai Waehner, Global Field CTO at Kestra, to examine why unified orchestration is becoming a category of its own. Waehner explains what fails at the boundaries between data, infrastructure, applications, and business processes, and why connecting an agent to enterprise APIs has become the easy part of the job.

For enterprise leaders, the deployment question shifts to where governance lives. Waehner places control, access policy, and accountability in an orchestration layer above the agents, people, and automation doing the work, with sovereignty and deployment constraints defined before any tooling is chosen. Kestra customer JPMorgan Chase already runs cybersecurity workflows this way, coordinating threat intelligence collection, retries, failure handling, and real-time alerts across business units.

Key Takeaways:

🔹 Why fragmentation starts inside a single domain. Even enterprise scheduling alone can span cron jobs, glue code, 20-year-old schedulers, and cloud-native tools. As digital processes cross data, infrastructure, application, and business process domains, complexity concentrates at the seams between them.

🔹 Cross-domain failures expose the missing end-to-end view. Fragmented automation works most of the time, but when a cross-domain process breaks, teams lack the observability and governance to locate the problem. Recovery falls back on phone calls and processes that often exist only on paper.

🔹 Why agent governance is harder than agent connectivity. With MCP interfaces now common across vendors, an agent can quickly reach nearly any enterprise API. Access control, data security, and compliance are where deployments get difficult, because agents act without asking whether they're allowed to.

🔹 How transaction identity keeps agent actions traceable. In critical use cases, agents handle root cause analysis faster than any human team, while people make the final call through case or incident management. Waehner says the transaction identity should sit outside the agent so every action can be governed end to end, whether a human, an application, or an agent made the decision, across multi-model environments driven by sovereignty and cost.

🔹 Why sovereignty requirements must shape architecture first. Organizations should decide whether they need cloud, hybrid, or air-gapped deployment before choosing a Platform. Kestra separates the control plane from the data plane, so workers execute where the data lives, from cloud data platforms to on-premises data centers running mainframes to air-gapped factory environments.

Enterprises that build governance into the orchestration layer before agents scale will be able to add new models, clouds, and agents without rebuilding control each time.

Watch the full video at sixfivemedia.com, and subscribe to our YouTube channel so you never miss an episode.

Learn more about unified orchestration at kestra.io.

‍

Disclaimer: Six Five Media is for information and entertainment purposes only. Over the course of this video, we may discuss companies that are publicly traded, and we may reference their equity share prices. Nothing discussed during this webcast should be considered investment advice or a recommendation to buy or sell any security. We are not investment advisors, and you should not rely on this content as financial advice. Six Five Media collaborates with technology companies and industry leaders to produce research-driven interviews and multimedia programming for enterprise technology audiences.

‍