Bullhorn
Bullhorn's feed is labor-market research and SMB advice, not release notes
A side-by-side editorial comparison of Jorani and Tanda — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Jorani | Tanda |
|---|---|---|
| Sector | HR | HR |
| Velocity score | 0.0 | 8.8 |
| Sparks · 30d | 0 | 1 |
| Top themes | hr, leave-management, self-hosted, php | workforce management, australian payroll, rostering compliance, child employment law |
| Last editorial update | 19d ago | 2d ago |
| Website | Visit → | — |
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.
Tanda starts encoding state statute into the roster itself, not just the pay run.
Tanda ships several short, specific notes a week across Australian rostering, payroll and HR. The current window adds automated child employment law validation in rosters, a rebuilt child support deduction flow that moves reference numbers from employee profiles to the company file, a per-question training response report, and a toggle to hide the graph and table in Roster Day View. Two of the four are regulatory mechanics; the compliance work is where the substance sits.
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.
Tanda ships several short, specific notes a week across Australian rostering, payroll and HR. The current window adds automated child employment law validation in rosters, a rebuilt child support deduction flow that moves reference numbers from employee profiles to the company file, a per-question training response report, and a toggle to hide the graph and table in Roster Day View. Two of the four are regulatory mechanics; the compliance work is where the substance sits.
The direction is compliance moving upstream — out of payroll reconciliation and into the moment a manager builds a roster. Child employment rules are not calculated after the fact but checked at publish time, with a new School Details record on under-18 profiles supplying the inputs and a configurable warn-or-block setting deciding how hard the rule bites. The child support change follows the same logic from the other end: strip per-employee configuration that was error-prone and move the single source of truth to the company file.
Expect the same treatment applied to further award and state-level rules — statutory constraints turned into roster validations with a warn/block switch — and continued consolidation of settings that currently live on individual employee profiles.
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 Jorani or Tanda.
Bullhorn's feed is labor-market research and SMB advice, not release notes
Zoho Recruit opened the ATS to AI tools via MCP, then spent the summer closing integration gaps.
Workable is localizing hard while its hiring agent quietly gets adjustable.
Wagepoint put AI at the payroll approval gate, then spent a week arguing about where else it belongs.
Eightfold has moved from screening candidates to running the interview loop itself.
Gauzy's React rewrite becomes a tenant-level switch, and its AI chat learns to listen
See all Jorani alternatives → · See all Tanda alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Tanda is currently shipping more aggressively (velocity 8.8 vs 0.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Tanda is currently shipping more aggressively (velocity 8.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other HR products to evaluate alongside.
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.
Top Tanda alternatives in HR are ranked by recent ship velocity. Browse the "Tanda alternatives" section above for the current picks, or visit /alternatives/tanda for the full list with editorial commentary on each.