kestra vs Vibe-Skills

kestra is much bigger: 28.0k stars against 3.2k. Over the days we have tracked them kestra moved +4.1% and Vibe-Skills +41.1%, so Vibe-Skills is growing faster right now.

They split the axes: kestra leads on customization and setup ease, Vibe-Skills on context depth and noise control.

Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.

Where they stand today

An event-driven, open-source orchestration platform that combines a declarative YAML workflow model with a rich plugin ecosystem and a visual editor for building and running workflows across environments.

Stars
28.0k
Tracked growth
+4.1%
Maturity
Last commit
15h ago
Language
Java
License
Apache-2.0
Cost to run
Free, self-hosted

Orchestrates and verifies multi-step work by discovering and assigning local Skill modules and enforcing end-to-end checks with resumable state.

Stars
3.2k
Tracked growth
+41.1%
Maturity
Last commit
4d ago
Language
Python
License
Apache-2.0
Cost to run
Free, self-hosted
0%+41%90 tracked days
kestra-io/kestraforyourhealth111-pixel/Vibe-Skills

Six axes, head to head

Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.

AxiskestraVibe-Skills
Context depth
How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository.
Flow-level only
Whole-repo analysis
Noise control
How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only.
Real-time validation
Severity gating
Customization
How far it bends to your team: custom rules, prompts, style guides, per-path config.
Plugins & YAML
Config file options
Privacy
Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only.
Self-hostable
Self-hostable
Model freedom
Whether you can point it at any provider, or it is wired to one.
No model support
Single provider
Setup ease
What it takes to get a first useful run out of it.
One-command start
Config + docs

Which one to pick

Pick kestra if…

Easy setup — get a local instance with a single Docker command and build, visualize, and run workflows from the UI while keeping workflows declarative in YAML.

  • Customization: Plugins & YAML (5/5 against 3/5)
  • Setup ease: One-command start (5/5 against 3/5)
Runs in web-app, ci. Works with other-fixed.

Pick Vibe-Skills if…

Privacy-first — runs on your host and coordinates local Skill libraries to plan, execute, and verify complex multi-step tasks.

  • Context depth: Whole-repo analysis (5/5 against 1/5)
  • Noise control: Severity gating (5/5 against 3/5)
Runs in cli. Works with other-fixed.

What people want from each one

Questions people ask

Is kestra better than Vibe-Skills?

They split the axes: kestra leads on customization and setup ease, Vibe-Skills on context depth and noise control. kestra is worth picking when easy setup — get a local instance with a single Docker command and build, visualize, and run workflows from the UI while keeping workflows declarative in YAML.

Which of kestra and Vibe-Skills keeps my code private?

kestra: Self-hostable (5/5). Vibe-Skills: Self-hostable (4/5).

What does each one cost to run?

kestra: Free, self-hosted. Vibe-Skills: Free, self-hosted.

Full profiles: kestra-io/kestra and foryourhealth111-pixel/Vibe-Skills. Everything else in Workflow & graph engines.