Kestra logo

Kestra

Event-driven orchestration platform for scheduled and API-triggered workflows

27k Java Apache-2.0 6 days ago

Overview

Kestra is an open-source, event-driven orchestration and scheduling platform where workflows are defined declaratively in YAML and managed through a web UI. It handles data pipelines, automation, and microservice orchestration with a rich plugin ecosystem, retries, and a built-in scheduler. It overlaps with iPaaS for API-triggered and scheduled automation while scaling to data-engineering workloads.

Key features

  • Workflows defined declaratively in YAML
  • Event-driven, scheduled, and API-triggered execution
  • Web UI for building, running, and monitoring flows
  • Built-in scheduler with retries and error handling
  • Plugin ecosystem for integrations and tasks
  • Deploys via Docker, Docker Compose, or Kubernetes

Our take

Kestra sits in an interesting middle ground, flexible enough to act like an iPaaS for API-triggered and scheduled automation while scaling up to genuine data-engineering pipelines. Defining flows in declarative YAML keeps them version-controllable and reviewable, and the web UI plus built-in scheduler, retries, and plugin ecosystem make it productive without much custom code. The main thing to know going in is that this is an orchestration engine, not a no-code consumer tool like Zapier, so non-technical users will find the YAML-first model less approachable than a point-and-click builder. It's a JVM application, which means a heavier runtime footprint than lightweight scripting tools, so plan resources accordingly. A managed option is available if you'd rather not run the infrastructure yourself.

Ideal for: Data and platform engineers who want a single orchestrator for scheduled pipelines, API-triggered automation, and microservice coordination.

Where it falls short of Zapier

  • YAML-declarative workflows are more engineering-oriented than no-code Zapier flows.
  • Enterprise edition gates SSO, RBAC, multi-tenancy, audit logs, and worker isolation.
  • Connectors are plugins focused on data/infra systems rather than consumer SaaS apps.
  • Production self-hosting benefits from Postgres plus a queue, raising operational overhead.

We list the gaps honestly so you can decide if the trade-off is worth owning your data.

Tags

orchestration
scheduling
data-pipelines
yaml
self-hosted
Maintain Kestra?

Claim this listing to keep it accurate, add a deploy template, or feature it on relevant pages.

Show off your self-host difficulty score

Embed the Kestra difficulty badge in your README — it links back here.

Self-host difficulty badge← add this to your README
[![Self-host difficulty](https://openreplace.com/api/badge/kestra)](https://openreplace.com/kestra)

Similar open-source projects

Other self-hostable tools in the same space worth comparing.

Sponsored

Fair-code workflow automation with 400+ integrations and native AI nodes

115k TypeScript Sustainable Use License 4 days ago
2/5
1-click
Kestra vs n8n

Programmatically author, schedule, and monitor workflows as Python DAGs

46k Python Apache-2.0 4 days ago
4/5
Kestra vs Apache Airflow

Flow-based low-code programming for wiring together APIs, services, and devices

23k JavaScript Apache-2.0 6 days ago
2/5
Kestra vs Node-RED

MIT-licensed no-code automation and AI agents builder, an open Zapier alternative

23k TypeScript MIT 6 days ago
3/5
Kestra vs Activepieces