Atlassian
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
A side-by-side editorial comparison of Aha! and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Aha! is removing the objections to letting product managers ship working software.
Aha! Builder carries most of the release weight right now: AI-coded applications with built-in authentication, role-based permissions, virtual user testing, and now a design system so generated prototypes inherit company brand. The core roadmap product still gets steady editing and documentation work, including find and replace, bulk attachment actions, and a sidebar table of contents. Essays on how to evaluate AI productivity fill the gaps between releases.
Wakapi is quietly rebuilding itself around the login and container requirements teams ask for.
Wakapi's recent releases cluster around identity and deployment rather than time tracking itself: OpenID Connect login, then an OIDC-only mode, multiple API keys per user, and a switch from Alpine to a distroless nonroot container image. The 2.17.x line has also carried a responsibly disclosed security fix and dropped its relay endpoint. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.
Aha! Builder carries most of the release weight right now: AI-coded applications with built-in authentication, role-based permissions, virtual user testing, and now a design system so generated prototypes inherit company brand. The core roadmap product still gets steady editing and documentation work, including find and replace, bulk attachment actions, and a sidebar table of contents. Essays on how to evaluate AI productivity fill the gaps between releases.
The Builder feature order reads like a checklist for making PM-built software survive contact with IT: authentication first, then permissions, then security review, then testing, now brand consistency. Aha! is arguing that the person who writes the requirements should also produce the working artifact, and it is closing the standard objections one at a time. The MCP server earlier in this arc points the same way, turning roadmap data into something other tools and agents act on.
The unaddressed part of that checklist is deployment and lifecycle: where these applications run, who supports them, and how they are retired. Expect the next Builder releases to deal with hosting or handoff to engineering rather than more authoring features.
Wakapi's recent releases cluster around identity and deployment rather than time tracking itself: OpenID Connect login, then an OIDC-only mode, multiple API keys per user, and a switch from Alpine to a distroless nonroot container image. The 2.17.x line has also carried a responsibly disclosed security fix and dropped its relay endpoint. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.
The direction is a self-hosted tool making itself deployable somewhere other than one developer's server. External identity providers, an option to disable local login entirely, per-key credentials and a container that runs as a nonroot user with no shell are the requirements that come from someone else's security review, not from a hobbyist's wishlist. The corresponding cost is visible too: dropped MSSQL support and a Docker base change that forces SQLite users to fix directory permissions by hand.
The identity and packaging thread is the only sustained one in this feed, so further hardening in that area is the most likely continuation; the sparse release notes make anything more specific guesswork.
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 Wakapi.
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
The time-tracking product is invisible behind a steady run of comparison roundups.
Phorge tags a release per fix, and years pass between the ones that reach this feed.
Zoho Projects makes time tracking the product's center of gravity, and lets Zia build the schema.
Jira is being pushed upward — from tracking the work to judging its cost, risk and business health.
Steady small-surface polish across Basecamp and HEY, with no directional move.
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 2.5), 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 2.5), 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 Wakapi alternatives in PM are ranked by recent ship velocity. Browse the "Wakapi alternatives" section above for the current picks, or visit /alternatives/wakapi for the full list with editorial commentary on each.