authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Node-RED vs Oh Dear
A side-by-side editorial comparison of Node-RED and Oh Dear — release velocity, themes, recent moves, and the top alternatives to consider.
Node-RED vs Oh Dear: at a glance
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.
What is Oh Dear?
The monitoring account is becoming something an agent operates, not just a dashboard someone reads.
Oh Dear is an uptime and site-health monitoring service shipping a dated changelog most weeks, with each release mixing new capability, security work and fixes. The MCP server is the thread running through all of it: monitor create, update and delete arrived in May, tag groups and notification routing in June, and the August release extends it across downtime, check summaries, domain intelligence, maintenance windows, check state, status page updates, notification destinations, scheduled tasks, Broken Links, Application Health and account management. Around that sit steady monitoring improvements — consecutive-failure thresholds for sitemap alerts, raw JSON bodies in HTTP checks, better handling of out-of-order scheduled-task pings.
Node-RED vs Oh Dear: editorial side-by-side
Node-RED
5.0INFRA · APIS
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.
Oh Dear
5.0INFRA · APIS
The monitoring account is becoming something an agent operates, not just a dashboard someone reads.
◆ Current state
Oh Dear is an uptime and site-health monitoring service shipping a dated changelog most weeks, with each release mixing new capability, security work and fixes. The MCP server is the thread running through all of it: monitor create, update and delete arrived in May, tag groups and notification routing in June, and the August release extends it across downtime, check summaries, domain intelligence, maintenance windows, check state, status page updates, notification destinations, scheduled tasks, Broken Links, Application Health and account management. Around that sit steady monitoring improvements — consecutive-failure thresholds for sitemap alerts, raw JSON bodies in HTTP checks, better handling of out-of-order scheduled-task pings.
◆ Where it's heading
Two things are being built at once and they depend on each other. The MCP surface keeps widening until an assistant can run the account end to end, and the authorization model keeps being tightened to make that safe — API token scoping, permission checks on monitor-modifying tools, access controls on the new write tools, sessions invalidated on password change. Each release moves both. Underneath, the business plumbing is being tidied in public too: legacy pricing shown on the plan chooser, corrected affiliate terms, an agency-focused pricing structure, AI wizard placeholder monitors excluded from usage limits.
◆ Prediction
Expect the MCP tool surface to keep filling in the remaining corners of the product and the permission model to keep pace with it, and expect the November Slack connection deprecation already being warned about in-app to produce a migration release before then.
Alternatives to Node-RED and Oh Dear
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 Oh Dear.
incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
Warp
The essay series keeps running ahead of the products it describes.
werf
The 3.x line finally ships function: authenticated secret writes and render patches.
Infisical
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
Retool
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all Node-RED alternatives → · See all Oh Dear alternatives →
Recent activity from Node-RED and Oh Dear
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoNode-RED5.0.5 fixes group fill defaults, a json node crash, and TLS config
- 1d agoNode-RED4.1.14 takes the multiplayer and theme locale fixes to the 4.x line
- 4d agoOh DearMCP tools extended across maintenance, status pages and account management
- 11d agoOh DearAPI token scoping and MCP permission checks tightened
- 19d agoOh DearRecovery notifications restored after performance delta alerts
- 25d agoOh DearJSON request bodies in HTTP checks; AI monitoring moves to the Laravel AI SDK
- 1mo agoOh DearApplication Health metadata limit doubled; scheduled-task ping fixes
- 1mo agoNode-REDJSONata upgrade reverted after behaviour regression
- 1mo agoNode-REDSession message sanitization backported to the 4.1 line
- 1mo agoNode-REDSession messages sanitized; JSONata and test fixes
- 1mo agoOh DearAgency pricing introduced; Forge import moves to scoped API v2 tokens
- 2mo agoNode-REDFirst 5.0 patch fixes sidebar APIs and tree-list behaviour
Frequently asked questions
What is the difference between Node-RED and Oh Dear?
They serve adjacent needs but don't currently overlap on shipped themes. Node-RED and Oh Dear are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 Oh Dear?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Node-RED and Oh Dear are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 Oh Dear?
Top Oh Dear alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Oh Dear alternatives" section above for the current picks, or visit /alternatives/ohdear for the full list with editorial commentary on each.