Process Street
Process Street's public feed is an SEO content engine, not a changelog.
A side-by-side editorial comparison of Timeneye and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Timeneye became Lucen Track, then turned a timer into a system of record.
The product was renamed from Timeneye to Lucen Track in May as its parent rebranded to Lucen Software, and as of August it sits behind a shared login across the Lucen suite with a redesigned interface. Underneath the rebrand, the last four months added time off tracking with approvals and holidays, global non-billable phases and tags, Enterprise custom fields across every object, and an MCP server that lets AI assistants read and write time entries. Shipping cadence is roughly twice a month with real features each time.
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
Wakapi's recent releases cluster around identity and deployment rather than time tracking itself: OpenID Connect login, then an OIDC-only mode, multiple API keys per user, and a switch from Alpine to a distroless nonroot container image. The 2.17.x line has carried two security fixes now — a responsibly disclosed issue in 2.17.3, and a critical authentication bypass in 2.17.6 caused by a shared cache key namespace. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.
The product was renamed from Timeneye to Lucen Track in May as its parent rebranded to Lucen Software, and as of August it sits behind a shared login across the Lucen suite with a redesigned interface. Underneath the rebrand, the last four months added time off tracking with approvals and holidays, global non-billable phases and tags, Enterprise custom fields across every object, and an MCP server that lets AI assistants read and write time entries. Shipping cadence is roughly twice a month with real features each time.
Two things are happening at once. The visible one is consolidation — one login, one Entra app, one design language across Lucen products, which is what a company assembling a suite does before it starts cross-selling. The less visible one is that Track keeps absorbing the work that used to happen around the timesheet: absence requests, billability rules, business-specific fields, and now programmatic access. Each addition makes Track the place the billing data is finished rather than a feed into something else.
The unified login and the suite framing point to cross-product features next — shared reporting or a single admin surface across Lucen products — with the Enterprise plan continuing to absorb the newest capabilities as custom fields did.
Wakapi's recent releases cluster around identity and deployment rather than time tracking itself: OpenID Connect login, then an OIDC-only mode, multiple API keys per user, and a switch from Alpine to a distroless nonroot container image. The 2.17.x line has carried two security fixes now — a responsibly disclosed issue in 2.17.3, and a critical authentication bypass in 2.17.6 caused by a shared cache key namespace. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.
The direction is a self-hosted tool making itself deployable somewhere other than one developer's server. External identity providers, an option to disable local login entirely, per-key credentials and a container that runs as a nonroot user are the requirements that come from someone else's security review. The 2.17.6 bypass sits awkwardly against that: a cache keyed without proper namespacing is exactly the class of bug that multi-tenant deployment surfaces, which suggests the auth work is now being exercised harder than the code was written for. Releases have also thinned to roughly one a month from a much faster earlier cadence.
The identity and packaging thread is the only sustained one in this feed, so further hardening in that area is the most likely continuation; the sparse release notes make anything more specific guesswork.
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 Timeneye or Wakapi.
Process Street's public feed is an SEO content engine, not a changelog.
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
Hive ships in batches, and this one is all planning accuracy and admin control.
Plane ships a fortnightly digest, and the AI layer is where the real work is going.
Ever Teams shipped ten tags in twelve hours and one of them touched the product
Asana's agent left the app — it now answers work questions inside Slack threads.
See all Timeneye alternatives → · See all Wakapi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — time-tracking — within PM. Timeneye is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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. Timeneye is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 Timeneye alternatives in PM are ranked by recent ship velocity. Browse the "Timeneye alternatives" section above for the current picks, or visit /alternatives/timeneye for the full list with editorial commentary on each.
Top Wakapi alternatives in PM are ranked by recent ship velocity. Browse the "Wakapi alternatives" section above for the current picks, or visit /alternatives/wakapi for the full list with editorial commentary on each.