Cory, Do you mean Gluu’s [support offerings](https://www.gluu.org/pricing/)? Or are you referring to functional support in the code?

Chris, I'm thinking my question is geared more toward the first. We're currently testing now for GLUU's functional support of lsyncd now, but were wanting to know if contractual/non-contractual(forum) support will diminish if we were to implement this software as opposed to csync2 (which is more of the default according to documentation)

Cory, Csync2 was the solution we have used in previous Gluu Server builds (2.4.4), so it was a natural fit with 3.1.*. That being said, there may be some difficulties with helping you with issues related to LSync replication, as we aren't familiar with the program. It shouldn't cause any major issues though. The files being replicated by csync2 are mildly dynamic. They usually don't change that often once configured.

Cory, Just to add to Chris' response... diverging from the documentation / listed components will definitely impact our ability to provide free community support. As you are probably aware of by now, a big part of our support strategy is to replicate reported issues to determine workarounds and fixes. It can be a time consuming process, so a paid support contract helps us allocate resources as needed to support more customized deployments. Feel free to [schedule a call](https://gluu.org/booking) if you'd like to discuss paid support options. Thanks for all your community contributions! Will