Kestra 2.0 Released: New Engine & Workers Anywhere
Kestra 2.0 launches with a major engine rewrite, splitting into control and data planes for secure cross-network workers, while maintaining its Apache 2.0 license.

Stock photo for illustration only, not from the actual event
- Kestra 2.0 introduces a redesigned architecture splitting the control plane and data plane.
- Workers connect via a secure, outbound-only gRPC stream without database credentials.
- Kafka Streams engine is removed, allowing independent queue and repository selection.
- The core engine, UI, and plugins remain fully open source under Apache 2.0.
Ever since its initial release in February 2022, the open-source orchestration platform Kestra has evolved by listening closely to real-world deployment feedback. While the early version relied on a heavy combination of Kafka and Elasticsearch, the project quickly adapted by introducing a JDBC backend just four months later to simplify deployments.
Building upon years of operational insights, Kestra 2.0 officially shipped this month with a major rewrite of its core engine. In previous 1.x versions, every worker required a direct connection to the central database, creating severe deployment hurdles for security teams managing restricted enterprise networks.

Stock photo for illustration only, not from the actual event
The new 2.0 release resolves this by cleanly separating the platform into a control plane and a data plane. The control plane houses the executor, scheduler, webserver, indexer, and a new worker controller—none of which execute user code. Meanwhile, workers operate exclusively within the data plane where tasks are safely processed.
Workers now maintain a single persistent gRPC stream initiated entirely from the worker side. Because no inbound connections are required and workers hold no database credentials, they can securely execute tasks across different clouds, separate regions, or inside strict outbound-only on-premise networks.
Splitting orchestration into control and data planes via secure gRPC streams reflects modern cloud-native design patterns, enabling strict network isolation and enhanced security compliance for enterprise environments.
Additionally, internal technical debt was addressed by removing the Kafka Streams engine and allowing users to pair queues and repositories independently. The platform continues to rely on declarative YAML configurations while keeping business logic decoupled from orchestrator code.
"We know a major version is where projects usually change it. We did not, and we do not plan to. The engine, the UI and all the plugins stay Apache 2.0."
Kestra Team
Reaffirming its open-source commitment, the team confirmed that the core engine, UI, no-code editor, and plugins remain under the Apache 2.0 license as an LTS release, ensuring a reliable upgrade path for users who have powered billions of production executions worldwide.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment