OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of AWeber and Eleventy — release velocity, themes, recent moves, and the top alternatives to consider.
AWeber is moving the console out of the browser and into the chat window
AWeber ships small, user-visible features on a steady two-to-four-week rhythm, and the recent run is unusually coherent: automatic UTM tagging on every link, opens-and-clicks charts over the last 100 broadcasts, AI image editing inside the signup form builder, and visual inline form placement. The newest release puts AWeber in Claude's connector directory, so drafting a broadcast, adding subscribers, or pulling open and click rates happens in a conversation against live account data. The rest of the feed is search-oriented marketing education that carries no product change.
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.
AWeber ships small, user-visible features on a steady two-to-four-week rhythm, and the recent run is unusually coherent: automatic UTM tagging on every link, opens-and-clicks charts over the last 100 broadcasts, AI image editing inside the signup form builder, and visual inline form placement. The newest release puts AWeber in Claude's connector directory, so drafting a broadcast, adding subscribers, or pulling open and click rates happens in a conversation against live account data. The rest of the feed is search-oriented marketing education that carries no product change.
Two threads run through this window and they are converging. One is measurement — UTM tagging, engagement charts, outlier comparison — building a record of what each send actually did. The other is generation, where the AI builders moved from producing forms to editing the images inside them. The Claude connector is what makes the pair useful without the app open: the analysis surface and the authoring surface both become things you ask for rather than navigate to.
The connector's surface should widen from broadcasts and subscriber lookups toward the automation and landing-page objects the AI builders already create. Whether AWeber treats chat as a companion to the console or as the primary interface is not something these entries settle.
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 AWeber or Eleventy.
OttoKit keeps widening its WordPress trigger surface one plugin at a time
Craft 6's alphas keep converting the plugin API, one removal at a time
Two security releases ship the same day, and 6.2 finally clears alpha
Buttondown ships almost daily, and most of it is someone else's bug report closed.
Flodesk just moved its analytics out of the dashboard and into Claude and ChatGPT.
Formidable widens MCP compatibility and locks down signature files
See all AWeber 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. AWeber 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. AWeber 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 Mkt Auto products to evaluate alongside.
Top AWeber alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "AWeber alternatives" section above for the current picks, or visit /alternatives/aweber 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.