Pricing guide

Kestra Cloud or Kestra Enterprise?

Both give you the same orchestration engine and 2,300+ plugins. The difference is who runs Kestra, where it runs, and how you pay for it.

Kestra Cloud Fits most teams

We run Kestra for you

Fully managed by Kestra. Nothing to deploy, upgrade or back up.

$500/mo, billed yearly

$625/mo billed monthly. Includes 10,000 task runs, 1,000 compute minutes, SSO and RBAC every month, then you pay for what runs.

Why teams choose it

  • No platform to staff. Upgrades, scaling, backups and uptime are ours.
  • Costs follow usage. Start small and pay for what runs, with no capacity to buy up front.
  • Value in days. A 14-day trial on your own flows, with no infrastructure project.
  • Security reviewed. SOC 2 Type 2 and GDPR.
Estimate your price Start a 14-day free trial
Kestra Enterprise

Kestra where you need it

Self-hosted or hybrid, in your private cloud or air-gapped.

Custom

Set in your contract. Talk to us for a quote.

Why teams choose it

  • Your environment, your rules. Data and deployment stay inside your network, air-gapped if needed.
  • Fits what you already run. Your directory, secret managers and SIEM.
  • 24/7 support. Response times and SLA set in your contract.
  • A contract built around you. Pricing and terms tailored in a proposal.
Talk to sales

Not sure yet? Answer four questions.

Can Kestra reach your systems over the internet?Public endpoints, or through an IP allowlist
Do you need LDAP, SCIM or strict governance?LDAP, automatic user provisioning (SCIM), hard isolation between teams, audit logs, dedicated storage
Do you keep your secrets in an external manager?Vault, AWS, GCP, Azure, 1Password, Doppler, Bitwarden or CyberArk. If not, secrets are stored in Kestra.
Do you have the people and skills to run Kestra yourselves?Someone with the time to handle upgrades, scaling, backups and monitoring

Data residency, a specific region or compliance needs such as HIPAA? Tell us early: it can change the setup.

Our suggestion
Kestra Cloud

Estimate your price
Kestra Cloud

Estimate your monthly price

Fill in what you know. The estimate updates as you go, and you can share a link to it.

1

How many task runs a month?

One task run is one step of a workflow, each time it runs. Loops, conditions, triggers and schedules are not counted. How it's counted

task runs / month
Included (first 10,000)Billed per run

Not sure? Pick the example closest to you. Each one is based on a real Kestra Cloud account.

2

Where do your scripts run?

Only Python, Shell, Node.js, dbt CLI or Terraform scripts on Kestra's task runner use compute. Plugin tasks never do.

3

Environments and limits

Start with the defaults. Most teams change these later, if at all.

InstancesA separate Kestra, for example dev and prod. 1 included, then $300/mo each.
1
TenantsIsolated workspaces inside an instance. 1 included, then $200/mo each.
1
Task runs at the same timePer instance. Extra runs wait in a queue, they don't fail.
Execution history7 days included on each instance. Longer retention is set up with our team.
Talk to sales
Side by side

What each edition includes

Feature Kestra Cloud$500/mo billed yearly, plus usage Kestra EnterpriseCustom pricing
Where it runs
Fully managed by KestraWith Kestra Cloud
Self-hosted, private cloud or air-gapped
Workers on your own infrastructure (hybrid)Talk to sales
Capacity per month
Task runs10,000 includedThen from $0.02 each, less at volumeSet in your contract
Compute on Kestra's task runner1,000 min includedAt size S. Beyond that and for larger sizes, billed per second.Set in your contract
InstancesA separate Kestra, for example dev and prod1 includedMore: $300/mo eachSet in your contract
TenantsIsolated workspaces inside an instance1 includedMore: $200/mo eachSet in your contract
Task runs at the same timePer instance. Extra runs queue, they don't fail8 includedOr 16, 32 or 64Set in your contract
Execution historyPer instance7 days included30, 90 or 365 days: talk to salesSet in your contract
Platform
2,300+ plugins, any language
AI Copilot to write and fix flows
Unit tests and versioned plugins
Custom blueprintsReusable flow templates for your team
Log shippingSend logs to the observability stack you already use
Apps for non-technical teammates
Upgrades, scaling and backupsHandled by KestraHandled by your team
Security and governance
SSO and RBAC
Unlimited users and custom roles
SCIM provisioningTalk to sales
LDAPUse SSO or SCIM
External secret managersVault, AWS, GCP, Azure, 1Password, Doppler, Bitwarden, CyberArkTalk to sales
Audit logs and SIEM export, dedicated storage, worker isolationTalk to sales
Support
Standard supportIncluded99% uptimeP0: answered within 12hP1: within 24hP2 and P3: best effortHours: weekdays, 08:00 to 18:00, Central European or US Eastern timeTailored support contract
Premium supportTalk to sales
Talk to sales Available on Kestra Cloud through a conversation with our sales team.
Usage on Kestra Cloud

