Celoxis
Celoxis publishes PMO thought-leadership at pace; the product ships out of view.
A side-by-side editorial comparison of NocoBase and Rize — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | NocoBase | Rize |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | low-code, ai-agents, workflow-automation, self-hosted | time-tracking, mcp, ai-agents, profitability-reporting |
| Last editorial update | 2h ago | 20h ago |
| Website | Visit → | — |
NocoBase is wiring its AI employees and its JS blocks to call each other
NocoBase is a self-hosted low-code platform, currently building 2.2.0 in the open across alpha and beta pre-releases. The visible work splits between a client v2 rewrite — tabs, subpages and pop-ups gaining linkage rules, configurable route entry modes — and an AI employees layer that is being connected to the platform's JS blocks in both directions.
Rize made its time data agent-queryable in May, then spent two months fixing the app it runs in.
Rize's last two releases are pure repair: black screens on Windows, frozen dashboards, unreliable auto-updates, widget timers, app size, and sign-in hardening, with settings sync across machines as the one additive item. That follows a dense May in which Rize shipped an MCP server exposing profitability and event data, in-app chat over that data, a Slack agent for asking about hours and project status, admin management of any team member's time entries, timeline notes, report grouping, and activity tracking for the Dia browser.
NocoBase is a self-hosted low-code platform, currently building 2.2.0 in the open across alpha and beta pre-releases. The visible work splits between a client v2 rewrite — tabs, subpages and pop-ups gaining linkage rules, configurable route entry modes — and an AI employees layer that is being connected to the platform's JS blocks in both directions.
The AI employees feature started as an assistant sitting beside the app. These releases dissolve that boundary: JS blocks can trigger AI employee tasks through a RunJS API, and AI employees now have frontend tools that operate JS blocks. Custom application logic and the agent layer become mutually callable, which is a different product than a chat panel bolted onto a builder. Around it, the approval workflow is being ported to client v2 with card-style selection and inline usage instructions.
With the call path open in both directions, the unresolved question these entries raise is governance — what an AI employee is permitted to execute and under whose authority — so expect permission scoping around AI employee tasks before 2.2.0 stabilizes.
Rize's last two releases are pure repair: black screens on Windows, frozen dashboards, unreliable auto-updates, widget timers, app size, and sign-in hardening, with settings sync across machines as the one additive item. That follows a dense May in which Rize shipped an MCP server exposing profitability and event data, in-app chat over that data, a Slack agent for asking about hours and project status, admin management of any team member's time entries, timeline notes, report grouping, and activity tracking for the Dia browser.
The May burst reframed what Rize is: not a tracker whose output is a dashboard, but a time dataset an assistant can interrogate — in the app, in Slack, or through any MCP client, with profitability and utilization exposed rather than just hours. The two months since suggest that expansion outran the desktop client's stability, and the current work is paying that down. Note also who the recent features serve: admin time-entry editing, source labels distinguishing AI from user entries, team titles, and per-client profitability are all manager surfaces, not individual-focus-tracker surfaces.
Once the stability work settles, the agent surface is the obvious place to resume — more MCP tools over the same profitability and event data, or write actions rather than read-only questions. The entries do not show whether the Slack agent gains a peer on other chat platforms.
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 NocoBase or Rize.
Celoxis publishes PMO thought-leadership at pace; the product ships out of view.
Process Street's blog buries the actual news: it has an MCP server
FuseBase is rebuilding its client-portal product around structured AI app building.
Notesnook ships desktop and mobile on a two-week clock, with the details kept off the feed.
Atlassian threw out Rovo's multi-agent router for one long-horizon reasoning loop.
Aha! is turning a roadmapping suite into a place where the app gets built and tested.
See all NocoBase alternatives → · See all Rize alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ai-agents — within PM. NocoBase 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. NocoBase 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 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.
Top Rize alternatives in PM are ranked by recent ship velocity. Browse the "Rize alternatives" section above for the current picks, or visit /alternatives/rize for the full list with editorial commentary on each.