DeepL Translator vs Reltio Cloud comparison

"It makes our work faster and more efficient, freeing up time for more complex tasks. The basic translation is done by DeepL, allowing us to focus on other details. The main improvement is in speed and efficiency."

"There are default limitations and considerations. For instance, Reltio can store a maximum of 200 values for a single attribute. If your data exceeds this limit, you can request Reltio support to increase the limit. However, be aware that increasing this limit may impact performance, potentially slowing down data loading times."

"The survivorship feature is great because we can define it, prioritize the sources, and only allow those sources to survive when making the golden record."

"The solution saves 30% to 40% of our time."

"The matching feature of Reltio Cloud is highly effective compared to many other tools available. Additionally, it is almost ready to use out-of-the-box, reducing the implementation time."

"Its user interface is different from that of other MDM solutions like Informatica"

"We can store the data and enrich it from multiple sources."

"The most valuable feature of Reltio Cloud is the customization we can make in its functionality."

"The cloud feature is very beneficial, and the scalability performance feature is excellent."

"In future releases, I would like to see an option for saving previous translations. For example, other translators like Google Translate, save your past searches, and that might be something useful."

"The support team is slow to respond when we need assistance with workflow deployments. We must rely on their availability and contact them to receive the required JAR files."

"We need manual data modeling and configuration to tailor the platform to our requirements."

"Initially, the UI was limited in features."

"The download process can be quite slow"

"Reltio Cloud could be improved in two specific areas. Firstly, the API capability needs to be enhanced, as when utilizing the REST API and posting a significant amount of data, there are multiple rejections from the MDM side. This can be due to the MDM server not responding or being unable to process the request. Therefore, I suggest that the API capacity should be increased to handle larger amounts of data. Additionally, I have noticed that the response time from the servers can take up to a minute or a few seconds, which can be improved for a faster response time."

"The solution's UI could be enhanced, and its record filtering could be expanded."

"The deployment is difficult."

"There is some lag in developing new features for specific business requirements. If a new feature is needed, we have to raise a request in the developer portal through the IDEA portal. This process takes time to develop, which can be a drawback when immediate business needs arise."

"The solution offers a fair price. If you're a casual user, you might not want to pay for it, so it's good to have the free version. The free version is good enough for what a casual user would need. But definitely, the prices are fair for this tool."