Sulu
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
A side-by-side editorial comparison of n8n and Eleventy — release velocity, themes, recent moves, and the top alternatives to consider.
n8n's daily patch train hides the real work: hardening its MCP server into a proper auth resource.
n8n ships patches almost daily across three live branches (2.31.x, 2.32.x, 2.33.x), so the changelog reads mostly as noise. Underneath it, nearly every substantive commit lands in one of two places: the AI agent builder and the MCP server. The 2.33.0 minor is the clearest example, a very large bundle with no features section at all, only fixes.
The v4 canary line is being renamed Build Awesome while 3.x is kept on pure maintenance.
Two lines run in parallel. The 3.x branch gets dependency-only releases — 3.1.5 and 3.1.6 explicitly ship no core code changes, after 3.1.3 and 3.1.4 failed to publish and were left as immutable dead tags. The v4 alpha train, meanwhile, is where the work is: Node minimum raised to 22.15, page.inputPathDir and page.dir removed, batched incremental builds added, and a large refactor of the Nunjucks fork onto a fully-async prerelease. The releases themselves now carry the Build Awesome name and offer an @awesome.me/buildawesome install alongside @11ty/eleventy@canary.
n8n ships patches almost daily across three live branches (2.31.x, 2.32.x, 2.33.x), so the changelog reads mostly as noise. Underneath it, nearly every substantive commit lands in one of two places: the AI agent builder and the MCP server. The 2.33.0 minor is the clearest example, a very large bundle with no features section at all, only fixes.
The MCP work has moved past merely exposing a server toward protocol compliance: OAuth protected-resource metadata served at the bare well-known path, the RFC 9207 iss parameter on authorization error redirects, PKCE negotiation and token expiry handling. Agent-side changes point the same direction, with secrets scrubbed before they reach agent memory, MCP connection failures made non-blocking for agents, and workflow deletion refused while an unpublish is still running. This is the unglamorous half of making agents safe to run inside someone else's instance.
With the auth and audit plumbing largely landed, the next visible move is agent capability that depends on it, such as delegated MCP access, rather than another round of protocol fixes.
Two lines run in parallel. The 3.x branch gets dependency-only releases — 3.1.5 and 3.1.6 explicitly ship no core code changes, after 3.1.3 and 3.1.4 failed to publish and were left as immutable dead tags. The v4 alpha train, meanwhile, is where the work is: Node minimum raised to 22.15, page.inputPathDir and page.dir removed, batched incremental builds added, and a large refactor of the Nunjucks fork onto a fully-async prerelease. The releases themselves now carry the Build Awesome name and offer an @awesome.me/buildawesome install alongside @11ty/eleventy@canary.
v4 is accumulating breaking changes faster than it is stabilizing — three of the entries in this window announce removals or minimum-version bumps, and alpha.10 exists only to hotfix a regression alpha.9 introduced. The Nunjucks refactor is the biggest bet: making the fork fully async removes the need for async-specific template tags, but the release notes flag it as risky for existing Nunjucks users. The naming change is proceeding on the same timeline, so users tracking canary are absorbing an identity shift and an API shift at once.
Expect more v4 alphas carrying breaking removals before any beta, with the Nunjucks async refactor generating follow-up regressions; 3.x looks likely to keep receiving dependency-only patches with no core changes.
Other Mkt Auto 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 n8n or Eleventy.
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
Nearly every release in this window carries security hardening — Pimcore is working through an injection sweep.
Steady feature-then-patch cadence, with security reports rising because AI tools are finding them
Measurement gets granular while the API quietly opens ClickFunnels up to outside agents
OneSignal is arguing a new category into existence before showing the product behind it.
Kit rebuilt its landing page editor, then handed the controls to an AI agent.
See all n8n alternatives → · See all Eleventy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. n8n and Eleventy 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. n8n and Eleventy 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 Mkt Auto products to evaluate alongside.
Top n8n alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "n8n alternatives" section above for the current picks, or visit /alternatives/n8n for the full list with editorial commentary on each.
Top Eleventy alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Eleventy alternatives" section above for the current picks, or visit /alternatives/eleventy for the full list with editorial commentary on each.