--- title: kestra Reviews meta_title: 'kestra Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 25 reviews by the users' company size, role or industry to find out how kestra works for a business like yours. aggregate_rating: rating_value: 4.6 review_count: 25 scale: '5' date_modified: '2026-11-16' parent_category: name: IT Infrastructure url: https://www.g2.com/categories/it-infrastructure ---

kestra Reviews & Product Details

Profile Status

This profile is currently managed by kestra but has limited features.

Are you part of the kestra team? Upgrade your plan to enhance your branding and engage with visitors to your profile!

User Insights

Average based on 25 real user reviews.

kestra Reviews (25)

Reviews

kestra Reviews (25)

4.6
25 reviews

What do users say?

Generated using AI from real user reviews

Pros & Cons

Generated from real user reviews
View All Pros and Cons
Search reviews
Filter Reviews
Clear Results
G2 reviews are authentic and verified.
Yingquan L.
YL
Yingquan L.
Founding Engineer (Stealth Energy Startup)
Small-Business (50 or fewer emp.)
"Kestra Makes Workflow Automation Effortless; Very Intuitive YAML Structure and Excellent Support!"
4.5/5
What do you like best about kestra?

What I like best about Kestra is the ability to build workflows for almost anything. I was able to build a workflow for one of my use cases: PostgreSQL to DuckDB replication with a full/incremental strategy. The progress to build a workflow is intuitive because it’s all defined with YAML. The UI allowed me to test the YAML quickly and isolate where the pipeline broke. I was able to quickly fix the YAML mistakes given the extremely helpful Kestra logging and error comments. Moreover, Kestra has integrated an AI feature and that makes writing the YAML much easier with boilerplate as opposed to writing everything from scratch. This workflow is great because doing the migration manually is a 70% less efficient way to do it.

This workflow can be integrated into both PostgreSQL and DuckDB easily through APIs. I think scaling it out to hundreds of GBs of data if not Terabytes of data is no problem at all. I’m very impressed with Kestra because of its pricing and more over its excellent product support and developer advocates who are extremely responsive. I’m very impressed with the Kestra product and team! Review collected by and hosted on G2.com.

What do you dislike about kestra?

Honestly, I really don’t have much to dislike about Kestra. I think it’s an excellent product. The only thing that could be enhanced is making the documentation more easily searchable. Aside from that, really nothing. The Kestra team has a product that really solves users’ data engineering and big data challenges, such as my DuckDB use case. When a product solves real customer needs, it will always have a standing in the market. Review collected by and hosted on G2.com.

Khushal A.
KA
Khushal A.
GSoC'26 Contributor
Small-Business (50 or fewer emp.)
Originally submitted 6/9/2026
"The Adamantium to my fragile AI pipeline"
4.5/5
What do you like best about kestra?

What I like most about Kestra is how it separates the data infrastructure from the AI reasoning layer.

First, the visual UI gives excellent observability. When a real-time event fails, I do not have to search through messy terminal logs. The topology and Gantt views show the exact execution flow step by step. I can click into a failed task, inspect the exact JSON payload or API error, and fix it immediately.

Second, the AI agent plugin allows you to expose infrastructure tasks directly to the model as tools using only YAML. For example, I exposed a PostgreSQL database query and a background web scraper subflow as tools to Gemini. The model can autonomously choose to run a database search, or trigger the scraping subflow if the database returns zero results. Kestra manages the state transitions, connections, and retries behind the scenes without requiring custom Python wrappers.

Finally, it is highly resource efficient. I develop on an older laptop with less than 6 GB of available RAM. Kestra runs smoothly as a standalone server with a small memory footprint, allowing me to build high-throughput, event-driven automation without overloading my system hardware. Review collected by and hosted on G2.com.

What do you dislike about kestra?

I don't particularly dislike something in Kestra, it's a great tool and moreover it is open-source. It just needs some improvements and everything will be really great. For instance, When I was writing code in Pebble template, I got confused when passing complex JSON outputs from an AI model into downstream python script or SQL query, managing quotes and data types requires a lot of trial and error. The parser errors can be hard to read at first.

