authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of MainWP and Node-RED — release velocity, themes, recent moves, and the top alternatives to consider.
MainWP's pulse is a steady drip of per-extension maintenance, not headline features.
MainWP is a self-hosted dashboard for managing many WordPress sites from one place, and its changelog is really a stream of independent extension updates — Google Search Console, Patchstack security, regression testing, cost and time tracking, analytics integrations. Recent work is squarely maintenance: reliability fixes to sync logic, batched multi-site operations, and UI consistency passes tied to the MainWP v6 interface. No single release reshapes the platform; the signal is breadth of ecosystem upkeep.
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.
MainWP is a self-hosted dashboard for managing many WordPress sites from one place, and its changelog is really a stream of independent extension updates — Google Search Console, Patchstack security, regression testing, cost and time tracking, analytics integrations. Recent work is squarely maintenance: reliability fixes to sync logic, batched multi-site operations, and UI consistency passes tied to the MainWP v6 interface. No single release reshapes the platform; the signal is breadth of ecosystem upkeep.
The pattern is a broad extension catalog kept individually current rather than a concentrated feature push — each extension gets fixes and small additions on its own cadence. Two themes recur: hardening multi-site operations at scale (batched Patchstack syncing, robust site mapping) and aligning every extension's UI with the v6 redesign. This is the maintenance profile of a mature product monetized through add-ons.
Expect continued per-extension point releases focused on reliability and v6 UI alignment, with the security (Patchstack) and analytics (GSC, Fathom) integrations seeing the most active work. A platform-level shift isn't visible in these entries.
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.
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.
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.
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 MainWP or Node-RED.
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Alert rate limits stop being per-source and start being per-tenant, by query.
The essay series keeps running ahead of the products it describes.
The 3.x line finally ships function: authenticated secret writes and render patches.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all MainWP alternatives → · See all Node-RED alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Infra & APIs. Node-RED is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Node-RED is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
Top MainWP alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "MainWP alternatives" section above for the current picks, or visit /alternatives/mainwp for the full list with editorial commentary on each.
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.