Resource Guru
Resource Guru is opening the schedule up — first to AI tools, now to bookings that fit themselves.
A side-by-side editorial comparison of Aha! and Vikunja — release velocity, themes, recent moves, and the top alternatives to consider.
Elle stops being Aha's assistant and becomes where teams encode their own standards.
Aha! publishes a steady run of concrete, narrow features across Roadmaps and Builder as one-line update posts, interleaved with occasional product-management essays. This window covers user groups for mentions and assignment, a design system for AI-generated apps, long-document handling, virtual user testing for prototypes, and user-defined skills for the Elle assistant. Aha! Builder, which turns plans into working applications, is absorbing most of the AI investment.
Vikunja crossed the v1.0 finish line and pivoted hard into security hardening.
Vikunja shipped two v1.0 release candidates through late 2025 and early 2026, then jumped to a v2 series whose first widely-tagged point release, v2.2.1, is dominated by security work. The latest release patches multiple SSRF and IDOR vulnerabilities, enforces disabled/locked-account semantics across every auth surface (OIDC, API tokens, CalDAV, LDAP), and adds a shared SSRF-safe HTTP client that webhooks and migrations now route through. User-facing feature work has slowed; the visible energy is in plumbing and audit cleanup.
Aha! publishes a steady run of concrete, narrow features across Roadmaps and Builder as one-line update posts, interleaved with occasional product-management essays. This window covers user groups for mentions and assignment, a design system for AI-generated apps, long-document handling, virtual user testing for prototypes, and user-defined skills for the Elle assistant. Aha! Builder, which turns plans into working applications, is absorbing most of the AI investment.
The arc is legible across three months: Aha! held the product data, then exposed it through an MCP server in May, then acted on it when Builder began generating applications in June, and now lets customers define how the assistant behaves. Skills make Elle configurable by the teams using it rather than only by Aha!, which repeats for the assistant what Builder did for applications. The Roadmaps side meanwhile keeps receiving unglamorous collaboration and document work, so the classic tool is not being starved while the AI half expands.
Skills are the obvious thing to extend next, most likely with sharing or governance controls, since Aha! sells to organizations that standardize process. On the Builder side, testing landed in July and deployment and handoff remain the visible gaps.
Vikunja shipped two v1.0 release candidates through late 2025 and early 2026, then jumped to a v2 series whose first widely-tagged point release, v2.2.1, is dominated by security work. The latest release patches multiple SSRF and IDOR vulnerabilities, enforces disabled/locked-account semantics across every auth surface (OIDC, API tokens, CalDAV, LDAP), and adds a shared SSRF-safe HTTP client that webhooks and migrations now route through. User-facing feature work has slowed; the visible energy is in plumbing and audit cleanup.
The arc moves from feature-completion (S3 storage, drag-and-drop project moves, hover previews in late 2025) toward platform credibility — closing security gaps a self-hosted task tool needs to clear before serious team adoption. The rapid version-number jump from v1.0.0-rc4 to v2.2.1 in two months suggests v1.0 shipped and the team tagged a v2 line aimed at addressing accumulated authz debt. Expect the next several releases to keep the security-first posture rather than return to a feature push.
The next release will likely continue closing remaining authz edges (more IDOR audits, additional credential-stripping in API responses) and bundle a translations and dependency sweep. A user-facing feature push probably waits until the security work plateaus.
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 Vikunja.
Resource Guru is opening the schedule up — first to AI tools, now to bookings that fit themselves.
Rize stops being a time tracker you query and becomes one that runs on a schedule without you.
A competitor-comparison content machine — the feed ranks rivals, it never reports a release.
Resource Guru is teaching its scheduler to place work for you, not just record where you put it
RentRedi is building for landlords who outgrew a spreadsheet — portfolios, documents, and now AI intake
Post-V5 releases are spent making the AI agency actually usable rather than adding to it.
See all Aha! alternatives → · See all Vikunja 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 0.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 0.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 Vikunja alternatives in PM are ranked by recent ship velocity. Browse the "Vikunja alternatives" section above for the current picks, or visit /alternatives/vikunja for the full list with editorial commentary on each.