Hive vs Kanri

Hive publishes its changelog as clusters of single-feature entries dated the same day — seven on August 18, three on August 14. The current batch splits between planning integrity (time estimates surviving assignee changes, a rebuilt Unsubmitted Timesheets view, reorderable Gantt columns), governance (a default restricted-member role applied across every onboarding path, custom-field edits appearing in activity feeds), and small chat conveniences. Nothing in the batch is a new product area; it is the existing surface being tightened.

Two themes have been running through recent batches. The first is making planned time trustworthy — estimates that no longer vanish when work is reassigned, timesheet views built for scanning who has not submitted. The second is administrative control that scales: a least-privilege default that holds across SAML, SCIM, invite links and domain auto-join, and an audit trail that now covers custom-field edits. Both point at larger deployments, where the failure modes are silent data loss and inconsistent permissions rather than missing features.

The audit-trail and permissions work looks incomplete rather than finished — activity coverage for other object types and per-field visibility rules are the obvious next steps. Expect the same batched cadence, roughly twice a month.