What do you like best about the product?

The ability to use Nuxeo as an OpenSource platform is appealing. But the kicker is Nuxeo Studio, the proprietary configuration engine.

Much of what may get customized in Nuxeo can be done "headless" via the APIs and this is how I have approached its use to date. While there are some use cases where access to documents and/or content via Nuxeo's Web UI would be valuable, our user-base is best served by knowing as little as necessary to do their jobs. This means transparent API driven approaches using the existing UI they already work within.

What do you dislike about the product?

While Nuxeo remains a flexible and powerful platform from which we can manage a wide variety of electronic content, and its future is bright, the one drawback I have noted is that the process of custom development takes some getting used to. Native libraries for frameworks such as the Spring family of frameworks would go a long way to simplifying integration work.

What problems is the product solving and how is that benefiting you?

We're using Nuxeo to store a wide variety of communications documents for various types of correspondence such as Fax, Mail and Email. This is integrated to multiple systems of record and CRM platforms depending upon business unit.

Compared to our previous implementations based on Microsoft SharePoint, Nuxeo is much more performant and flexible.

Recommendations to others considering the product:

Nuxeo has a decent stand-up time. Its architecture is significantly more extensible and friendly from an integration standpoint than others we reviewed in our selection process.

While Nuxeo's underlying platform is Open Source Software (OSS), and also built on predominantly OSS components allowing it to be used at minimal cost … we found that the Nuxeo Studio configuration engine rather significantly enhances the deliverability of Nuxeo based solutions. So much so that it's well worth the annual license costs, at least in this stage of our implementation cycle.