Atlassian
Atlassian is rebuilding Jira and Forge so agents, not people, are the ones taking action.
Comparison · PM
Camunda vs NocoBase
A side-by-side editorial comparison of Camunda and NocoBase — release velocity, themes, recent moves, and the top alternatives to consider.
Camunda vs NocoBase: at a glance
What is Camunda?
Camunda is untying the business key from process start — assign it late, propagate it down.
The 8.10 alpha series is built around one theme: business IDs. Across engine, protocol, REST, gRPC, the Java client and the exporters, Camunda added late assignment via CompleteJob, forward-propagation semantics, resolution into child instances at call activity, deploy-time validation of the businessId attribute on zeebe:calledElement, and exposure in FEEL expressions. Underneath it, agent-instance data now gets cleaned up at the end of a process instance lifecycle and loop counters were renamed across agent instance history.
What is NocoBase?
NocoBase is turning its plugin system into the skill supply for in-app AI employees.
Two release trains run in parallel — a 2.2.0 line still taking features and a 3.0.0 alpha line that inherits them. Across both, the AI employees subsystem is where the substantive work lands: an embeddable chat block scoped to a context, frontend AI tools callable from JS blocks, backup and restore for AI-mode portals, and now skills assigned per employee from the settings page. A second thread reorganizes application entry — a standalone Settings app, portal-scoped conversations, a CLI that can set and update the client entry mode.
Camunda vs NocoBase: editorial side-by-side
Camunda
6.3PM
Camunda is untying the business key from process start — assign it late, propagate it down.
◆ Current state
The 8.10 alpha series is built around one theme: business IDs. Across engine, protocol, REST, gRPC, the Java client and the exporters, Camunda added late assignment via CompleteJob, forward-propagation semantics, resolution into child instances at call activity, deploy-time validation of the businessId attribute on zeebe:calledElement, and exposure in FEEL expressions. Underneath it, agent-instance data now gets cleaned up at the end of a process instance lifecycle and loop counters were renamed across agent instance history.
◆ Where it's heading
Business IDs are being promoted from a value you set once at start into a first-class, propagating, late-bindable identifier — which is what a process engine needs when the domain entity a process refers to is not known until partway through. In parallel, a canonical endpoint-to-permission mapping is being exposed as the single source of truth for RBAC, and the agent-instance surface implies agentic constructs are being maintained as ordinary engine state with their own lifecycle and cleanup.
◆ Prediction
Expect 8.10 to reach general availability with the business ID work complete across all three client surfaces, and the RBAC mapping to become the basis for generated authorization documentation or tooling. The agent-instance cleanup and history renames suggest that surface is still pre-stable and will keep changing shape before it settles.
NocoBase
7.5PM
NocoBase is turning its plugin system into the skill supply for in-app AI employees.
◆ Current state
Two release trains run in parallel — a 2.2.0 line still taking features and a 3.0.0 alpha line that inherits them. Across both, the AI employees subsystem is where the substantive work lands: an embeddable chat block scoped to a context, frontend AI tools callable from JS blocks, backup and restore for AI-mode portals, and now skills assigned per employee from the settings page. A second thread reorganizes application entry — a standalone Settings app, portal-scoped conversations, a CLI that can set and update the client entry mode.
◆ Where it's heading
The AI employees work has moved from a chat surface to a capability model: an employee is now an addressable actor with assigned skills, a portal it belongs to, and unread state. Because skills are built from plugins, NocoBase's existing extension ecosystem becomes the thing that defines what agents can do, rather than a separate tool registry. The parallel portal and settings restructuring reads as preparation for 3.0 shipping AI portals as a first-class deployment shape.
◆ Prediction
Expect the 3.0 alpha train to formalize permissions on AI employees — which roles may assign which skills, and which collections an employee can reach — since the access-control plumbing is already moving in the same releases.
Alternatives to Camunda and NocoBase
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 Camunda or NocoBase.
Aha!
Aha! keeps closing the gaps that stop product managers from shipping the apps they build.
Process Street
Process Street's feed is a content marketing engine with one real product signal in it.
NotePlan
NotePlan keeps opening its notebook to outside writers: plugins, MCP agents, now Apple Reminders.
Hive
Hive deepens its proofing stack for creative teams while teaching Buzz restraint
Buddy Punch
Buddy Punch's feed is vertical listicles and blog essays, with no release notes
See all Camunda alternatives → · See all NocoBase alternatives →
Recent activity from Camunda and NocoBase
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8h agoCamundaAlpha4 final: business ID work plus broker fixes
- 17h agoNocoBaseAI employees gain plugin-built skills and portal-scoped conversations ⚡
- 2d agoCamundaOptimize 8.7 dependency and iframe backports
- 3d agoNocoBasev3.0.0-alpha.6
- 4d agoNocoBasev3.0.0-alpha.5
- 6d agoNocoBasev3.0.0-alpha.4
- 6d agoCamundaOpenAPI version check fixed after spec backport
- 6d agoNocoBasev2.2.0-beta.16 ⚡
- 7d agoNocoBasev3.0.0-alpha.3
- 9d agoCamundaLate business ID assignment lands across engine and clients ⚡
Frequently asked questions
What is the difference between Camunda and NocoBase?
They serve adjacent needs but don't currently overlap on shipped themes. NocoBase is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 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.
Is Camunda better than NocoBase?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NocoBase is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 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.
What are the best alternatives to Camunda?
Top Camunda alternatives in PM are ranked by recent ship velocity. Browse the "Camunda alternatives" section above for the current picks, or visit /alternatives/camunda for the full list with editorial commentary on each.
What are the best alternatives to NocoBase?
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.