Atlassian
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
A side-by-side editorial comparison of Everhour and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
The time-tracking product is invisible behind a steady run of comparison roundups.
The feed carries the Everhour marketing blog, not a release channel. The last ten items are ranked-list roundups and definitional posts — best timesheet software, twenty employee time trackers, what time theft is — with Everhour appearing as one entry among competitors in its own comparisons. Cadence is roughly weekly and has been consistent since late June.
Wakapi is quietly rebuilding itself around the login and container requirements teams ask for.
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 also carried a responsibly disclosed security fix and dropped its relay endpoint. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.
The feed carries the Everhour marketing blog, not a release channel. The last ten items are ranked-list roundups and definitional posts — best timesheet software, twenty employee time trackers, what time theft is — with Everhour appearing as one entry among competitors in its own comparisons. Cadence is roughly weekly and has been consistent since late June.
Coverage is widening outward from time tracking into workforce management, employee scheduling, attendance, and remote-team operations. That suggests a keyword strategy chasing larger adjacent search categories rather than defending the narrow time-tracking term. Whether the product is following the content into scheduling and workforce management is not something this feed can answer.
More ranked roundups on the same weekly rhythm, extending into HR and payroll-adjacent queries. Product movement stays unreadable until Everhour exposes an actual changelog.
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 also carried a responsibly disclosed security fix and dropped its relay endpoint. 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 with no shell are the requirements that come from someone else's security review, not from a hobbyist's wishlist. The corresponding cost is visible too: dropped MSSQL support and a Docker base change that forces SQLite users to fix directory permissions by hand.
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 Everhour or Wakapi.
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
Phorge tags a release per fix, and years pass between the ones that reach this feed.
Zoho Projects makes time tracking the product's center of gravity, and lets Zia build the schema.
Jira is being pushed upward — from tracking the work to judging its cost, risk and business health.
Steady small-surface polish across Basecamp and HEY, with no directional move.
Linear stopped being where work is described and became where it gets started.
See all Everhour 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. Everhour 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. Everhour 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 Everhour alternatives in PM are ranked by recent ship velocity. Browse the "Everhour alternatives" section above for the current picks, or visit /alternatives/everhour 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.