NocoBase
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
A side-by-side editorial comparison of Atlassian and Super Productivity — release velocity, themes, recent moves, and the top alternatives to consider.
Atlassian keeps feeding the Teamwork Graph — Salesforce is the newest source agents can read.
The Inside Atlassian feed mixes research posts and AI thought leadership with a steady run of real releases, and the releases cluster on one idea: making the Teamwork Graph the context layer agents read from. Code Context brought multi-repo codebase understanding into it, a Salesforce connector now brings account, opportunity and case data, and agents already operate inside Confluence and through the Rovo MCP.
A local-first task manager quietly rebuilding itself into a sync engine with a plugin platform on top.
Super Productivity ships minor releases every week or two where the visible feature work is thin and the real effort sits in sync. Across the last six releases the operation-log sync layer picked up field-level merging of concurrent edits, queued background requests, conflict replay, and encrypted-only enforcement for SuperSync. The plugin system absorbed the Azure DevOps and Trello issue providers and gained OAuth hooks plus local secret storage. Since v18.19.0 in early August the repository has published only working branch tags, so the numbered release stream has been quiet for over a week.
The Inside Atlassian feed mixes research posts and AI thought leadership with a steady run of real releases, and the releases cluster on one idea: making the Teamwork Graph the context layer agents read from. Code Context brought multi-repo codebase understanding into it, a Salesforce connector now brings account, opportunity and case data, and agents already operate inside Confluence and through the Rovo MCP.
Atlassian is competing on the index rather than the assistant. Each release widens what the Graph knows — repositories, CRM records, documents, service tickets — and the agent surfaces are deliberately open, running in Confluence, in Claude, in Cursor, in the IDE. Alongside that, the AI governance line signals a second front: selling oversight of the agents customers are already deploying.
Expect more third-party systems connected into the Teamwork Graph on the Salesforce pattern, and governance packaged as a product rather than a posture.
Super Productivity ships minor releases every week or two where the visible feature work is thin and the real effort sits in sync. Across the last six releases the operation-log sync layer picked up field-level merging of concurrent edits, queued background requests, conflict replay, and encrypted-only enforcement for SuperSync. The plugin system absorbed the Azure DevOps and Trello issue providers and gained OAuth hooks plus local secret storage. Since v18.19.0 in early August the repository has published only working branch tags, so the numbered release stream has been quiet for over a week.
The arc is a single-user local app growing the two things multi-device users demand — sync they can trust and third-party integrations — without standing up a server the project has to operate. Sync is being pushed toward fail-closed defaults: encryption is enforced rather than offered, plaintext downloads are refused, stale-key uploads are blocked, and the local REST API now demands a bearer token. Integrations are moving the other way, out of core and into plugins that can authenticate on their own. The one visible thread since then is design-system work — dialogs being moved off hardcoded fills onto theme tokens — which suggests a theming pass running between releases.
Expect the opt-in split-file delta sync format to become the default once conflict replay settles, and more built-in issue providers to follow Azure DevOps and Trello out of core into plugins. The current styling commits point to a theme-token cleanup landing in the next numbered release, though the branch tags alone do not say how large it is.
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 Super Productivity.
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.
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.
Apploye's feed is an SEO blog, and its running theme is defending monitoring on privacy grounds.
See all Atlassian alternatives → · See all Super Productivity 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 5.0), with 1 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 5.0), with 1 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 Super Productivity alternatives in PM are ranked by recent ship velocity. Browse the "Super Productivity alternatives" section above for the current picks, or visit /alternatives/super-productivity for the full list with editorial commentary on each.