Coveo Relevance Cloud vs. Inbenta Enterprise Search

Coveo Relevance Cloud is a great solution to implement into Salesforce to provide Knowledge-Centered Support, Enhancements to a Customer Community, to provide sales aids, or to complement your customized app in Salesforce.

Incentivized

If you are looking for an enterprise search platform that offers an easy to use interface and if high performance is not really your priority, then I believe Inbenta Enterprise Search would fit your use case. For most other situations, I would recommend using a tried and tested search platform like Apache Solr.

Incentivized

• Coveo is fast, search results come up quick (though it's not always great).
• Not much complexity to run.
• Coveo is implemented within our portal and doesn't require extra steps to use it.

Incentivized

• Fairly easy to use interface.
• Quick to onboard new users, both in terms of access as well as training.
• The NLP-based semantic search feature is quite impressive.

Incentivized

• It would be great if Coveo 6 allowed you to rebuild indexes from a certain subtree instead of needing to rebuild the entire tree to see changes. This functionality was added in Coveo 7 and is very useful.
• In Coveo 6, integration with Sitecore is more difficult than one would expect. This integration is much improved in Coveo 7.
• I have seen cases where an exception thrown when crawling a specific document will cause the indexing to stop completely. I believe this only happens in implementations using custom faceting but it could be handled more efficiently if the trouble document was skipped and the indexing could continue.
• Relevancy ranking editor is good but not as powerful as GSA. GSA offers a self-learning scorer which automatically analyzes user behavior and the specific links that users click on for specific queries to fine tune relevance and scoring.
• We've ran into issues on multiple clients with Sitecore items being indexed multiple times in Sitecore 7 and Coveo 7. The fix Coveo suggested was to upgrade our Sitecore version and Coveo but unfortunately this didn't resolve our issue. After months of testing we were finally able to resolve this by implementing our own CoveoItemCrawler to get around the issue (based on https://developers.coveo.com/display/public/SC201404/Items+in+the+Same+Language+Gets+Indexed+Multiple+Times;jsessionid=3C1A2AE33540E0A0B8BB52BA3A64AF70).
• Integration with RabbitMQ in Coveo 7 seems error prone. We often see the error "The AMQP operation was interrupted" and on occasion, need to restart the Coveo service to get this operating again. In some extreme cases, we have also had to restart the server because of issues when attempting to restart the Coveo service.

Incentivized

• It is a fairly new tool in the market, so not much market feedback exists for this. This made us apprehensive in using it.
• The documentation and online forums are bare minimum.
• Quite buggy when working with multiple sources.

Incentivized

This question is not applicable to me

Incentivized

Apache Solr to Inbenta is like Java to Python. Apache Solr is powerful and handles complex search platforms well. Inbenta, on the other hand, is meant to be easy to use and does not lay too much emphasis on performance. If you are a small or medium business, Inbenta may suit your needs better. However, if you wish to manage a large and complex search platform, Solr is the way to go.

Incentivized

• Quick to find things in a massive database when needed.
• Results need to be more concise - sometimes we spend more time looking for the right file than if we were to just search amongst our own networks instead.
• Coveo is not always the most useful but does its job when general information is needed.

Incentivized

• Enabled our developers to quickly deploy changes to the search model.
• NLP-powered semantic search feedback provides good actionable insights.

Incentivized