← Back to home
Comparison · Infra & APIs

Node-RED vs Windmill

A side-by-side editorial comparison of Node-RED and Windmill — release velocity, themes, recent moves, and the top alternatives to consider.

Node-RED vs Windmill: at a glance

FeatureNode-REDWindmill
SectorInfra & APIsInfra & APIs
Velocity score5.06.3
Sparks · 30d01
Top themeslow-code, node-red-5, maintenance, dual-branchdeveloper-platform, ai-agents, evaluation, workflow-orchestration
Last editorial update21h ago1d ago
WebsiteVisit →Visit →

What is Node-RED?

Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.

Node-RED shipped 5.0 in June 2026 after a long beta, raising the runtime floor to Node.js 22.9, and the work since has been stabilisation. This pair patches both lines within ninety minutes: 5.0.5 fixes group fill defaults and opacity, an uncaught exception in the json node on malformed input with a schema, tlsConfigDisableLocalFiles, and multiplayer event property validation; 4.1.14 takes the multiplayer fix, a themes locale lookup error, and the same dependency work. JSONata 2.2.2 lands on both lines, the version that was reverted in July after a behaviour regression.

Read the full Node-RED trajectory →

What is Windmill?

Windmill gives its AI agents a test harness, the piece that lets them into production flows

Windmill is a developer platform for scripts, flows and internal apps, shipping weekly across three lanes. The AI lane is the busiest: sessions that build scripts and flows as reviewable drafts, a read-only plan mode that refuses writes until you approve, version history on session artifacts, and now evaluation for reusable agents. The runtime lane keeps absorbing data tooling — dbt projects run natively, BigQuery and Snowflake came out from behind the Enterprise licence. The workspace lane is consolidating deployment semantics around fork lineage.

Read the full Windmill trajectory →

Node-RED vs Windmill: editorial side-by-side

N
Node-RED
INFRA · APIS
5.0

Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.

◆ Current state

Node-RED shipped 5.0 in June 2026 after a long beta, raising the runtime floor to Node.js 22.9, and the work since has been stabilisation. This pair patches both lines within ninety minutes: 5.0.5 fixes group fill defaults and opacity, an uncaught exception in the json node on malformed input with a schema, tlsConfigDisableLocalFiles, and multiplayer event property validation; 4.1.14 takes the multiplayer fix, a themes locale lookup error, and the same dependency work. JSONata 2.2.2 lands on both lines, the version that was reverted in July after a behaviour regression.

◆ Where it's heading

The 4.1 line is not winding down. It has now received same-day parallel releases twice, and the fixes crossing over are correctness rather than security this time, which is a wider commitment than backporting sanitisation patches. The defects still cluster in the editor surfaces 5.0 rewrote — groups, multiplayer, tree lists — rather than in the runtime, which is the expected shape after a major that focused on the editor.

◆ Prediction

JSONata 2.2.2 going out on both lines after July's revert suggests the upstream regression is resolved, so the next patches likely return to editor defects rather than dependency churn. The release notes give no timeline.

W
Windmill
INFRA · APIS
6.3

Windmill gives its AI agents a test harness, the piece that lets them into production flows

◆ Current state

Windmill is a developer platform for scripts, flows and internal apps, shipping weekly across three lanes. The AI lane is the busiest: sessions that build scripts and flows as reviewable drafts, a read-only plan mode that refuses writes until you approve, version history on session artifacts, and now evaluation for reusable agents. The runtime lane keeps absorbing data tooling — dbt projects run natively, BigQuery and Snowflake came out from behind the Enterprise licence. The workspace lane is consolidating deployment semantics around fork lineage.

◆ Where it's heading

The AI work has moved through a recognisable sequence: first let the assistant build things, then constrain what it may do without approval, then make its output reviewable and revertible, and now make agents measurable against a fixed set of cases. That is the arc of taking AI from a demo surface to something you are willing to put in a scheduled flow. In parallel, Windmill keeps pulling data-stack runtimes inside its own execution model rather than integrating with them, and keeps giving away runtimes that were previously licensed.

◆ Prediction

Evals are the obvious hook for regression gating, so expect them to be callable from a flow or CI rather than only from the agent card, and expect the eval run history to feed the same version-comparison surface the session artifacts already use.

Alternatives to Node-RED and Windmill

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Node-RED or Windmill.

See all Node-RED alternatives → · See all Windmill alternatives →

Recent activity from Node-RED and Windmill

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoNode-RED5.0.5 fixes group fill defaults, a json node crash, and TLS config
  2. 1d agoNode-RED4.1.14 takes the multiplayer and theme locale fixes to the 4.x line
  3. 9d agoWindmillAI agent evals (beta)
  4. 19d agoWindmillPlan mode for AI sessions
  5. 22d agoWindmillNested filter groups and dotted paths in trigger filters
  6. 23d agoWindmillVersion history for AI session artifacts
  7. 1mo agoWindmillRun dbt projects as a first-class Windmill runtime
  8. 1mo agoNode-REDJSONata upgrade reverted after behaviour regression
  9. 1mo agoNode-REDSession message sanitization backported to the 4.1 line
  10. 1mo agoNode-REDSession messages sanitized; JSONata and test fixes
  11. 1mo agoWindmillOne deployment target, derived from the workspace lineage
  12. 2mo agoNode-REDFirst 5.0 patch fixes sidebar APIs and tree-list behaviour

Frequently asked questions

What is the difference between Node-RED and Windmill?

They serve adjacent needs but don't currently overlap on shipped themes. Windmill is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Node-RED better than Windmill?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Windmill is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Node-RED?

Top Node-RED alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Node-RED alternatives" section above for the current picks, or visit /alternatives/node-red for the full list with editorial commentary on each.

What are the best alternatives to Windmill?

Top Windmill alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Windmill alternatives" section above for the current picks, or visit /alternatives/windmill for the full list with editorial commentary on each.