YugmirOne way to ship engineering tools across your firm.
Kinetic publishes your in-house tools to Revit, AutoCAD and ETABS from a single folder on your own network drive. Update once and every seat picks it up — without a reinstall, an IT ticket, or anyone restarting the application.
The problem isn’t writing the tool. It’s everything after.
Most firms already have useful in-house tools. What they don’t have is a safe way to get them onto sixty machines — and take them back off when one misbehaves.
So tools get copied to a network folder and loaded blindly. Nobody knows which version each person is running. A bad script reaches everyone at once. When a tool corrupts a model at 4pm on a deadline, there is no way to switch it off except calling people one by one.
Kinetic treats tool deployment as something that should be staged, reversible and accountable — the same way you would treat any other software going into production.
One platform, three hosts
The same publishing model everywhere: a tool is a folder, and the folder name builds the ribbon. Authors move between hosts without relearning anything.
Yugmir Kinetic for Revit Available
Ship Revit tools to your whole firm without losing control.
- Revit 2019 – 2027
- Full deployment governance
Yugmir Kinetic for AutoCAD Available
One toolset across the whole AutoCAD family.
- AutoCAD-based products
Yugmir Kinetic for ETABS Available
Structural modelling, automated.
- ETABS
What each product includes
The deployment core is shared. The full governance suite ships on Revit today — so this table tells you exactly where each capability stands rather than implying parity that doesn’t exist yet.
| Capability | Revit | AutoCAD | ETABS |
|---|---|---|---|
| Folder-driven ribbon — publish a tool by copying a folder | Yes | Yes | Yes |
| Update without reinstalling or restarting the host | Yes | Yes | Yes |
| Central toolset on your own network drive | Yes | Yes | Yes |
| Staged rollout to a Beta channel | Yes | — | — |
| One-action rollback to a previous release | Yes | — | — |
| Crash isolation and automatic quarantine | Yes | — | — |
| Role-based access, including AD groups | Yes | — | — |
| Remote kill switch (signed) | Yes | — | — |
| Hash-chained audit trail | Yes | — | — |
| Two-person approval before release | Yes | — | — |
| Fleet and ROI reporting | Yes | — | — |
Evaluating governance specifically? The governance page covers each control in detail, including which ones need code signing before they become active.
Built for how firms actually work
No restart. No reinstall. No ticket.
Users press Sync and the ribbon rebuilds in place, mid-session. Files in use at that moment apply on the next start rather than failing.
Works when the network doesn’t
Licensing is offline-first: one online activation, then a sealed local record and a grace window. A dropped VPN doesn’t lock anyone out.
Nothing leaves your network
Tools and usage data live on your own file server. The only outbound call is licence activation, which carries no project information.
Try it on one project team
Fifteen days, full product, no card. Publish a tool, roll it back, and see the audit entry — that’s the whole pitch in about ten minutes.