Bullhorn
Bullhorn's feed is labor-market research and SMB advice, not release notes
A side-by-side editorial comparison of Jorani and Workable — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Workable is localizing hard while its hiring agent quietly gets adjustable.
Two threads dominate. Localization is being pushed on both sides at once: the interface now ships in French, Canadian French, Danish and Dutch, and candidate-facing language kits expanded from five languages to nine. The other thread is the Workable Agent, generally available in June to run sourcing, screening and qualification against an ideal candidate profile, and now editable — teams can rewrite criteria, add or remove must-haves, and re-evaluate an existing pipeline against the revised profile at one credit per candidate.
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.
Two threads dominate. Localization is being pushed on both sides at once: the interface now ships in French, Canadian French, Danish and Dutch, and candidate-facing language kits expanded from five languages to nine. The other thread is the Workable Agent, generally available in June to run sourcing, screening and qualification against an ideal candidate profile, and now editable — teams can rewrite criteria, add or remove must-haves, and re-evaluate an existing pipeline against the revised profile at one credit per candidate.
The Agent has moved from launch to operability in two months: the interesting release was not making it autonomous but letting a recruiter change its mind and replay the pipeline. That, plus credit-metered re-evaluation, tells you Workable is selling agent output as something to be corrected rather than trusted outright. Around it the platform keeps widening past the ATS — employee surveys, headcount reporting, entity-scoped HR admin — which is the HRIS build-out competing for the same seat. Localization serves both, and is the cheapest way to reach markets where an English-only ATS was disqualifying.
Mobile app localization is stated as coming, and the language-kit and interface lists will likely converge. On the Agent, per-criterion transparency — why a candidate scored as they did — is the natural follow-on to letting teams edit the criteria.
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 Workable.
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.
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
Miter added accounts payable and opened a free API — it's no longer just construction payroll.
See all Jorani alternatives → · See all Workable alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Workable is currently shipping more aggressively (velocity 5.0 vs 0.0), 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. Workable is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Workable alternatives in HR are ranked by recent ship velocity. Browse the "Workable alternatives" section above for the current picks, or visit /alternatives/workable for the full list with editorial commentary on each.