What counts as a task run, and when you pay for compute

A task run is one run of one task, not one run of a whole flow. Scripts on Kestra's task runner are also billed for their minutes.

Usage by kind of task

Failed runs count the same as successful ones. Skipped and cancelled tasks don't count.

Kind of taskTask runsCompute
Plugin tasks that call a serviceBigQuery, Snowflake, HTTP, Slack, S3, dbt Cloud1 per runNone
Scripts on Kestra's task runnerPython, Shell, Node.js, dbt CLI, Terraform1 per runBilled per second
Scripts sent to your own cloudAWS Batch, Google Batch, Azure Batch, Kubernetes1 per runNone
Flow control and triggersLoop, Parallel, If, Switch, Subflow, Pause, schedules, webhooksFreeNone

Example: one flow, step by step

How a real flow adds up over a month.

StepTask runsCompute
3 plugin tasksA query, an API call, a Slack message30
One task in a Loop over 500 itemsThe Loop is free; the task counts once per item+5000
One item fails and is retried onceEvery attempt counts+10
Trigger a 30 min dbt Cloud jobIt runs on dbt Cloud, not on Kestra+10
A Python script that runs 62 minOn Kestra's task runner, size S+1+62 min
One execution50662 min
Run daily, 30 times a month15,1801,860 min
≈ $621/mobilled yearly, or ≈ $746 billed monthly
Why are scripts billed by duration?

A plugin task does one thing on another service's infrastructure. A script runs on Kestra's machines and can do any amount of work, so its time on the runner is measured and billed per second, per attempt, at the runner size you pick (S by default). Waiting or polling inside a script counts as running. The first 1,000 minutes at size S are included each month. At size S, $0.02 a minute is $0.000333 a second.

How do loops, retries and subflows count?

The Loop itself is free; the tasks inside it count once per item, and a script inside a loop starts one runner per item. Every retry is a new task run, and a new runner for scripts. Calling a subflow costs only the tasks inside the child flow.

Should I use plugins or scripts?

Use a plugin wherever one exists. There is no code to maintain, and the work runs on the service the plugin calls, so it uses no Kestra compute. Browse the 2,300+ plugins. Missing one? Open a feature request.

How do I check my real usage during the trial?

Open Tenant → System Overview for usage over time. It is computed differently from billing, so read it as an approximation. For the exact count of one run, open the execution: every task run is listed with its state and attempts, and a task that used Kestra's runner shows a taskRunner entry in its outputs. Your invoice is the final total.

Coming from another tool?

Turn 30 days of your current usage into task runs

Pick the tool you use today to see which of its numbers to look at, and how it maps to Kestra.

Let a coding agent do the counting

If your tool has a CLI, an API or a database you can query, a coding agent can read your workflows and 30 days of history and return your task runs and compute minutes. It asks before it runs anything, and works read-only.

  1. Copy the instructions, or download them as a skill file.
  2. Open your agent where it can see your workflows.
  3. Paste them and ask, for example: Estimate our Kestra Cloud usage from our Airflow setup.

Try it on your own flows

14 days free. Two or three workflows usually make up most of the volume, and we can review them with you during the trial.

Start a 14-day free trial Talk to sales