AFFiNE
A nightly canary train where the AI platform work hides between dependency bumps
A side-by-side editorial comparison of Hive and NocoBase — release velocity, themes, recent moves, and the top alternatives to consider.
Governance and cross-workspace plumbing, not new AI surface
August's batch is administrative: approval rounds and stages can be locked against edits, action cards can hide apps and areas per action, and status libraries filter by project. Managed Jira actions now move through transitions from List View with Jira still the source of truth. My Actions spans workspaces, and notifications carry comments and reactions.
NocoBase is building an AI employee layer while running its 2.2 and 3.0 lines in parallel.
NocoBase is shipping two trains at once: v2.2.0 is at beta.17 and v3.0.0 is at alpha.8, with features crossing between them. The work concentrates in three areas — AI employees that draw skills from the plugin system, a Portal manager that defines application entry points, and an AI knowledge base backed by configurable vector databases. Cadence on the alpha line is close to daily.
August's batch is administrative: approval rounds and stages can be locked against edits, action cards can hide apps and areas per action, and status libraries filter by project. Managed Jira actions now move through transitions from List View with Jira still the source of truth. My Actions spans workspaces, and notifications carry comments and reactions.
Hive is hardening what it already shipped rather than opening new ground. Permissions around approvals, less clutter on action cards, and tighter two-way Jira sync all read as preparation for larger multi-team deployments, where a workflow has to survive many editors. The AI work that dominated July — Buzz sub-tasks, AI Proofing — is absent from this window.
Expect more admin-scoped controls around approvals and templates, plus continued Jira parity work; on the evidence here the next Buzz change is likelier to be scoping and permissions than a new capability.
NocoBase is shipping two trains at once: v2.2.0 is at beta.17 and v3.0.0 is at alpha.8, with features crossing between them. The work concentrates in three areas — AI employees that draw skills from the plugin system, a Portal manager that defines application entry points, and an AI knowledge base backed by configurable vector databases. Cadence on the alpha line is close to daily.
The plugin system is becoming the extension mechanism for agents, not just for the no-code builder: AI employee skills are built from plugins, and a plugin development guide for defining tools, skills and built-in employees shipped alongside them. Portals are turning into first-class application surfaces with their own access checks, AI conversations, unread counts and backup support. Setup that started as CLI-only — LLM services, vector databases — keeps acquiring UI navigation a release or two later.
Expect the AI employee skill system and vector database management to keep filling in, since CLI-driven setup already has UI navigation and model selection guidance just landed. Features appearing first on the 3.0 alpha line and then reaching the 2.2 betas is now the established pattern, so the next 2.2 beta is the place to watch for what 3.0 tested.
Other PM products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with Hive.
A nightly canary train where the AI platform work hides between dependency bumps
Self-hosted dashboard that finished its feature arc and stopped shipping in 2023.
A self-hosted RSS reader that now spends most of its release notes on security.
SiYuan's v3.8.0 train restates one AI feature set across seven consecutive builds.
Jellyfin renumbers to 12.0 and spends the whole cycle paying down its backend rewrite.
Teable is spending its release budget making bring-your-own-database failures survivable.
Other PM products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with NocoBase.
After a mandatory Action Gateway, the RC train is back to hardening the sandbox
Bonsai is assembling a real CRM underneath the freelancer billing tools
The changelog turned into a how-to blog — capability news now arrives disguised as tutorials.
Two release lines, weekly tags, and not one line of release notes in the feed.
Elle stops being Aha's assistant and becomes where teams encode their own standards.
Every surface is being rebuilt around agents, and the shareholder letter says it is paying.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hive is currently shipping more aggressively (velocity 10.0 vs 6.3), with 0 editorial sparks in the last 30 days against 1. 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. Hive is currently shipping more aggressively (velocity 10.0 vs 6.3), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Hive alternatives in PM are ranked by recent ship velocity. Browse the "Hive alternatives" section above for the current picks, or visit /alternatives/hive for the full list with editorial commentary on each.
Top NocoBase alternatives in PM are ranked by recent ship velocity. Browse the "NocoBase alternatives" section above for the current picks, or visit /alternatives/nocobase for the full list with editorial commentary on each.