October 2026 Summaries

Enterprises often rely on fragmented automation tools across infrastructure, data, applications, and business processes, creating gaps in observability, governance, and incident response when workflows span domains. The piece argues that a unified orchestration layer can coordinate these systems end to end, particularly as AI agents are introduced to perform tasks within and across domains. Although connecting agents through APIs and MCP may be straightforward, effective deployment requires controls over data access, permitted actions, compliance, human approvals for critical decisions, and a persistent transaction identifier outside the agent to preserve auditability. It presents Kestra’s execution model as an example of unifying AI steps, human decisions, and remediation within one governed workflow, while supporting multiple AI models and deployment environments. The discussion also emphasizes designing for data sovereignty, privacy, security, hybrid infrastructure, and air-gapped environments from the outset, and cites JPMorgan Chase’s use of Kestra to collect, analyze, and distribute threat intelligence from external feeds in near real time.

Kestra presents its Migration Assistant for VMware vRealize Automation and vRealize Orchestrator as an open-source local assessment tool intended to help organizations evaluate and plan migrations away from vRA/vRO, often prompted by licensing changes and poorly documented inherited workflows. The tool analyzes exported packages to inventory workflows, triggers, dependencies, integrations, and potential Kestra plugin support, then recommends whether each workflow should be retired, merged, wrapped, converted, or rebuilt and organizes remaining work into migration waves. The proposed approach emphasizes reducing scope by consolidating duplicates, retaining existing systems such as Ansible, Terraform, ServiceNow, and vSphere, identifying unused workflows, and replacing custom integration code where plugins provide equivalent functionality. Kestra recommends running vRA and Kestra in parallel, beginning with a proof of concept, reviewing generated flow conversions, testing in a simulated VMware environment, and cutting over workflow by workflow with rollback options. It argues that moving orchestration outside the VMware stack can improve portability, support broader integrations and AI tasks, and reduce costs, while noting that organizations should validate savings, licensing implications, and design choices around catalogs and infrastructure records for their own environments.