And other improvement is tracking asynchronous tasks in the UI needs better visual connection. If an AI tool triggers a background subflow without waiting for it to finish, the main topology map does not show that child flow. You have to open separate tabs to track the full execution path. Review collected by and hosted on G2.com.

Deemanth G.
DG
Deemanth G.
developer
Small-Business (50 or fewer emp.)
"Exceptional Orchestration for Resilient, Self-Healing Data Pipelines"
4/5
What do you like best about kestra?

Kestra’s ability to orchestrate self-healing data pipelines is exceptional. I heavily utilize native features like pluginDefaults and polymorphic triggers to build resilient architectures. It goes beyond simple task scheduling; it acts as an automated guardian for our application's data layers, seamlessly handling memory-cached data and integrating flawlessly with local AI agents. Review collected by and hosted on G2.com.

What do you dislike about kestra?

The learning curve for some of the more advanced templating can catch you off guard. During initial setup, we ran into some frustrating Jinja2/Pebble bracket collisions. We also had to spend extra time engineering around DuckDB write contention when scaling the pipeline. It requires a solid understanding of the underlying architecture to optimize perfectly. Review collected by and hosted on G2.com.

Ayan G.
AG
Ayan G.
Open Source Developer | Hacktoberfest'25
Small-Business (50 or fewer emp.)
"Replaced my entire bug triage pipeline with Kestra"
5/5
What do you like best about kestra?

The thing I keep coming back to is the AIAgent plugin with native MCP tool support. I built a Discord forum triage bot: new bug report comes in, Kestra fires, an agent runs semantic search across GitHub and Discord via Coral MCP, decides if it's a duplicate or new, and acts on it. All of that is one YAML file.

Plugin coverage is solid. GitHub issue creation, a KV store for per-guild config, parallel HTTP calls to Discord's API, JSONStructuredExtraction for pulling structured fields out of AI output. Stuff I'd normally spend a day wiring up is just a few lines in the flow.

There was a real race condition where two upvote reactions landing simultaneously would both try to file a GitHub issue. behavior: QUEUE, limit: 1 fixed it. Literally one line in the YAML. I wasn't expecting that to be so clean.

Everything's in git, flow changes go through PRs, and the whole thing deploys with a single docker run on a server I already own. No extra cost, nothing new to maintain. For a side project running on existing infrastructure, that's kind of the whole point. Review collected by and hosted on G2.com.

What do you dislike about kestra?

There's no Discord plugin, so everything goes through the HTTP request task. Every action, posting a message, adding a reaction, archiving a thread, is a REST call you write yourself. It's more verbose than it needs to be, but you also never get stuck waiting on a plugin to expose something it doesn't.

The WebSocket gap is the more honest complaint. Discord's gateway runs over WebSocket, and Kestra is built around stateless webhook-triggered flows, not persistent connections. I ended up building a small Node.js bot just to bridge them: it holds the connection and forwards events as webhook calls. That's an extra thing to run and maintain. Though I'll say, it turned into a cleaner split than I expected. The bot owns the real-time protocol layer, Kestra owns everything else. I don't really think of it as a workaround anymore. Review collected by and hosted on G2.com.

Shivam K.
SK
Shivam K.
Frontend Developer
Small-Business (50 or fewer emp.)
"Kestra Handled the Plumbing So I Could Focus on the Actual Problem"
5/5
What do you like best about kestra?

I built a post-deploy security agent with Kestra that scans package dependencies, monitors live browser network requests using Playwright, and rolls back Vercel deployments automatically when something looks unsafe.

The biggest thing Kestra helped with was removing all the boilerplate. Scheduling, webhook validation, running Docker containers as tasks, passing values between flows using KV Store, Slack notifications, HTTP calls to Gemini and Vercel APIs, all of that was just a task type and a few YAML lines. None of it needed custom code. The actual work stayed focused on the scan logic and rollback decision, not the infrastructure around it.

