A private package server would work well for us, in conjunction with the public one. We have our own private Nuget Server for distributing our internal company libraries, and we use the public one for everything public. It would make sense for Rhino to behave the same. essentially we’d like for each of our GH add-in to publish to our local server through our CI/CD pipelines. The folder solution is probably going to work for us, but it doesn’t solve the distribution problem.