NocoBase
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
A side-by-side editorial comparison of Aha! and Asana — release velocity, themes, recent moves, and the top alternatives to consider.
Aha! is teaching its assistant the customer's own standards, then spreading design systems across the suite.
Aha!'s releases run on a weekly cadence and split between Elle, the AI assistant, and the Builder and Roadmaps surfaces it operates on. Elle gained user-defined skills, then a dedicated screen in My work; design systems arrived in Builder and have now been extended to prototypes in Roadmaps. Collaboration basics like user groups fill the gaps.
Asana's agent left the app — it now answers work questions inside Slack threads.
Two arcs run in parallel. A text and editor surface has been built out steadily — Pages, rich text in custom fields, highlighting, threaded comments, and now syntax highlighting — and an agent layer has grown alongside it through AI Teammates, Teammate Skills, and AI Studio. Nearly every release cites a named Community forum request as its origin. The editor work carries a recurring caveat: features land on web first and mobile trails, sometimes losing formatting outright.
Aha!'s releases run on a weekly cadence and split between Elle, the AI assistant, and the Builder and Roadmaps surfaces it operates on. Elle gained user-defined skills, then a dedicated screen in My work; design systems arrived in Builder and have now been extended to prototypes in Roadmaps. Collaboration basics like user groups fill the gaps.
The pattern is a customer-configurable assistant tied to customer-configurable output. Skills encode the team's standards for how work gets done; design systems encode the company's brand for what gets built. Both make the generated artifact reflect the buyer rather than the vendor default, and both are being propagated across products rather than kept in one.
Expect design systems and Elle skills to keep spreading into the remaining Aha! products, and Elle's dedicated screen to accumulate more of the work surface.
Two arcs run in parallel. A text and editor surface has been built out steadily — Pages, rich text in custom fields, highlighting, threaded comments, and now syntax highlighting — and an agent layer has grown alongside it through AI Teammates, Teammate Skills, and AI Studio. Nearly every release cites a named Community forum request as its origin. The editor work carries a recurring caveat: features land on web first and mobile trails, sometimes losing formatting outright.
The editor arc is now mostly closing out a backlog of formatting asks, and each release is narrower than the last. The agent arc is the one changing shape: it has moved from configuring automations inside Asana to answering questions about the work graph from inside another vendor's application, on every tier including Personal. Building it permission-inheriting and private-by-default suggests Asana is treating the agent as a distribution surface rather than a feature to upsell.
Expect the same agent to appear on more surfaces — Teams and email are the obvious next ones — and expect mobile parity work on the editor features that shipped web-only. The language-tier expansion Asana flagged for syntax highlighting is the low-risk near-term item.
Other PM 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 Aha! or Asana.
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
Hive ships in batches, and this one is all planning accuracy and admin control.
Plane ships a fortnightly digest, and the AI layer is where the real work is going.
Ever Teams shipped ten tags in twelve hours and one of them touched the product
Apploye's feed is an SEO blog, and its running theme is defending monitoring on privacy grounds.
Notesnook ships steady 3.4.x patches across desktop and Android with the notes kept off-feed.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Asana is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 editorial sparks in the last 30 days against 1. 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. Asana is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Aha! alternatives in PM are ranked by recent ship velocity. Browse the "Aha! alternatives" section above for the current picks, or visit /alternatives/aha for the full list with editorial commentary on each.
Top Asana alternatives in PM are ranked by recent ship velocity. Browse the "Asana alternatives" section above for the current picks, or visit /alternatives/asana for the full list with editorial commentary on each.