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 Vikunja — 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.
Vikunja crossed the v1.0 finish line and pivoted hard into security hardening.
Vikunja shipped two v1.0 release candidates through late 2025 and early 2026, then jumped to a v2 series whose first widely-tagged point release, v2.2.1, is dominated by security work. The latest release patches multiple SSRF and IDOR vulnerabilities, enforces disabled/locked-account semantics across every auth surface (OIDC, API tokens, CalDAV, LDAP), and adds a shared SSRF-safe HTTP client that webhooks and migrations now route through. User-facing feature work has slowed; the visible energy is in plumbing and audit cleanup.
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.
Vikunja shipped two v1.0 release candidates through late 2025 and early 2026, then jumped to a v2 series whose first widely-tagged point release, v2.2.1, is dominated by security work. The latest release patches multiple SSRF and IDOR vulnerabilities, enforces disabled/locked-account semantics across every auth surface (OIDC, API tokens, CalDAV, LDAP), and adds a shared SSRF-safe HTTP client that webhooks and migrations now route through. User-facing feature work has slowed; the visible energy is in plumbing and audit cleanup.
The arc moves from feature-completion (S3 storage, drag-and-drop project moves, hover previews in late 2025) toward platform credibility — closing security gaps a self-hosted task tool needs to clear before serious team adoption. The rapid version-number jump from v1.0.0-rc4 to v2.2.1 in two months suggests v1.0 shipped and the team tagged a v2 line aimed at addressing accumulated authz debt. Expect the next several releases to keep the security-first posture rather than return to a feature push.
The next release will likely continue closing remaining authz edges (more IDOR audits, additional credential-stripping in API responses) and bundle a translations and dependency sweep. A user-facing feature push probably waits until the security work plateaus.
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 Vikunja.
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 Vikunja 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 0.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 0.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 Vikunja alternatives in PM are ranked by recent ship velocity. Browse the "Vikunja alternatives" section above for the current picks, or visit /alternatives/vikunja for the full list with editorial commentary on each.