Kestra

Kestra is a declarative orchestration platform for building, running and governing workflows across an organization. Its workflows, called flows, are defined in YAML and can include tasks, dependencies, conditions, triggers and runtime parameters. Execution controls include retries, failure policies, timeouts, concurrency limits, worker assignment and log capture. Kestra advertises more than 2,000 plugins for connecting workflows to external tools, including AWS, Azure, GitHub, Kafka, Kubernetes, Slack and Snowflake. Flows can orchestrate SQL, Python, shell, APIs, Terraform, dbt, Spark and custom tools. An MCP server supports AI agents, and flows can be exposed as tools for agents to call. Teams can self-host with Docker or Kubernetes; Enterprise Edition also supports cloud, on-premises and air-gapped deployments. Enterprise features include SSO, audit logs, secret manager integration, end-to-end encryption, SCIM sync, multi-tenancy and role-based access control. Kestra Cloud advertises up to two months free while a team gets set up. The Open Source, Enterprise Edition and Cloud plan prices are not listed.

Kestra offers YAML-defined flows, broad tool connections and multiple deployment choices. Teams should compare the unpriced plan options and check which enterprise controls they need.

Kestra may suit teams coordinating workflows across different languages and external tools. Its deployment options and enterprise access controls may also suit organizations with specific hosting or governance needs.

Overview

Kestra is a workflow orchestration platform for technical teams coordinating jobs across tools and runtimes. It suits organizations comfortable defining workflow logic in YAML, while its visual builder offers another way to work. The mix of execution controls, integrations and deployment choices is compelling; teams should weigh the unpriced plan options and the need for enterprise governance.

Key features

Define and manage flows

Flows use YAML to specify tasks, dependencies, conditions, triggers and runtime parameters. That gives teams a structured way to describe complex work, but makes Kestra a less natural fit for organizations that want workflow creation to depend entirely on a visual interface. A visual workflow builder is available alongside YAML.

Retries, failure policies, timeouts, concurrency limits, worker assignment and log capture give operators ways to control execution and diagnose failures. Event triggers, execution observability and human approvals extend its use beyond simple scheduled jobs. These controls are valuable when workflows need to respond to events or require deliberate handling of errors and approvals.

Connect tools, runtimes and agents

Kestra advertises more than 2,000 plugins, with examples including Airbyte, AWS, Azure, BigQuery, dbt, Docker, GitHub, Kafka, Kubernetes, Slack, Snowflake and Terraform. It can orchestrate SQL, Python, shell, APIs, Terraform, dbt, Spark and custom tools within the same workflows. That breadth makes it a strong candidate for teams coordinating work across varied systems; organizations with a narrow, single-tool workflow may not need so much orchestration capability.

An MCP server supports AI agents, and flows can be exposed as tools for agents to call. This gives teams a way to connect agent activity to workflow execution, though the platform's broader case remains orchestration across systems and runtimes.

Pricing

Kestra's Open Source plan has custom pricing and includes declarative workflows, 1,200+ plugins, event-driven scheduling, and unlimited flows and executions. Its unlimited flow and execution allowance is attractive for teams that want to self-manage orchestration without a stated usage cap, while deployment and operations remain their responsibility.

Kestra Cloud has custom pricing, with fully managed hosting, automatic scaling, built-in security and governance, SOC 2 compliance, and a pay-as-you-scale model. It is the fit for teams that prefer managed operations and scaling over self-hosting. The cloud trial offers up to two months free with full access while a team gets set up.

Enterprise Edition has custom pricing and adds LDAP, SCIM, custom RBAC, SSO, audit logs, multiple tenants, worker groups and task runners, plus cloud, on-premises and air-gapped deployment. It is aimed at organizations with access-control, tenancy or deployment requirements beyond the open-source and cloud options. Enterprise also includes a customer success program and enterprise support with an SLA. Kestra identifies itself as released under the Apache 2.0 license.

Platforms

Kestra supports API, Linux, macOS, self-hosted, web and Windows environments. Docker and Kubernetes are self-hosting options, while Enterprise Edition also supports cloud, on-premises and air-gapped deployments. That hybrid range gives teams room to choose where workflows run, including environments with strict isolation requirements. Kestra Cloud advertises SOC 2 Type 1 and Type 2 and GDPR status through its Trust Center.

Who it's for

Kestra is best for technical teams coordinating workflows across multiple languages and external services, especially when they need execution controls or deployment flexibility. The Open Source plan suits teams prepared to manage their own infrastructure; Cloud suits those seeking managed hosting; Enterprise Edition is the relevant option for organizations needing SSO, auditability, multi-tenancy or air-gapped deployment. Teams seeking only a visual, low-complexity workflow tool may find its YAML-centered approach and broad platform unnecessary.

Pros and cons

• Pros: YAML flows combine tasks, conditions, triggers and runtime parameters, giving technical teams a consistent way to define workflow logic.
• Pros: More than 2,000 advertised plugins and support for varied languages help coordinate work across diverse systems.
• Pros: Retries, failure policies, timeouts, worker assignment and log capture provide practical control over execution.
• Pros: Self-hosted, managed cloud, on-premises and air-gapped options address a broad range of deployment needs.
• Cons: Teams that do not want to define workflow logic in YAML may find the platform less suitable, despite its visual builder.
• Cons: All three plan prices are custom, so teams cannot compare costs from the stated plan prices alone.
• Cons: Self-hosting the open-source option means taking responsibility for operating the platform.

Alternatives

For a free, open-source software platform, ONAP is a straightforward alternative; Kestra distinguishes itself with YAML-defined flows, a broad plugin catalog and multiple deployment choices.

AWS Step Functions is worth considering for teams looking for a free tier that does not automatically expire after the 12-month AWS Free Tier term. Kestra is the broader fit when workflows need its advertised plugin range, multiple runtimes or self-hosting.

Google Cloud Workflows offers an Always Free plan with monthly limits of 5,000 internal steps and 2,000 external steps, as well as a pay-as-you-go plan. Consider it when those limits suit the workload; Kestra offers unlimited flows and executions on its Open Source plan and can be self-hosted.

Orkes Conductor is another freemium workflow orchestration option.

Windmill offers a free and open-source plan with 3 workspaces, 50 users and 10 GiB of workspace object storage. Its stated workspace and user allowances may suit teams that want those defined caps; Kestra's Open Source plan instead states unlimited flows and executions.

StackStorm is a free, open-source alternative with no paid products offered by the project.

ActiveBatch is a paid IT orchestration alternative with custom pricing.

HCL Workload Automation is a paid enterprise workload automation option with a free trial and custom pricing.

Readers comparing the category can also browse IT Orchestration Software, DataOps Platforms, Workload Automation Software, Integration Platform as a Service Software and Workflow Orchestration Software.

Verdict

Kestra is a strong choice for technical teams that need to coordinate workflows across tools, languages and deployment environments, with execution controls that cover failure handling and runtime management. Its open-source plan's unlimited flows and executions and its Enterprise deployment range are meaningful strengths. Choose another option if a published price is essential to evaluation, or if YAML-centered workflow definition and operational breadth exceed what your team needs.