Kestra 2.0 launch recap: what you actually get

Kestra 2.0, launched September 8, introduces a redesigned orchestration platform intended to unify data, infrastructure, application, and business-process workflows under one control plane, addressing fragmented ownership, audit trails, and governance across specialized tools. The release replaces Kestra 1.x’s separate JDBC and Kafka Streams engines with a single architecture that separates queues from repositories and adds a Controller, allowing workers to connect outbound through mutual TLS without direct database access and to run across clouds, on-premises systems, restricted networks, or air-gapped environments. It adds integrated case management for incidents, approvals, SLAs, remediation actions, and deployment promotion, creating audit trails that connect automated executions with human decisions. Kestra 2.0 also positions AI agents as governed tasks within workflows, supporting approval gates, MCP integrations, external tool calls, natural-language interaction with flows and logs, and publication of workflows as typed agent-callable tools. Existing 1.x users can retain their flows while using automated server migration, a YAML flow-rewriter CLI, migration documentation, and agent-assisted support for more complex changes; core engine, UI, editor, and plugins remain Apache 2.0, while Enterprise provides additional governance, backends, and multi-tenancy.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.