Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Aha! and Ever Teams — 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.
Ever Teams shipped ten tags in twelve hours and one of them touched the product
The window is ten releases published between 01:06 and 12:54 on a single day, and nine of them are continuous-integration work: runners migrated to self-hosted ARC, dead ubicloud labels replaced, the DigitalOcean deploy gated behind a flag, actions bumped to Node 24, a desktop cache bounded after it grew to 9.5 GB. The one product change is v0.133.58, which drops four unread relations from the team-wide daily-plan fetch. Several tags carry no changelog at all beyond a compare link.
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.
The window is ten releases published between 01:06 and 12:54 on a single day, and nine of them are continuous-integration work: runners migrated to self-hosted ARC, dead ubicloud labels replaced, the DigitalOcean deploy gated behind a flag, actions bumped to Node 24, a desktop cache bounded after it grew to 9.5 GB. The one product change is v0.133.58, which drops four unread relations from the team-wide daily-plan fetch. Several tags carry no changelog at all beyond a compare link.
The release train is fully automated and fires on every merge, so tag count says nothing about progress here — the same CI changelog is restated verbatim across multiple tags minutes apart. What work is visible points at build infrastructure being rebuilt around self-hosted runners rather than at the application.
Until the runner migration settles, expect the tag stream to stay dominated by CI commits, with product changes appearing as occasional query-cost fixes like the daily-plan one.
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 Ever Teams.
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
Process Street's public feed is an SEO content engine, not a changelog.
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.
Asana's agent left the app — it now answers work questions inside Slack threads.
See all Aha! alternatives → · See all Ever Teams alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Aha! 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. Aha! 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 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 Ever Teams alternatives in PM are ranked by recent ship velocity. Browse the "Ever Teams alternatives" section above for the current picks, or visit /alternatives/ever-teams for the full list with editorial commentary on each.