Camunda
Camunda is untying the business key from process start — assign it late, propagate it down.
A side-by-side editorial comparison of RentRedi and NocoBase — 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.
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.
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.
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.
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.
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.
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 NocoBase.
Camunda is untying the business key from process start — assign it late, propagate it down.
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.
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 NocoBase alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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 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.