Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Ever Teams and Teamhood — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Teamhood's feed is comparison-SEO listicles, not product releases
Teamhood is a project- and portfolio-management tool with a Gantt/Kanban and EU-hosting angle, but its feed is entirely SEO content: 'best alternatives to X' roundups and vertical buyer guides (aerospace, civil engineering, construction, PMO). None of these are changelog entries, so the feed shows no shipped product change.
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.
Teamhood is a project- and portfolio-management tool with a Gantt/Kanban and EU-hosting angle, but its feed is entirely SEO content: 'best alternatives to X' roundups and vertical buyer guides (aerospace, civil engineering, construction, PMO). None of these are changelog entries, so the feed shows no shipped product change.
The content strategy is targeting high-intent switchers from Wrike, Trello, Smartsheet, and enterprise PM tools, and leaning on regulated/heavy verticals plus EU data-hosting as differentiators. That reveals go-to-market positioning, not product direction; the release cadence itself is invisible from this stream.
No release data is present, so a product prediction can't be grounded here; the vertical and competitor-displacement focus of the content is the only forward signal, and it is marketing rather than roadmap.
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 Ever Teams or Teamhood.
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 Ever Teams alternatives → · See all Teamhood alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Ever Teams and Teamhood are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Ever Teams and Teamhood are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
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.
Top Teamhood alternatives in PM are ranked by recent ship velocity. Browse the "Teamhood alternatives" section above for the current picks, or visit /alternatives/teamhood for the full list with editorial commentary on each.