Guide for using speckle in backend only

Welcome back @grub

Thank you for sharing your thought process with us. Your intention to use Speckle to synchronise Revit data with a database is intriguing. From what I gather, you’re interested in leveraging Speckle’s existing capabilities for converting and serializing Revit data rather than building an entirely new custom connector. Am I right?

If you want to sync Revit data to a database, you might be able to use the existing Revit connector and process the data once it has been transported to the Speckle server. This way, you could work with the data outside Revit and still benefit from Speckle’s conversion and serialization capabilities.

This approach would bypass the need to handle the UI components outlined in the Speckle connector guide, presumably avoiding some of the complexities of developing a custom Revit plugin.

However, I want to ensure that this solution aligns with your objectives. Could you provide more detail on your project requirements? What kind of data are you trying to synchronize, and how do you plan to use this data once it’s in the database?

In case it helps get a clearer picture of what you want to do, I’d like to cross-reference this post by @henkon, who asked a similar question about plugins coexisting that both use the Speckle innards and some potential pitfalls to avoid, especially related to “DLL hell”.

I am looking forward to your response!