Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Plane and Resource Guru — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Resource Guru is opening the schedule up — first to AI tools, now to bookings that fit themselves.
Resource Guru publishes real product notes and SEO articles through the same feed, so the signal has to be separated from capacity-planning guides and review round-ups. The product entries are short — 200 to 320 characters — but they are genuine launches, not excerpts of something larger. Recent releases cluster around two things: making the schedule readable on the user's own terms (custom field colors, configurable Projects columns, placeholder digests) and making it reachable by machines, via an MCP server and integrations with Trello and ClickUp.
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.
Resource Guru publishes real product notes and SEO articles through the same feed, so the signal has to be separated from capacity-planning guides and review round-ups. The product entries are short — 200 to 320 characters — but they are genuine launches, not excerpts of something larger. Recent releases cluster around two things: making the schedule readable on the user's own terms (custom field colors, configurable Projects columns, placeholder digests) and making it reachable by machines, via an MCP server and integrations with Trello and ClickUp.
Custom fields have become the organizing spine of the product — they now drive color coding and column layout rather than sitting as inert metadata. Alongside that, the scheduling engine is taking on decisions the user used to make manually: placeholder digests surface unassigned work, and Total Hours bookings hand the system a quantity and a window instead of fixed slots. The MCP server points the same schedule data at AI assistants. The through-line is a resource scheduler that increasingly arranges work rather than just recording it.
Total Hours bookings put allocation logic inside the scheduler for the first time, and the MCP server exposes account data to assistants that could drive it; the next step these entries point toward is more scheduling decisions being automated rather than displayed. What is not visible yet is whether the MCP server will gain write access or stay read-only.
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 Plane or Resource Guru.
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 Plane alternatives → · See all Resource Guru alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Plane and Resource Guru 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. Plane and Resource Guru 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 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.
Top Resource Guru alternatives in PM are ranked by recent ship velocity. Browse the "Resource Guru alternatives" section above for the current picks, or visit /alternatives/resourceguru for the full list with editorial commentary on each.