How is Kestra different from n8n?

n8n targets no-code API automation (connecting SaaS apps, webhooks, HTTP triggers). Kestra targets code-first data and ETL pipelines: YAML workflows, Python/SQL/Bash scripts, Docker task runners and reproducible execution history. Teams that want Git-managed pipelines with audit trails choose Kestra; those who want a drag-and-drop automator choose n8n.

Support

Automate business processes.

Kestra

Declarative YAML orchestration for data pipelines and ETL — self-hosted on your VPS, Apache-2.0, 15 k+ stars.

4 GB minimum (JVM-based); 8 GB recommended for Docker tasks RAM 2 vCPU minimum In validation

In validation

Automatic installation for this solution is ready and currently going through our tests on a real server. Ordering will open as soon as validation is complete.

Kestra is an open-source orchestration platform (Apache-2.0, 15 k+ stars) where every workflow is a versioned YAML file. It targets data and ETL pipelines, event-driven automation and scheduled tasks — the use cases where Python DAGs feel heavy and no-code tools feel limited.

Self-hosted on a VPS, Kestra runs as two containers: PostgreSQL 16 and the Kestra server in standalone mode. It exposes a polished web UI with a YAML flow editor, an execution timeline, real-time logs and a plugin browser. Over 600 plugins cover SQL databases (PostgreSQL, MySQL, BigQuery, Snowflake), cloud storage (S3, GCS, Azure Blob), scripts (Python, Bash, Go), HTTP APIs and Docker task runners.

Workflows are triggered by cron schedules, incoming webhooks, file detection or API calls. Each execution is fully logged — inputs, outputs, sub-task timings — and retryable with configurable back-off. Because Kestra can mount the Docker socket, workers can spin up isolated containers for each script, keeping the host clean and making data pipelines fully reproducible.

Key features

Everything-as-Code — workflows are YAML files, versionable in Git, reviewable in PRs, reproducible across environments.

600+ plugins — SQL, S3, Python/Bash/Go scripts, Docker, HTTP, cloud services and more, browseable from the UI.

Multiple trigger types — cron, webhook, API call, file detection; chain flows with sub-flows.

Docker task runner — each script runs in its own isolated container, keeping the host clean.

Full execution history — inputs, outputs, real-time logs, per-task timings and retry controls.

Topological view — visualise the dependency graph of any flow directly in the web editor.

Apache-2.0 licence — use, fork and distribute without restriction.

When to use this solution?

Data pipeline orchestration

Event-driven automation

Scheduled reporting

Deploy Kestra on your VPS

Guide optimized for ServOrbit Cloud VPS.

Deploy Kestra from the ServOrbit Marketplace

Go to Marketplace → Automation & Workflows → Kestra in your ServOrbit control panel and click Deploy. AWX provisions Docker, creates the PostgreSQL database, generates the required secrets, configures nginx and starts both containers automatically.

Open the Kestra UI

Navigate to your domain (or IP if no domain is attached). The Kestra dashboard opens directly — no login required by default. The first screen shows the Flows list, which is empty on a fresh install.

Create your first flow

Click New Flow, give it an id and a namespace (e.g. company.etl). In the YAML editor, add one task: io.kestra.plugin.core.log.Log with message: 'Hello Kestra'. Save and click Execute — you will see the execution appear in the timeline with its logs.

Add a scheduled trigger

Add a triggers section to the flow YAML with a io.kestra.plugin.core.trigger.Schedule cron expression (e.g. cron: 0 7 * * MON). Save the flow and verify that a scheduled execution appears in the timeline at the next cron tick.

Explore the plugin library

In the left sidebar, click Plugins to browse the 600+ available task types. Use the search to find the plugin for your use case: database connectors, cloud storage, scripting runtimes and API callers are all there with inline documentation and examples.

Frequently asked questions

No. Kestra is accessible via its VPS IP address on port 8080 without a domain. Adding a domain gives you a clean URL, TLS termination and nginx reverse proxy — recommended for any internet-facing instance.

Yes. Kestra mounts the Docker socket and can run any Docker image as a task via io.kestra.plugin.scripts.runner.docker.Docker. Each task runs in an isolated container with its own dependencies, keeping the host clean and making results fully reproducible.

Complementary solutions

Automation & Workflows

n8n

Automate your workflows across applications without code. Over 400 integrations, 100% self-hosted on your VPS.

Automation & Workflows

Activepieces

Open-source automation platform with 280+ connectors and an AI agent hub. Replace Zapier — unlimited flows, your data stays on your VPS, zero per-task billing.

Automation & Workflows

Node-RED

Node-RED is a flow-based automation tool that lets you connect APIs, IoT devices and webhooks in a visual editor. You build your scenarios by wiring together nodes, with no code to write. Self-hosted on your server, it gives you full control over your data and integrations, backed by an ecosystem of more than 4000 community nodes.

Automate business processes.

Kestra isn't orderable yet.

Automatic installation for this solution is ready and currently going through our tests on a real server. Ordering will open as soon as validation is complete.

Need help?

Browse our help center and FAQ, or write to our team — support in French, English and Arabic.

or write to us