Overview

Kestra is a declarative platform for coordinating workflows across teams and tools. It suits technical teams that want to combine varied runtimes and govern execution centrally. Its breadth is a strength; teams that need enterprise access controls should compare the Enterprise Edition with their requirements.

Key features

Workflow definition and execution

Flows are written in YAML, with tasks, dependencies, conditions, triggers and runtime parameters. A visual workflow builder is also available, but YAML remains central to how flows are defined, making Kestra a better fit for teams comfortable expressing workflow logic in configuration than for those seeking a purely visual authoring model.

Retries, failure policies, timeouts, concurrency limits, worker assignment and log capture give teams control over execution behavior and failures. Event triggers, execution observability and human approvals broaden its use beyond basic job scheduling. These controls are useful when workflows need explicit handling of errors, parallel work or human intervention.

Integrations, 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 coordinate SQL, Python, shell, APIs, Terraform, dbt, Spark and custom tools in the same workflows. That range can reduce the need to split cross-tool processes among separate orchestrators, though teams should confirm that their specific connectors fit their stack.

An MCP server lets AI agents call exposed flows as tools. This gives teams a route to make existing workflows callable by agents without limiting Kestra to AI use cases; the platform also covers conventional orchestration.

Pricing

Kestra offers Open Source, Enterprise Edition and Kestra Cloud plans, with custom pricing for the paid editions. The Open Source plan includes declarative workflows, 1,200+ plugins, event-driven scheduling, and unlimited flows and executions. It is the natural starting point for teams that can self-manage and do not require the enterprise access controls or managed hosting.

Enterprise Edition adds LDAP, SCIM, custom RBAC, SSO, audit logs, multiple tenants, worker groups and task runners, and supports cloud, on-premises and air-gapped deployment. Enterprise support with an SLA and a customer success program make it the relevant choice for organizations needing those controls and support commitments.

Kestra Cloud provides fully managed hosting, automatic scaling, security and governance, SOC 2 compliance, and a pay-as-you-scale model. It advertises up to two months free with full access while a team gets set up. That trial makes it possible to evaluate the managed option before committing; ongoing costs depend on scale.

Platforms

Kestra has a hybrid deployment model. Teams can self-host with Docker or Kubernetes, while Enterprise Edition also supports cloud, on-premises and air-gapped environments. Setup instructions cover macOS, Windows and Linux; the platform also lists API and web support. Kestra Cloud advertises SOC 2 Type 1 and Type 2 and GDPR status through its Trust Center.

Who it's for

Kestra is a strong candidate for engineering, data and operations teams coordinating workflows across languages, platforms and external services. Its YAML definitions and execution controls suit teams that want explicit, governable workflows; the visual builder and human approvals can support broader participation. Organizations needing SSO, audit logs, multi-tenancy or an SLA should consider Enterprise Edition rather than assuming the open-source plan covers those needs.

Pros and cons

Pro: Broad plugin coverage and support for multiple languages make it practical to coordinate work across a varied stack.
Pro: Retries, failure policies, timeouts, concurrency controls, worker assignment and logs provide concrete execution management.
Pro: Self-hosting and enterprise deployment options accommodate teams with different infrastructure and isolation needs.
Con: YAML-centered flow definitions favor technical authors; a visual builder is available, but does not remove that core orientation.
Con: Enterprise access controls and support commitments are tied to Enterprise Edition, which uses custom pricing.
Con: Cloud uses a pay-as-you-scale model, so teams should assess expected scale when choosing managed hosting.

Alternatives

Choose AWS Step Functions if an indefinitely available free tier and API or web access fit better; its free tier does not expire with the 12-month AWS Free Tier term. Google Cloud Workflows is worth considering for its Always Free monthly allowances of 5,000 internal and 2,000 external steps, or its pay-as-you-go plan.

Orkes Conductor offers a free Developer Edition with OSS and enterprise features. Temporal is another option for teams considering a free plan and usage-based pricing; its Pay-As-You-Go plan has no base monthly fee and includes $150 in credits for 90 days. Windmill may suit teams for whom its free plan's limits of three workspaces, 50 users and 10 GiB of workspace object storage are a fit.

StackStorm is a free, open-source alternative. ActiveBatch and BMC Helix AIOps are paid alternatives.

Verdict

Choose Kestra if your team needs one platform to orchestrate work across languages and tools, with both execution controls and flexible deployment. Look elsewhere if you need a purely visual workflow model or if Enterprise Edition's custom pricing and feature tier do not suit your access-control requirements.

	Cleo Integration Cloud	Kestra
Free plan	No	Yes
Free trial	No	Yes
Paid from	—	Free
Open source	No	No
Platforms	Web	api, Linux, macOS, self-hosted, Web, Windows
Free plan	—	Yes
Deployment model	—	hybrid

Cleo Integration Cloud vs Kestra

Cleo Integration Cloud

Kestra