Atlassian
Atlassian is rebuilding Jira and Forge so agents, not people, are the ones taking action.
A side-by-side editorial comparison of RentRedi and Camunda — release velocity, themes, recent moves, and the top alternatives to consider.
RentRedi is rebuilding around the portfolio, not the individual property
The last two months trace a clear structural shift: Portfolios arrived in July as a way to group properties by LLC, state or owner with a global filter across the whole app, and Portfolio Performance had already landed an aggregated NOI, cash flow and equity view in June. Around that spine, RentRedi keeps filling in operational surfaces — a global Documents tab with folders, a rebuilt split-view chat with unread counts, a dedicated Listings page, and the option for landlords to absorb tenant screening fees themselves.
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 last two months trace a clear structural shift: Portfolios arrived in July as a way to group properties by LLC, state or owner with a global filter across the whole app, and Portfolio Performance had already landed an aggregated NOI, cash flow and equity view in June. Around that spine, RentRedi keeps filling in operational surfaces — a global Documents tab with folders, a rebuilt split-view chat with unread counts, a dedicated Listings page, and the option for landlords to absorb tenant screening fees themselves.
This is a product growing up with its users. Early RentRedi assumed a landlord managing a handful of units one property at a time; the recent work assumes someone holding several LLCs who needs cross-property roll-ups, searchable document storage and a filter that reshapes every screen at once. The screening-fee change points the same way — larger operators competing for applicants will eat that cost, and the product now lets them.
Expect portfolio-level scoping to keep propagating into surfaces it has not reached yet — reporting, accounting exports and permissions — and for portfolio-scoped user roles to follow, since grouping by LLC or owner implies wanting to give someone access to just one slice.
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.
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 RentRedi or Camunda.
Atlassian is rebuilding Jira and Forge so agents, not people, are the ones taking action.
Aha! keeps closing the gaps that stop product managers from shipping the apps they build.
Process Street's feed is a content marketing engine with one real product signal in it.
NocoBase is turning its plugin system into the skill supply for in-app AI employees.
NotePlan keeps opening its notebook to outside writers: plugins, MCP agents, now Apple Reminders.
Hive deepens its proofing stack for creative teams while teaching Buzz restraint
See all RentRedi alternatives → · See all Camunda alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. RentRedi and Camunda are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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. RentRedi and Camunda are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top RentRedi alternatives in PM are ranked by recent ship velocity. Browse the "RentRedi alternatives" section above for the current picks, or visit /alternatives/rentredi for the full list with editorial commentary on each.
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.