Kalido vs. Reltio Connected Data Platform

Suitability depends on your business model.

Incentivized

The data model is really flexible, so it should function well across many industries. Reltio Connected Data Platform tends to add new features first to its industrial vertical customers, though, so it may be especially well suited if your use case is specifically supported.

Incentivized

• Kalido has developed a data security and privacy manual for its personnel that is easy to understand and that provides direct guidance with respect to security requirements, including requirements related to support services to Kalido customers.
• Flexible master data modeling
• Kalido clearly establishes in its policy documents that Customer Database Information (CDI) is confidential information that must beprotected, and sets forth specific requirements for handling of CDI including encryption during electronic transmission and storage, as well as other controls.

Incentivized

• integration with SFDC, D&B
• Reltio API allows us to build interfaces with ease.
• The beauty of Reltio is Consolidation at any time we can review data at field level from different sources (crosswalk) and configure match merge and survivorship rules to define operational value and approved data can be redistributed to the upstream or downstream systems.
• With Central data governance, enrichment with D&B allows creating trusted data and distribute to various systems.

Incentivized

• Multiple rows, linked by pointers that makes data difficult to read. Could be structured in columns in a table.
• Kalido indicated in its survey response that it does not formally employ a standard configuration for its workstation builds, and/or it does not periodically review systems for deviations from the standard configuration. The Kalido DSP Manual indicates that Kalido does use a system security agent to maintain patches and anti-malware defense.

Incentivized

• UI does not support creating different profile views for an entity based upon customer types as example however we can achieve this by using sub entities ( sub classes). This feature is useful if we are creating profiles in reltio manually.
• Manual export every time we need to pick entities, fields etc does not allow to save templates. workaround is using postman creating predefined API with selected fields, filters and trigger export.
• UI does not support data masking which needed while we maintain PII information
• Potential Matches doesnt auto sort on confidence code so users need to manually select deselect relevant entities which is time consuming and painful process however this issue is when we have more than 4 entities as potential matches.
• It would be beneficial if UI displays data related errors (if any) between Reltio and SFDC.

Incentivized

Good Feedback

Incentivized

Love the UI

Incentivized

We felt Reltio had the best user experience, with flexible graph database technology and a customizable UI. Also important was the ability to look at historical snapshots to see relationships as they existed as of a previous date.

Incentivized

• unifying multiple sources of data = 10+
• Data quality on customer and vendors moved from 65% to 95%
• Reporting quality on operational, finance and sales improved from 70% to 95%

Incentivized