The execution visibility also made a real difference. When something broke, I could see exactly which task failed, what it returned, and where the flow stopped. That made debugging much faster than digging through terminal logs. Review collected by and hosted on G2.com.

What do you dislike about kestra?

The YAML expression syntax has a real learning curve. Referencing task outputs, using Pebble expressions correctly, and understanding when a condition expects a string versus a boolean, these are small things, but they slow you down until they click. More real-world examples in the docs covering these patterns would help a lot. Review collected by and hosted on G2.com.

Rahil A.
RA
Rahil A.
Student
Small-Business (50 or fewer emp.)
Originally submitted 6/5/2026
"Reliable Workflow Orchestration for AI Projects"
5/5
What do you like best about kestra?

I used Kestra while building AI workflow projects like API Roulette, where multiple APIs, AI-generated outputs, and asynchronous tasks needed to coordinate reliably. It helped me move away from messy backend scripts into structured workflows with retries, execution tracking, logging, and DAG-based visibility. I especially liked the workflow observability features, since watching executions through DAGs, logs, retries, and task outputs made debugging much easier compared to traditional scripts.

The Docker setup and onboarding experience felt very smooth, and integrating Kestra with REST APIs and AI workflows was straightforward. Performance during local development was also surprisingly good even with larger multi-step workflows. Since retries, scheduling, logging, and monitoring are already built in, it reduced the need for extra backend tooling and made the overall development experience much cleaner.

For the features and workflow visibility Kestra provides out of the box, I feel it delivers a lot of value, especially for automation and AI workflow projects that would otherwise require much more custom backend setup. Review collected by and hosted on G2.com.

What do you dislike about kestra?

The only thing I’d improve is having more advanced AI orchestration and multi-agent workflow examples in the documentation. The core experience itself was smooth, but more real-world AI automation templates and architecture examples would make it even easier to explore larger workflow systems. Review collected by and hosted on G2.com.

Sahil S.
SS
Sahil S.
Events Lead
Small-Business (50 or fewer emp.)
"Powerful Orchestration & Observability with a Plugin Ecosystem That Just Works"
4/5
What do you like best about kestra?

The orchestration and observability you get for free. I built a full Telegram to Claude AI to Google Sheets receipt pipeline (ReceiptBot) as a single Kestra flow, and the things I would normally hand-write, like conditional branching, retries, and error handling, were just declarative YAML. The error block meant a failed step automatically stopped, logged, and notified the user without any try/catch boilerplate.

On UI/UX, the topology view makes the whole pipeline legible at a glance, and the per-run execution traces are the feature I keep coming back to. Every run logs inputs, outputs, duration, and per-task state, so debugging an unexpected API response takes seconds instead of print-statement archaeology.

On integrations, the plugin ecosystem covered everything I needed. Native Telegram, generic HTTP request and download, and polyglot Python scripts as first-class tasks meant I never hit a wall where Kestra

could not talk to a service.

On AI and intelligence, wiring a Claude Sonnet 4.6 vision call into the flow was just another HTTP task. Kestra handled the image download, base64 handoff, and the structured JSON response cleanly, which made

adding an AI step feel no different from any other integration.

On performance, a full receipt goes from photo to spreadsheet in about four seconds end to end, and Kestra adds negligible overhead on top of the actual API latency. Review collected by and hosted on G2.com.

What do you dislike about kestra?

The Pebble templating layer has a learning curve, especially when passing data into Python scripts. Because Pebble and Python both use curly braces, you can hit parser errors until you learn to hand off larger values through environment variables. Returning structured data from a script also relies on a specific output convention that is not obvious until you find it in the docs.

On support and onboarding, the core docs are solid but a few real-world patterns are under-documented. The exact webhook trigger URL is not surfaced in the UI, so you assemble it from the tenant, namespace, flow, and trigger key yourself. Secrets in the open-source edition are injected as base64-encoded environment variables with no UI, which works but is clunkier than the cloud secrets manager. None of these are blockers, but they make the first run harder than the polished first impression suggests. Review collected by and hosted on G2.com.

