Rhino Sync

Multi-user collaboration for Rhino®.

Multi-user collaboration for Rhino®.

Lock, reload and sync Rhino® objects.

Supports geometry, blocks, layers, and attributes. Alpha release available now FREE to use without limits.

Compatible with Rhino 8.

Download from: www.mksdtech.com/sync

The server only temporarily stores a lightweight ledger of element IDs to support collaboration—never any geometry or design data.

This history is automatically deleted after 3 days of inactivity and is restored when collaboration resumes.

MKS DTECH has no access to geometry or user design data at any point, and we do not store any authentication tokens from users.

When testing Rhino Sync, certain plug-ins may cause issues such as crashes or missing methods. To troubleshoot, disable any unused plug

To work properly the following server has to be unblocked by any firewall or IT system:

https://sync.mksdtech.com/

To ensure the server is reachable, unblocking or whitelisting may be necessary. For assistance, contact your IT department.

To verify server access, visit: Sync Collaboration Hub, you should see

Connection ID required

Support for Rhino 7 has been temporarily dropped as of version 0.0.4.0. This is due to conflicts in assemblies loaded by other plugins, which the .NET Framework is unable to manage. Support may return in the future however it is unlikely due to api and technology limitations.

Why Rhino Sync?

Imagine you're working on a big project with a small team. Everyone is handling different parts of the same Rhino model, but instead of getting real-time updates, each person is stuck with their own copy of the files or split worksessions. When it's time to merge your work, you're hit with conflicting changes and wasted time.

This not only slows down the project—it creates unnecessary headaches.

For this reason, we created Rhino Sync:

• Real-Time Object-Level Collaboration: Work together on the same project with changes synchronized per object (geometry, blocks, layers, attributes), not via whole-file merges.

• Lock, Reload, and Sync Mechanism: Lock an object to prevent simultaneous edits, reload to instantly see updates from teammates, and sync to keep the central model current.

• Streamlined Workflow: Continuous integration of changes means no more time-consuming file merging and better traceability for each user’s contributions.

---

How it differs from Rhino Worksessions

Feature	Rhino Worksessions	Rhino Sync
Control Granularity	Manages whole model files, often requiring bulky merges.	Offers object-level control, letting you work on individual items (geometry, layers, etc.)
Conflict Management	Merging complete files can lead to editing conflicts.	Uses a lock/reload/sync mechanism to prevent simultaneous edits and avoid conflicts.
Team Coordination	Results in patchy updates that may need manual merging.	Provides real-time updates, ensuring that all changes are integrated seamlessly.

Rhino Worksessions remain great for many workflows!

Rhino Sync simply adds another level of collaboration with real-time, object-based coordination to help teams save time and avoid merging headaches.

Please send any comments or issues to [e-mail]