TimeTagger
A time tracker that ships twice a year and spends it on self-hosters.
A side-by-side editorial comparison of Jorani and Fountain — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Jorani | Fountain |
|---|---|---|
| Sector | HR | HR |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 1 |
| Top themes | hr, leave-management, self-hosted, php | frontline-hiring, ai-agents, automation, recruiting |
| Last editorial update | 1h ago | 7d 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.
Fountain wires autonomous scheduling into Cue and per-customer instances into Sam
Fountain's frontline-hiring platform is layering AI agents onto its core products: Cue, the assistant users prompt for hiring insight, and Sam, a workforce-facing agent. This cycle both agents get meaningfully more capable — Cue can now run recurring work on its own schedule, and Sam becomes a configurable per-customer instance. Alongside the agent work, Fountain is reconciling data between its Source and Hire products so hire counts finally agree.
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.
Fountain's frontline-hiring platform is layering AI agents onto its core products: Cue, the assistant users prompt for hiring insight, and Sam, a workforce-facing agent. This cycle both agents get meaningfully more capable — Cue can now run recurring work on its own schedule, and Sam becomes a configurable per-customer instance. Alongside the agent work, Fountain is reconciling data between its Source and Hire products so hire counts finally agree.
The direction is agent-native frontline hiring: Fountain is moving Cue from a reactive prompt box toward an operator that acts on a cadence without being asked, and turning Sam into tenant-specific configuration rather than one shared assistant. The parallel Source/Hire data-unification and campaign-lifecycle work is the connective tissue that makes those agents trustworthy across the suite.
Expect Cue's autonomous task surface to widen — more task types, triggers, and outputs — and Sam's per-customer configuration to deepen. Continued Source/Hire consolidation suggests the two products keep converging on a single data model.
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 Fountain.
A time tracker that ships twice a year and spends it on self-hosters.
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
See all Jorani alternatives → · See all Fountain alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fountain 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. Fountain 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 Fountain alternatives in HR are ranked by recent ship velocity. Browse the "Fountain alternatives" section above for the current picks, or visit /alternatives/fountain for the full list with editorial commentary on each.