Leantime vs Rize
Side-by-side trajectory, velocity, and editorial themes.
Leantime swaps its rich-text engine, ships experimental PostgreSQL, and spends a month fixing the fallout.
Leantime just landed 3.7, which replaced TinyMCE with a Tiptap-based editor across every rich-text surface, redesigned the wiki, and added experimental PostgreSQL support beside MySQL/MariaDB. The three follow-up patches in three weeks are real bug-fix work — PostgreSQL ROUND/GROUP BY errors, ticket PATCH 500s, session lifetime regressions — not cosmetic tidying. The team also pushed accessibility to WCAG 2.1 AA in the prior 3.6 line.
Leantime is mid-modernization: editor stack, database portability, and design-system tokens are all moving at once. The volume of PostgreSQL-specific bug fixes since 3.7.0 suggests Postgres is being driven by real users hitting real edges, not just a checklist item. Editor-related fixes show Tiptap migration is still settling in.
Expect 3.7.4 within a couple of weeks closing the remaining migration-era bugs, then a clearer 3.8 push around design-token rollout or PostgreSQL going non-experimental.
Rize pivots from passive tracker to live, AI-queryable work data substrate.
Rize landed two directional moves in the last 30 days: live time-entry creation that replaces the previous batched-after-the-fact model, and a Beta MCP server that exposes time tracking data to Claude and ChatGPT for natural-language analysis. Around those, the team rebuilt the time-entry review panel and added an alternative Work Hours calculation that excludes break time the way most teams actually want. Cadence is high and the releases are coherent, not scattered.
The product is repositioning itself from 'passive tracker that classifies activity later' to 'live work-data platform other AI tools can read.' MCP integration signals Rize wants to be the data layer external assistants reach into, not a self-contained reporting app. The live-entries shift is the user-experience counterpart: data is current and editable in the moment instead of reconstructed later.
Expect the next moves to lean into the new substrate: manager-facing project-overrun alerts, budget-vs-actual dashboards, or richer outbound webhooks. A natural follow-on is broader MCP exposure (write-side actions, not just read), or a chat surface inside Rize itself.
See more alternatives to Leantime →
See more alternatives to Rize →