Release notes
What’s new in Yugmir Kinetic
Every release, what changed, and whether it affects how you deploy.
Version 1.0 Current
The first public release of Yugmir Kinetic for Revit.
Deployment and control
- Channels. Assign users to Production or Beta and publish to each independently
- Promotion and rollback. Promoting snapshots the previous state first, so rollback is a single action
- Optional two-person approval before anything reaches Production, with self-approval refused
- Revocation. Withdraw a tool centrally; it greys out everywhere with your reason attached
- Role-based access by Windows user or Active Directory group
Reliability
- Crash isolation. A failing tool is caught, reported plainly, and benched after repeated failures
- Safe Mode. Hold Shift while Revit starts to load core only and reset quarantined tools
- Mid-session sync that skips files currently in use rather than failing, and applies them on the next start
- Offline-first licensing with a grace window, so a dropped connection doesn’t lock anyone out
Visibility
- Fleet and ROI reporting — hours saved from successful runs, success rate, crashes by tool, adoption and Revit-version spread, exportable to CSV
- Hash-chained audit log of every governance action
- Per-user telemetry written to your own file server, with firm-level and per-user consent controls
Compatibility
- Revit 2019 through 2027
- Two Revit versions running side by side during a migration year
- Everything installs locally — no runtime dependency on our infrastructure
Upgrading or evaluating? The governance page covers how each control behaves, including which ones require code signing to become active.