Leantime vs RescueTime
Side-by-side trajectory, velocity, and editorial themes.
Leantime is stabilizing its big 3.9 rewrite while extending cross-project planning and a mobile API
Leantime is deep in a modernization cycle. The 3.9.0 release rebuilt the app around a native, fail-closed permission engine, a JSON-RPC API, and a consolidated Blueprints domain; the releases since then mostly stabilize that foundation. Recent point releases fix regressions (repeated Bearer/PAT auth fixes) while adding cross-project program views and a mobile app backend.
The work is consolidation over expansion: hardening the new auth/permission and API layers, closing security IDORs domain by domain, and building the surface a mobile app and program-level planning need. The steady stream of small patch releases reflects shaking out regressions from the 3.9.0 refactor rather than opening new product directions.
Expect continued point releases fixing regressions from the permission-engine and JSON-RPC migration, plus buildout of the Leantime Mobile app now that its Bearer-authenticated backend API is landing.
RescueTime's feed is all blog essays — no product signal to read
The crawled feed for RescueTime is its marketing blog, not a product changelog. Every entry is an opinion essay on work culture — busyness, meeting cost, hybrid teams, freelancing, time-blocking — with no reference to the RescueTime time-tracking product's features, releases, or fixes. There is no shipping activity to interpret here.
Nothing about the product's direction can be inferred from these posts; they reflect a content-marketing cadence, not engineering output. To produce meaningful commentary the signal source needs to be repointed from blog.rescuetime.com to an actual release or changelog feed.
Insufficient data: this feed carries no product releases, so no next product move can be predicted from it.
See more alternatives to Leantime →
See more alternatives to RescueTime →