Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of ActiveCollab and Plane — release velocity, themes, recent moves, and the top alternatives to consider.
AI agents got the keys in June; in July ActiveCollab added the locks.
ActiveCollab ships small, self-contained changes on a roughly weekly cadence, and this window covers three fronts. Security gained an IP allowlist and per-tool permissions for MCP agents, both filed under Security settings. The client layer was rebuilt, with native macOS and Windows desktop apps replacing Electron and distributed through the platform app stores, followed by dark themes that match system appearance. Collaboration picked up chat favorites and self-expiring mute, plus an activity heatmap on My Work.
Plane ships a fortnightly digest, and the AI layer is where the real work is going.
Plane releases on a strict twice-monthly cadence, each entry a bundle rather than a single feature. The current window covers Pages becoming a document surface (toggle blocks, embedded widgets, nested-page zip export), Intake getting dashboard visibility, and Automations extending to modules, milestones, and releases. Underneath, Plane AI has been accumulating capability faster than any other area — Skills, an AI Block in Pages, live PQL results in chat, open-weight model options.
ActiveCollab ships small, self-contained changes on a roughly weekly cadence, and this window covers three fronts. Security gained an IP allowlist and per-tool permissions for MCP agents, both filed under Security settings. The client layer was rebuilt, with native macOS and Windows desktop apps replacing Electron and distributed through the platform app stores, followed by dark themes that match system appearance. Collaboration picked up chat favorites and self-expiring mute, plus an activity heatmap on My Work.
The clearest thread runs through MCP. In mid-June the product made individual comments linkable specifically so an AI agent could retrieve one; four weeks later it shipped controls restricting which MCP tools those agents may call. That is a reach-then-govern sequence, and putting agent permissions in Security settings next to the IP firewall says an agent is being treated as a principal to scope rather than an integration to enable. Everything else in the window is steady quality-of-life and platform hygiene.
Expect the governance layer around MCP to keep filling in - audit logging of agent actions, or per-role rather than per-account tool limits, is the natural next step given both new controls landed in Security settings on the same day.
Plane releases on a strict twice-monthly cadence, each entry a bundle rather than a single feature. The current window covers Pages becoming a document surface (toggle blocks, embedded widgets, nested-page zip export), Intake getting dashboard visibility, and Automations extending to modules, milestones, and releases. Underneath, Plane AI has been accumulating capability faster than any other area — Skills, an AI Block in Pages, live PQL results in chat, open-weight model options.
The tracker is being rebuilt around two things it did not start as: a wiki with executable blocks, and a workspace where agent behaviour is authored and stored. Skills was the turn — instructions saved once and reused rather than re-typed — and the Pages work since has been about making the document a place where that output lands. The structural cleanups run alongside: epics folded into the work item type system, permissions redesigned into two layers, automations widened to more object types. It is consolidation, not sprawl.
The next digests likely extend Automations toward AI-triggered actions, since Skills, PQL, and rule-based automation now exist as separate pieces that obviously compose. The entries are digest summaries linking off-site, so per-feature depth is not readable from the feed.
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 ActiveCollab or Plane.
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.
Ever Teams shipped ten tags in twelve hours and one of them touched the product
Asana's agent left the app — it now answers work questions inside Slack threads.
See all ActiveCollab alternatives → · See all Plane alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — project-management — within PM. ActiveCollab and Plane are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. ActiveCollab and Plane are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top ActiveCollab alternatives in PM are ranked by recent ship velocity. Browse the "ActiveCollab alternatives" section above for the current picks, or visit /alternatives/activecollab for the full list with editorial commentary on each.
Top Plane alternatives in PM are ranked by recent ship velocity. Browse the "Plane alternatives" section above for the current picks, or visit /alternatives/plane for the full list with editorial commentary on each.