NocoBase
NocoBase is building AI employees as plugins and Portals as the surface they live on
A side-by-side editorial comparison of Atlassian and Reclaim.ai — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Atlassian | Reclaim.ai |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 10.0 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | agents, rovo-mcp, jira, confluence | calendar-scheduling, slack, out-of-office, team-coordination |
| Last editorial update | 20h ago | 2mo ago |
| Website | Visit → | — |
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.
Reclaim's roadmap has narrowed to OOO and Slack polish as its release cadence slows
Reclaim's recent shipping is concentrated on out-of-office and Slack integration — custom Slack OOO auto-replies and team OOO calendars are its only two 2026 entries. The rest of the visible feed is from 2025 (a Slack app overhaul, travel timezones, scheduling-link branding). The cadence has thinned noticeably, with multi-month gaps between releases.
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.
Reclaim's recent shipping is concentrated on out-of-office and Slack integration — custom Slack OOO auto-replies and team OOO calendars are its only two 2026 entries. The rest of the visible feed is from 2025 (a Slack app overhaul, travel timezones, scheduling-link branding). The cadence has thinned noticeably, with multi-month gaps between releases.
The product is iterating on team-coordination edges — OOO visibility, Slack presence sync — rather than its core AI scheduling. Combined with the slowed cadence, the signal reads as consolidation and polish over expansion.
Expect continued OOO/Slack-coordination refinements; the multi-month gaps between releases suggest no major net-new capability is imminent based on the entries shown.
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 Atlassian or Reclaim.ai.
NocoBase is building AI employees as plugins and Portals as the surface they live on
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
See all Atlassian alternatives → · See all Reclaim.ai 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 2.5), 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 2.5), 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 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.
Top Reclaim.ai alternatives in PM are ranked by recent ship velocity. Browse the "Reclaim.ai alternatives" section above for the current picks, or visit /alternatives/reclaim for the full list with editorial commentary on each.