Bullhorn
Bullhorn's feed is labor-market research and SMB advice, not release notes
A side-by-side editorial comparison of Jorani and Workyard — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Jorani | Workyard |
|---|---|---|
| Sector | HR | HR |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 1 |
| Top themes | hr, leave-management, self-hosted, php | ai-assistant, time-tracking, payroll-export, job-costing |
| Last editorial update | 19d ago | 8d 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.
Workyard's Time Assistant now does the pre-payroll cleanup a bookkeeper used to do by hand.
Workyard is building on two fronts. The AI Time Assistant has moved from fixing clock times and breaks to reading worker notes, proposing exact edits, reallocating hours across projects and cost codes from a plain-language request, and is now delegated down to managers scoped to their own crews. Separately, the back-office edge keeps widening: Acumatica sync, time off in QuickBooks Online exports, expense transaction exports to NetSuite and QuickBooks Desktop, and auto top-up for expense card funding.
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.
Workyard is building on two fronts. The AI Time Assistant has moved from fixing clock times and breaks to reading worker notes, proposing exact edits, reallocating hours across projects and cost codes from a plain-language request, and is now delegated down to managers scoped to their own crews. Separately, the back-office edge keeps widening: Acumatica sync, time off in QuickBooks Online exports, expense transaction exports to NetSuite and QuickBooks Desktop, and auto top-up for expense card funding.
The assistant is being positioned as the pre-payroll review layer, where every change is a proposal the approver accepts rather than an automated write. Note-reading and cost-code reallocation together cover most of what made timecard cleanup a manual pass. Meanwhile the integration work is aimed at the same outcome from the other side: getting GPS-verified field hours into payroll and accounting systems without re-keying, which is what makes accurate job costing worth anything.
Time Assistant should reach the mobile app for managers and admins next, as the manager release states, and the approval-with-diff pattern is the likely template for any further automation Workyard applies to timecards.
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 Workyard.
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 Workyard alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Workyard is currently shipping more aggressively (velocity 7.5 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. Workyard is currently shipping more aggressively (velocity 7.5 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 Workyard alternatives in HR are ranked by recent ship velocity. Browse the "Workyard alternatives" section above for the current picks, or visit /alternatives/workyard for the full list with editorial commentary on each.