My Hours
My Hours adds an audit trail to its timesheet approval cycle.
A side-by-side editorial comparison of Huly and Unito — release velocity, themes, recent moves, and the top alternatives to consider.
Huly ships near-weekly builds, but its release notes say almost nothing about what changed.
Huly's GitHub releases are a steady run of s0.7.x tags, roughly one every few days through July, each published as a bare 'merge develop' note. The only titled entries are a package update and a test fix. Readers get a cadence signal, not a feature signal.
Unito is repositioning two-way sync as "AI context", and the blog is doing the argument.
Unito's feed has pivoted from integration how-tos to a sustained argument about AI context — a whitepaper plus two supporting posts published within roughly a day of each other, defining AI context as a connected, current picture of how an organisation works. The older posts underneath it are the familiar material: Asana-Jira sync walkthroughs, phased tool migrations, distributed engineering teams keeping Jira and Azure DevOps in step. The through-line is that the same two-way sync engine is now being sold as the thing that feeds AI rather than the thing that spares a migration.
Huly's GitHub releases are a steady run of s0.7.x tags, roughly one every few days through July, each published as a bare 'merge develop' note. The only titled entries are a package update and a test fix. Readers get a cadence signal, not a feature signal.
The tag stream shows active development on the 0.7 line, but the releases record no user-facing changes, so the direction of the product cannot be read from them. The feed also goes quiet after 1 August, which is either a pause in tagging or a move to a different release channel.
The entries do not support a confident call on Huly's next feature; the clearest observable signal would be whether s0.7.x tagging resumes after the August gap.
Unito's feed has pivoted from integration how-tos to a sustained argument about AI context — a whitepaper plus two supporting posts published within roughly a day of each other, defining AI context as a connected, current picture of how an organisation works. The older posts underneath it are the familiar material: Asana-Jira sync walkthroughs, phased tool migrations, distributed engineering teams keeping Jira and Azure DevOps in step. The through-line is that the same two-way sync engine is now being sold as the thing that feeds AI rather than the thing that spares a migration.
This is a positioning move made in content before it is visible in product. Sync has been a commodity integration category for years; framing the synced graph as the context layer AI tools need is an attempt to move up the stack without changing what the engine does. The coordinated whitepaper-and-explainer launch suggests a campaign rather than an experiment. Whether any of this corresponds to shipped capability is not something this feed shows.
Expect the AI-context framing to keep expanding through the blog, and to start appearing in product surfaces — an MCP endpoint or an AI-facing view of the synced graph would be the natural follow-through. These entries do not confirm such a feature exists yet.
Other PM 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 Huly or Unito.
My Hours adds an audit trail to its timesheet approval cycle.
Tracecat is hardening its embedded Claude Code agents one guardrail at a time.
Hive is turning App Studio and Workflows into the admin's control panel.
RentRedi is taking maintenance and money work off the landlord's desk.
Atarim's AI agency now comes with a clock on every stalled job.
Camunda is in release-candidate mode as 8.10 heads for stable.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Unito 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. Unito 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 PM products to evaluate alongside.
Top Huly alternatives in PM are ranked by recent ship velocity. Browse the "Huly alternatives" section above for the current picks, or visit /alternatives/huly for the full list with editorial commentary on each.
Top Unito alternatives in PM are ranked by recent ship velocity. Browse the "Unito alternatives" section above for the current picks, or visit /alternatives/unito for the full list with editorial commentary on each.