Kestra is an open-source, declarative orchestration platform that lets engineers describe workflows in YAML and connect them to 1,300+ plugins spanning data, infrastructure, APIs, and AI. We rate it 88/100 — the strongest modern Airflow alternative for teams that want orchestration without Python lock-in or a sprawling Helm chart.

What is Kestra?

Kestra was founded in 2019 by Ludovic Dehon and Loïc Mathieu in Paris after a decade of operating data pipelines on legacy schedulers. The team open-sourced the platform on September 15, 2019 under the Apache-2.0 license. The repository kestra-io/kestra now sits at 26,776 GitHub stars as of May 3, 2026, used across 30,000+ organisations including Leroy Merlin, Bouygues Telecom, Rivian, Decathlon and Doctolib.

The pitch is simple. Apache Airflow is Python-only and was designed for cron-driven batch jobs. Kestra is language-agnostic, event-driven by default, and treats workflows as declarative YAML — the same format your DevOps team already uses for Kubernetes, Terraform and GitHub Actions. In March 2026, Kestra raised a $25M Series A led by RTP Global, bringing total funding to $36M and pushing the platform toward unified orchestration of data, infrastructure and AI agents.

Kestra banner showing the declarative orchestration platform UI with a topology view, plugin catalog, and YAML editor — Kestra: declarative YAML on the left, live execution graph on the right — the same workflow definition runs locally, in Cloud, or on Enterprise.

Key Features of Kestra

1,300+ plugins out of the box: First-class integrations for AWS, GCP, Azure, Snowflake, BigQuery, dbt, Spark, Kafka, Postgres, OpenAI, Anthropic, Slack and more — every plugin is a versioned, isolated runtime.
YAML-first declarative workflows: Define a flow with id, tasks, triggers — Git-versionable, code-reviewable, deployable through Terraform, no DAG factories or Python decorators required.
Polyglot tasks: Run Python, Node.js, R, Shell, Julia, Rust, Go or Bash inside the same flow without leaving the YAML — Kestra spawns isolated container runtimes per task.
Event-driven triggers: Webhooks, S3 events, Kafka topics, file-watchers, Pub/Sub messages and database row changes can all start a flow — no cron required.
Unified UI for editing, lineage and tracing: Embedded code editor with autocomplete, real-time topology graph, blueprint catalog, and execution lineage all live at localhost:8080 after one docker run.
Backfills, retries and SLAs as first-class concepts: No need to reinvent retry logic — define retry, timeout and SLA blocks declaratively and Kestra handles the state machine.
AI Copilot and agent tasks: The 1.0 release added native LLM-driven flow generation and AI Agent tasks that let you build autonomous workflows with memory, tools and any model provider.
Single binary or Docker Compose deployment: One YAML file boots an entire production-shaped stack — API server, scheduler, workers, executor, indexer — no separate metadata DB to babysit.

Animated screenshot of the Kestra UI editor showing a user adding tasks to a flow with autocomplete and live topology preview — Adding tasks in Kestra's embedded editor — the topology graph updates in real time as you type YAML.

What Users Say About Kestra

Reaction across Hacker News, Reddit's r/dataengineering, and G2 is overwhelmingly positive but pointed. The recurring praise: teams report cutting orchestration setup from "a sprint of Helm charts" to a single afternoon, and non-Python contributors (analysts, platform engineers, ML researchers) can finally read and edit flows without learning Airflow's DAG idiom. On G2, one platform team reports a 98% pipeline success rate after migrating off Airflow. The recurring criticism: large Python codebases still end up pasted into script blocks inside YAML, which can feel awkward, and engineers used to writing imperative DAGs sometimes miss the flexibility of pure code. A second thread of feedback notes that the Enterprise pricing is opaque — there is no public price list, and several Reddit threads complain that you have to talk to sales to get a number.

Kestra Pricing

Kestra's open-source edition is free forever and includes every core orchestration feature. Cloud and Enterprise are the paid surfaces.

