Wagepoint
Wagepoint's news is its accountant channel, not its software
A side-by-side editorial comparison of TimeTagger and Jorani — release velocity, themes, recent moves, and the top alternatives to consider.
A time tracker that ships twice a year and spends it on self-hosters.
TimeTagger is a self-hosted time tracker maintained by a small core with a steady stream of outside contributions. Releases land two or three times a year and bundle whatever community PRs arrived rather than a planned roadmap. Recent work concentrates on the deployment and integration surface — an API for external tooling, a hardened default binding, offline usage — rather than the tracking UI itself.
A dormant leave-management app returns with an MIT relicense and a hard break from its own API
Jorani is a self-hosted leave and overtime management app built on legacy CodeIgniter PHP. After a three-year gap, v1.0.4 arrives labelled a maintenance release but is anything but conservative: it relicenses from AGPL to MIT, moves the repository to a new organization, and deletes the Basic Auth REST API, the client-side password encryption layer and MySQL 5.7 support. The database schema is untouched, so the disruption is entirely in licensing, packaging and interfaces rather than data.
TimeTagger is a self-hosted time tracker maintained by a small core with a steady stream of outside contributions. Releases land two or three times a year and bundle whatever community PRs arrived rather than a planned roadmap. Recent work concentrates on the deployment and integration surface — an API for external tooling, a hardened default binding, offline usage — rather than the tracking UI itself.
The center of gravity has moved from the timeline UI toward how an instance is run and scripted against. v25.12.1 added a version endpoint and server-side record filters, which are the pieces an operator needs to automate against a deployment; v24.12.2 moved the default bind to loopback after an auth gap. The app-facing changes in the same window are smaller and mostly contributed.
The next release will most likely extend the records API further, since that is where the last cycle of contributions concentrated. The two-releases-a-year cadence gives no basis for predicting when.
Jorani is a self-hosted leave and overtime management app built on legacy CodeIgniter PHP. After a three-year gap, v1.0.4 arrives labelled a maintenance release but is anything but conservative: it relicenses from AGPL to MIT, moves the repository to a new organization, and deletes the Basic Auth REST API, the client-side password encryption layer and MySQL 5.7 support. The database schema is untouched, so the disruption is entirely in licensing, packaging and interfaces rather than data.
The long arc is a small project shedding weight. Releases through 2017 filled in the workflow model — cancellation states, SSO, mandatory rejection comments, a steady stream of translations. Version 1.0.0 in 2020 rebuilt the leave-balance engine and documented an OpenAPI surface, and the two releases since have been almost entirely security and PHP-version compatibility. v1.0.4 continues by removing rather than adding, including the very API 1.0.0 had documented, and folds the old tree under a legacy/ directory — which reads as groundwork for a replacement rather than a destination.
The legacy/ layout and the withdrawn REST API point to a new API and a non-legacy codebase as the next move; the entries don't indicate on what stack, or when.
Other HR 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 TimeTagger or Jorani.
Wagepoint's news is its accountant channel, not its software
Ever Gauzy turned its dashboard into a composable canvas, then filled it with 47 widgets in a week.
iCIMS publishes labor-market research on a cadence its product changelog never matches.
UK HR and payroll software running a pure search-acquisition feed
An ATS opening its pipeline to AI assistants while screening moves into every stage
Sling's feed is shift-scheduling SEO on a fortnightly cadence; no product release appears.
See all TimeTagger alternatives → · See all Jorani alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. TimeTagger and Jorani are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. TimeTagger and Jorani are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other HR products to evaluate alongside.
Top TimeTagger alternatives in HR are ranked by recent ship velocity. Browse the "TimeTagger alternatives" section above for the current picks, or visit /alternatives/timetagger for the full list with editorial commentary on each.
Top Jorani alternatives in HR are ranked by recent ship velocity. Browse the "Jorani alternatives" section above for the current picks, or visit /alternatives/jorani for the full list with editorial commentary on each.