← Back to home
Comparison · PM

Leantime vs Wakapi

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

Shared themes:self-hosted

Leantime vs Wakapi: at a glance

FeatureLeantimeWakapi
SectorPMPM
Velocity score6.32.5
Sparks · 30d00
Top themesproject-management, self-hosted, api, permissionstime-tracking, self-hosted, oidc, auth-bypass
Last editorial update1mo ago1h ago
WebsiteVisit →Visit →

What is Leantime?

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.

Read the full Leantime 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 →

Leantime vs Wakapi: editorial side-by-side

L6.3

Leantime is stabilizing its big 3.9 rewrite while extending cross-project planning and a mobile API

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

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 Leantime 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 Leantime or Wakapi.

See all Leantime alternatives → · See all Wakapi alternatives →

Recent activity from Leantime and Wakapi

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

  1. 7h agoWakapiCritical auth bypass from a shared cache key namespace
  2. 1mo agoWakapiRelease 2.17.5
  3. 1mo agoLeantimeLeantime 3.9.8: milestone reporting and MCP endpoint fixes
  4. 1mo agoLeantimeLeantime 3.9.7 adds cross-project program views
  5. 1mo agoLeantimeLeantime 3.9.6: security hardening plus content templates
  6. 2mo agoLeantimeLeantime 3.9.5 adds mobile notification and calendar APIs
  7. 2mo agoLeantimeLeantime 3.9.4 fixes cross-project 'My Work' loading
  8. 2mo agoLeantimeLeantime 3.9.3 fixes Bearer-token API authentication
  9. 2mo agoWakapiRelease 2.17.4
  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 Leantime and Wakapi?

Both compete on the same themes — self-hosted — within PM. Leantime is currently shipping more aggressively (velocity 6.3 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 Leantime better than Wakapi?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Leantime is currently shipping more aggressively (velocity 6.3 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 Leantime?

Top Leantime alternatives in PM are ranked by recent ship velocity. Browse the "Leantime alternatives" section above for the current picks, or visit /alternatives/leantime 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.