Rize
Rize stops being a time tracker you query and becomes one that runs on a schedule without you.
A side-by-side editorial comparison of ActiveCollab and Atlassian — 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.
Every surface is being rebuilt around agents, and the shareholder letter says it is paying.
The Inside Atlassian feed interleaves real product releases with engineering-culture writing, and the release half is now almost entirely agent infrastructure. This window holds a rebuilt Deployments page, agents that can be @mentioned to author directly inside Confluence pages, and those same agents reachable from Claude, Cursor, or an IDE through Rovo MCP. Atlassian puts agent invocations above five million, and the Q4 FY26 shareholder letter names enterprise, AI, and the system of work as its priorities.
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.
The Inside Atlassian feed interleaves real product releases with engineering-culture writing, and the release half is now almost entirely agent infrastructure. This window holds a rebuilt Deployments page, agents that can be @mentioned to author directly inside Confluence pages, and those same agents reachable from Claude, Cursor, or an IDE through Rovo MCP. Atlassian puts agent invocations above five million, and the Q4 FY26 shareholder letter names enterprise, AI, and the system of work as its priorities.
One direction runs through a long sequence of releases: agents are moving from a feature inside Atlassian products to a layer that other tools call. MCP is the mechanism, and each release widens either what agents can act on or where they can be invoked from, which means the interesting question is no longer what Rovo can do but how little of it requires an Atlassian tab. The culture posts run alongside and increasingly carry internal measurements — ticket quality, code throughput, translation volume — turning the blog into the evidence base for the same argument.
The next releases most likely extend agent reach into the surfaces that remain and add actions rather than new chat entry points. The shareholder framing suggests enterprise controls and scale figures will keep arriving attached to those launches.
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 Atlassian.
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.
Hostaway is becoming a compliance and finance system that happens to manage channels
See all ActiveCollab alternatives → · See all Atlassian alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Atlassian is currently shipping more aggressively (velocity 10.0 vs 6.3), with 0 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. Atlassian is currently shipping more aggressively (velocity 10.0 vs 6.3), with 0 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 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 Atlassian alternatives in PM are ranked by recent ship velocity. Browse the "Atlassian alternatives" section above for the current picks, or visit /alternatives/atlassian for the full list with editorial commentary on each.