Shaik D.
SD
Shaik D.
student
Small-Business (50 or fewer emp.)
"Automation Made Scalable and Reliable"
5/5
What do you like best about kestra?

What I like most about Kestra is the way it balances **simplicity with extensibility**. At first glance, you can build flows using core tasks like logging or HTTP requests, which feels very straightforward. But the real magic is in the **plugin ecosystem**: over a thousand connectors that let you query databases, run scripts in multiple languages, interact with cloud platforms, and send notifications through tools like Slack or Teams. As a result, you can orchestrate almost any workflow without having to reinvent integrations or maintain a lot of custom glue code.

Another standout for me is its **language‑agnostic approach**. You’re not locked into a single runtime—whether you prefer Python, Shell, or Go, Kestra lets you embed that directly into your flows. That kind of flexibility is especially appealing for teams working across diverse stacks.

Finally, I appreciate the **blueprints**: ready‑made templates that demonstrate how to combine plugins for real‑world use cases. They help reduce the overwhelm that can come with so many options and give you a practical place to start.

*"Kestra’s plugin ecosystem is its superpower — it turns orchestration into integration without friction, while blueprints make adoption smooth."* Review collected by and hosted on G2.com.

What do you dislike about kestra?

Kestra is powerful, but the sheer number of plugins-along with the YAML learning curve-can feel overwhelming at first. Clearer, more comprehensive documentation and stronger plugin governance would go a long way toward making adoption smoother and reducing the initial friction. Review collected by and hosted on G2.com.

shubham k.
SK
shubham k.
Full-stack Developer
Small-Business (50 or fewer emp.)
"Clean UI, YAML Workflows, and Fast Troubleshooting with Kestra"
4/5
What do you like best about kestra?

What I like most about Kestra is its clean UI and the ease of building workflows with YAML. The execution logs and monitoring features make troubleshooting much faster, which saves a lot of time during development.

Kestra integrates well with different tools and services, making it easy to automate end-to-end processes from a single platform. I've found it reliable and responsive even when running multiple workflows.

The documentation and Kestra Fundamentals course made onboarding straightforward. One thing I didn't expect was how quickly I could start experimenting with AI-powered workflows by connecting external AI services into automated pipelines.

From a productivity standpoint, Kestra has reduced manual work and helped organize automation in one place, providing a good return on the time invested in setting it up and learning it. Review collected by and hosted on G2.com.

What do you dislike about kestra?

One area where Kestra could improve is the learning curve for users who are new to workflow orchestration and YAML-based configurations. While the documentation is helpful, some advanced use cases can take time to understand.

I would also like to see more built-in templates, AI-focused examples, and integration guides to help users get started faster. In some cases, troubleshooting complex workflows requires digging through logs and documentation, which can be challenging for beginners.

That said, these are relatively minor issues, and the platform continues to improve with new features and community resources. Review collected by and hosted on G2.com.

BAVYA S.
BS
BAVYA S.
Site Reliability Engineer (SRE)
Enterprise (> 1000 emp.)
"From Idea to Workflow in Minutes"
5/5
What do you like best about kestra?

What impressed me most about Kestra is how quickly it allows you to model real-world workflows without building custom orchestration logic from scratch. While building Trinetra, an emergency escalation workflow, I was able to implement webhook-triggered execution, timers, conditional branching, and observability using a declarative workflow definition. The visual topology and execution views made it easy to understand, debug, and validate workflow behavior. As someone exploring workflow orchestration, I found Kestra both beginner-friendly and powerful enough to handle practical automation use cases. Review collected by and hosted on G2.com.

What do you dislike about kestra?

As a beginner, the biggest challenge was understanding the large number of available plugins and identifying the best workflow patterns for a given use case. Additional end-to-end examples and real-world reference architectures would make it even easier for new users to get started. Overall, the learning experience was still very positive. Review collected by and hosted on G2.com.

Pricing

Pricing details for this product isn’t currently available. Visit the vendor’s website to learn more.

kestra Features
Cross-system Integration
Self-service
Automated workflows
Data Observability