← Back to home
Comparison · PM

Timeneye vs Wakapi

A side-by-side editorial comparison of Timeneye and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:time-tracking

Timeneye vs Wakapi: at a glance

FeatureTimeneyeWakapi
SectorPMPM
Velocity score5.02.5
Sparks · 30d00
Top themestime-tracking, rebrand, mcp, billabilitytime-tracking, self-hosted, oidc, auth-bypass
Last editorial update15d ago1h ago
WebsiteVisit →Visit →

What is Timeneye?

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.

Read the full Timeneye trajectory →

What is Wakapi?

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.

Read the full Wakapi trajectory →

Timeneye vs Wakapi: editorial side-by-side

T5.0

Timeneye became Lucen Track, then turned a timer into a system of record.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

W2.5

A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to Timeneye and Wakapi

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.

See all Timeneye alternatives → · See all Wakapi alternatives →

Recent activity from Timeneye and Wakapi

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 7h agoWakapiCritical auth bypass from a shared cache key namespace
  2. 16d agoTimeneyeUnified Lucen login and a redesigned Track interface
  3. 1mo agoWakapiRelease 2.17.5
  4. 1mo agoTimeneyeCustom fields across clients, projects, entries, and users
  5. 2mo agoTimeneyeGlobal non-billable phases and tags for T&M projects
  6. 2mo agoTimeneye🤖 Your AI tools can now connect directly to Lucen Track
  7. 2mo agoWakapiRelease 2.17.4
  8. 2mo agoTimeneye🏝️ Time Off tracking available in Lucen Track!
  9. 3mo agoTimeneyeImportant update: Timeneye is now called Lucen Track
  10. 4mo agoWakapiSecurity fix, relay endpoint dropped, summaries may need regenerating
  11. 5mo agoWakapiDistroless nonroot container image; SQLite permissions need fixing
  12. 6mo agoWakapiOIDC-only login mode disables local accounts

Frequently asked questions

What is the difference between Timeneye and Wakapi?

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.

Is Timeneye better than Wakapi?

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.

What are the best alternatives to Timeneye?

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.

What are the best alternatives to Wakapi?

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.