Timeneye vs Leantime
Side-by-side trajectory, velocity, and editorial themes.
Timeneye, now Lucen Track, adds MCP access and rounds out time tracking
Timeneye rebranded to Lucen Track and is filling the gaps of a serious time-tracking tool: custom fields across every object, global non-billable phases and tags, time-off tracking with approvals, and an Outlook add-in. The standout is an MCP server that lets AI assistants read and write time entries directly.
The product is maturing from timesheets toward a configurable work-and-billing record while opening an AI-interop surface. The MCP server bets that users will manage time through assistants like Claude and Cursor rather than only the app UI, alongside steadier depth work in billability and custom fields.
Expect the AI/MCP surface to deepen with more actions and reporting exposed to assistants, plus continued billing-side depth as the non-billable and custom-field work points toward richer invoicing. The rebrand hints at more products consolidating under the Lucen umbrella.
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.
See more alternatives to Timeneye →
See more alternatives to Leantime →