← Back to home
Comparison · PM

My Hours vs Wakapi

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

Shared themes:time-tracking

My Hours vs Wakapi: at a glance

FeatureMy HoursWakapi
SectorPMPM
Velocity score6.32.5
Sparks · 30d10
Top themestime-tracking, mcp, ai-native, invoicingtime-tracking, self-hosted, oidc, auth-bypass
Last editorial update5d ago28d ago
WebsiteVisit →Visit →

What is My Hours?

My Hours launches a Claude MCP connector, making AI-driven time logging a first-class workflow

My Hours is a time tracking platform with a strong invoicing and reporting core, now shipping in two distinct directions: an AI integration layer (Claude MCP connector, Sep 3) and expanded compliance-friendly tracking features (break tracking with payroll calculations, attendance reports, budget alerts). The September releases represent the most capability-dense period in the window, following a patch-heavy summer. The MCP connector runs on Keboola's Cloudflare infrastructure — zero install, OAuth-only.

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

My Hours vs Wakapi: editorial side-by-side

M6.3

My Hours launches a Claude MCP connector, making AI-driven time logging a first-class workflow

◆ Current state

My Hours is a time tracking platform with a strong invoicing and reporting core, now shipping in two distinct directions: an AI integration layer (Claude MCP connector, Sep 3) and expanded compliance-friendly tracking features (break tracking with payroll calculations, attendance reports, budget alerts). The September releases represent the most capability-dense period in the window, following a patch-heavy summer. The MCP connector runs on Keboola's Cloudflare infrastructure — zero install, OAuth-only.

◆ Where it's heading

The Claude MCP connector signals a clear strategic bet: My Hours wants to be the time tracking tool you interact with through AI conversation rather than through a timer UI. The infrastructure choice (remote server on Cloudflare, not a local install) removes adoption friction, making it viable for teams already using Claude. Parallel development on attendance reports and break tracking points toward a compliance and HR use case — overtime tracking, payroll-ready break records — that broadens My Hours beyond professional services billing.

◆ Prediction

The MCP integration will expand to cover write operations beyond time logging — budget tracking, invoice creation, and report export are the most obvious additions. The attendance report launched in August suggests a near-term push toward HR and payroll integrations, potentially positioning My Hours against more compliance-focused tools like Harvest or Timely for regulated industries.

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 My Hours 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 My Hours or Wakapi.

See all My Hours alternatives → · See all Wakapi alternatives →

Recent activity from My Hours and Wakapi

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

  1. 6d agoMy HoursBreaks, simpler clocking & bulk edit for Basic (9.10.0)
  2. 13d agoMy HoursMy Hours MCP for Claude
  3. 15d agoMy HoursTask budget alerts, invoice references & Jira sync (9.9.0)
  4. 27d agoMy HoursAttendance report, budget tracking & invoice links (9.8.0)
  5. 28d agoWakapiCritical auth bypass from a shared cache key namespace
  6. 1mo agoMy HoursBug fixes (9.6.1)
  7. 1mo agoMy HoursCustom field filters, view settings & invoicing improvements (9.6.0)
  8. 2mo agoWakapiRelease 2.17.5
  9. 3mo agoWakapiRelease 2.17.4
  10. 5mo agoWakapiSecurity fix, relay endpoint dropped, summaries may need regenerating
  11. 6mo agoWakapiDistroless nonroot container image; SQLite permissions need fixing
  12. 7mo agoWakapiOIDC-only login mode disables local accounts

Frequently asked questions

What is the difference between My Hours and Wakapi?

Both compete on the same themes — time-tracking — within PM. My Hours is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 My Hours better than Wakapi?

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

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