Plan	Price	Key Limits
Open Source	$0	Self-hosted, all 1,300+ plugins, unlimited flows and executions, community support
Cloud	Usage-based (request access)	Fully managed SaaS, automatic scaling, built-in security, Cloud SSO, multi-tenant
Enterprise Edition	Contact sales (annual subscription)	Adds RBAC, audit logs, LDAP, worker groups, plugin versioning, AI Copilot with custom models, Apps, SLA support

Who Should Use Kestra?

Best for: Data, platform and DevOps teams (5–500 engineers) running multi-language pipelines who want a single orchestration layer over data, infra and AI — especially anyone migrating off Airflow because they are tired of the Python-only DAG model, the metadata-DB upgrade pain, or the scheduler/executor/webserver split.

Not ideal for: Solo developers running a handful of cron jobs (a single GitHub Actions workflow is simpler), or teams deeply standardised on Airflow with thousands of existing DAGs where the migration cost outweighs the benefit. Also a poor fit if your entire workflow is one Python notebook — Prefect or Dagster will feel more natural.

Pros and Cons

Pros:

YAML-first design means flows are readable by everyone on the team — not just Python engineers.
1,300+ official plugins is the largest catalog in the open-source orchestration space.
Event-driven triggers (S3, Kafka, webhooks) work out of the box — no Sensor hacks.
Single Docker Compose stands up a production-shaped stack — no separate metadata database, scheduler, or webserver to wire up.
Apache-2.0 licensed and self-hostable forever — no rug-pull risk.

Cons:

Long Python scripts pasted into YAML script blocks can feel awkward versus a pure-Python DAG.
Enterprise pricing is opaque — no public price list, sales call required.
The Java backend means JVM tuning is occasionally necessary at very large scale.
Smaller community than Airflow — fewer Stack Overflow answers when you hit an edge case.

Alternatives to Kestra

The closest direct competitor is Apache Airflow, which has a larger community but is Python-only and operationally heavier. Prefect and Dagster are Python-native challengers with strong type systems but neither matches Kestra's polyglot or YAML approach. Temporal is the right pick for application-level workflows in code (Go, Java, TypeScript) rather than data pipelines. For lightweight automation, n8n and Windmill overlap on the low-code side but lack Kestra's enterprise orchestration depth.

Verdict: Is Kestra Worth It?

Yes — for any team running multi-language data, infrastructure or AI pipelines, Kestra is the strongest open-source orchestration platform on the market in 2026. The combination of a YAML-first declarative model, 1,300+ plugins, event-driven triggers and a single-binary deployment story makes it materially easier to operate than Airflow without giving up the production hardness Airflow is known for. We rate it 88/100 — the four points off reflect opaque Enterprise pricing and the fact that very Python-heavy teams may prefer Prefect or Dagster's pure-code model.

Frequently Asked Questions

Is Kestra free?: Yes. Kestra Open Source is free forever under the Apache-2.0 license, with every core feature, all 1,300+ plugins, and unlimited flows. Kestra Cloud is usage-based (request access) and Enterprise Edition requires a sales conversation.
Is Kestra open source?: Yes. Kestra is Apache-2.0 licensed and the source is on GitHub with 26,776+ stars as of May 2026. The Cloud and Enterprise editions add proprietary plugins and operational features on top of the open core.
What platforms does Kestra support?: Kestra runs anywhere the JVM does — Linux, macOS, Windows, Docker, Kubernetes, AWS, GCP and Azure. The web UI runs in any modern browser. Workers can be deployed in dedicated worker groups for sensitive workloads.
How does Kestra compare to Apache Airflow?: Kestra and Airflow are both production-grade orchestrators, but Kestra is YAML-first and language-agnostic while Airflow is Python-only with a code-defined DAG model. Kestra ships event-driven triggers as a first-class concept, includes 1,300+ plugins, and deploys with one Docker Compose file — whereas Airflow typically requires a separate scheduler, webserver, metadata DB and executor.
Does Kestra support AI workflows?: Yes. Kestra 1.0 added native AI Agent tasks and an AI Copilot that generates flows from natural language. The platform ships plugins for OpenAI, Anthropic, Google Vertex AI, AWS Bedrock and any custom LLM provider, so you can build agentic workflows with memory and tools entirely in declarative YAML.

#workflow

Dify

Kestra

React Flow