kestra vs oh-my-hermes

kestra is much bigger: 28.1k stars against 1.7k. Over the days we have tracked them kestra moved +4.1% and oh-my-hermes +84.2%, so oh-my-hermes is growing faster right now.

oh-my-hermes leads on context depth and model freedom. kestra does not take any axis by a clear margin.

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.1k
Tracked growth
+4.1%
Maturity
Last commit
19h ago
Language
Java
License
Apache-2.0
Cost to run
Free, self-hosted

Provides a local-first operating layer for Hermes that enforces explicit evidence boundaries and verification gates while keeping executors and provider access observable.

Stars
1.7k
Tracked growth
+84.2%
Maturity
Last commit
1h ago
Language
Python
License
MIT
Cost to run
Your API key, per-use
0%+84%90 tracked days
kestra-io/kestrarlaope/oh-my-hermes

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.

Axiskestraoh-my-hermes
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
Diff + related files
Noise control
How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only.
Real-time validation
Evidence gates
Customization
How far it bends to your team: custom rules, prompts, style guides, per-path config.
Plugins & YAML
Configurable workflows
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
Bring your own key
Setup ease
What it takes to get a first useful run out of it.
One-command start
One-command setup

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.

Runs in web-app, ci. Works with other-fixed.

Pick oh-my-hermes if…

Local-first control plane — pick OMH when you want an installable, evidence-first workflow catalog and gating layer for Hermes that keeps execution ownership explicit and configurable.

  • Context depth: Diff + related files (3/5 against 1/5)
  • Model freedom: Bring your own key (5/5 against 1/5)
Runs in cli, coding-agent-plugin, web-app. Works with byok.

What people want from each one

Questions people ask

Is kestra better than oh-my-hermes?

oh-my-hermes leads on context depth and model freedom. kestra does not take any axis by a clear margin. 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 oh-my-hermes keeps my code private?

kestra: Self-hostable (5/5). oh-my-hermes: Self-hostable (4/5).

What does each one cost to run?

kestra: Free, self-hosted. oh-my-hermes: Your API key, per-use.

Full profiles: kestra-io/kestra and rlaope/oh-my-hermes. Everything else in Workflow & graph engines.