Hostaway
Hostaway builds out the direct-booking stack while tightening who sees what
A side-by-side editorial comparison of Camunda and Sugar Calendar — release velocity, themes, recent moves, and the top alternatives to consider.
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.
The changelog turned into a how-to blog — capability news now arrives disguised as tutorials.
Sugar Calendar has stopped announcing numbered releases and now ships each capability as a problem-framed post. The four most recent cover emailing everyone registered for an event, designing event pages in Elementor, setting multiple ticket prices for one event, and attaching a Zoom meeting without copying links by hand. Each opens on a scenario rather than a feature name, and each body is truncated in the feed, so the capability is identifiable but its scope is not. The last numbered announcements, 3.7 and 3.6, are a year old.
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.
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.
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.
Sugar Calendar has stopped announcing numbered releases and now ships each capability as a problem-framed post. The four most recent cover emailing everyone registered for an event, designing event pages in Elementor, setting multiple ticket prices for one event, and attaching a Zoom meeting without copying links by hand. Each opens on a scenario rather than a feature name, and each body is truncated in the feed, so the capability is identifiable but its scope is not. The last numbered announcements, 3.7 and 3.6, are a year old.
The product is filling in the operational gaps around events rather than the calendar itself: attendee communication, tiered pricing, virtual meeting links, page design. That is the arc of a calendar plugin becoming event-management software, and the ticketing and email work in particular moves it toward territory held by dedicated event platforms. The editorial shift matters too — capability news written as tutorials is optimized for search rather than for existing users tracking what changed.
Expect more problem-framed posts covering individual capabilities rather than a numbered 3.8 announcement. These entries still do not say whether the Elementor, Zoom, and email work ships in core or as paid add-ons, so the packaging remains unclear.
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 Sugar Calendar.
Hostaway builds out the direct-booking stack while tightening who sees what
ClickUp folds MCP into Super Agents, wiring outside tools into its AI coworker
Ten release candidates in, Tracecat is stabilising the sandbox its agents run inside
Hive keeps tightening the same three seams: planned time, admin control, and AI review scope
Akiflow's newest release finally adds capability, but reliability work still fills the notes.
A time tracker whose blog argues both sides of employee monitoring, and never mentions the product.
See all Camunda alternatives → · See all Sugar Calendar alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Camunda is currently shipping more aggressively (velocity 6.3 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. Camunda is currently shipping more aggressively (velocity 6.3 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 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.
Top Sugar Calendar alternatives in PM are ranked by recent ship velocity. Browse the "Sugar Calendar alternatives" section above for the current picks, or visit /alternatives/sugar-calendar for the full list with editorial commentary on each.