Datamatics TruBot vs Nintex RPA comparison

"The solution is inexpensive compared to many other solutions in the market."

"The product's initial setup phase is straightforward and easy to use."

"Ability to calculate the ROI on the jobs that are running."

"The initial setup process is easy."

"Troubleshooting and debugging could be improved. It's missing a proper debugger. It's very difficult, based on the log files and the fact that it doesn't have a proper debugger, to troubleshoot issues. It will sometimes end with no indication as to why it ended and it becomes a bit of trial and error."

"We took a very complex business area, and every activity in it which can be done automatically is being replaced by the robot instead of people working on it."

"It's very seamless to interact with Excel files and web app pages."

"The most valuable features for our organization are the automatic processes which save main power in the back office."

"Once I decide a process is suitable as a Kryon solution, the cycle of automation is quite quick. I learn about the manual process and I'm one of the two guys who program the Kryon environment. It's relatively simple. There are many details, but once you understand the concept it is quite easy."

"Nintex RPA often includes security features, including encryption and user access controls, which ensure the protection of sensitive data and compliance with security standards."

"It has been helpful in reducing the manpower and error rate since we are able to run tasks 24/7 without interruptions. As humans definitely take breaks and there may be absenteeism that is unexpected, the solution provides continuous work. Humans tend to make errors once in a while, but the solution has almost zero percent errors."

"There is a learning curve, and some training could be included to bring users up to speed."

"The stability of the product has certain shortcomings, making it an area where improvements are required."

"Would like to see more additions to the library."

"I have seen some very minor occurrences where Kryon's interactions with Microsoft Office might cause the robot to hang. However, it is about one to two percent of the time where we are seeing this happen. It is such a small percentage that it's not even something that we are overly worried about. This would be where they might have some stability issues, but it could be the Microsoft Office API or how they are interacting together."

"Another major drawback is OCR. We are not able to read scanned documents correctly in a reliable way. There is always some margin of error. Some of the processes require us to read scanned documents, and you need to ensure that it is 100 percent accurate. Without that level of assurance, you can't automate such tasks."

"What needs improvement in Kryon RPA is the support. Sometimes, the solution has problems, so I contacted support, but I didn't receive immediate help from the team. You have to wait a while before the problem gets solved. This happens a few times in terms of getting cases solved. It would also be better if Kryon RPA had a cloud version because currently, from what I know, it only has an on-premise version, though I could be wrong about that. There isn't any additional feature I'd like added to Kryon RPA because it's a good service, but the support is very, very bad, so that area could be improved."

"Kryon could be easier to use, especially in comparison to UiPath."

"It would be better to have [upgrades] done automatically, like an application on your smartphone. Or even if done manually, the upgrade should just be "next, next, next," and it's upgraded, rather than making it a project to upgrade."

"I would like to see a better OCR solution. That's the main thing: identifying unstructured data, like all paper documents and data from pictures."

"We use Google Drive a lot. If somebody sends us a spreadsheet or a document, it's going to be in Google’s format. It's not going to be in Microsoft Office format. But currently, there's no integration with Google’s documents. That would be a huge plus to have."

"The only unstable part is Studio where you build this stuff. In our version, the 5.25. It has a memory leak. If you leave it open for too long, eventually it just freezes. Saving your work, closing, and opening it just once a day is all it takes. However, this is a bug that I have noticed about the stability of the actual tool."

"The tool is expensive."

"We've more than broken even over on the license. Year to date, we are at $120,000 in savings."

"It is very cheap. I would rate the pricing a three out of ten, with ten being expensive."

"Licensing costs are about $100,000 a year without any additional costs."

"Compared to its competitors, Kryon RPA's pricing is very competitive."

"Kryon is slightly more expensive compared to UiPath."

"Can't beat the price... There are different pricing levels for every bot or unattended bot. You can buy however many you want. You'll need an additional virtual machine for it to work on."

"The product has reasonable pricing."

"We have been able to alleviate two FTEs, which was a big savings for us. We were able to reuse those resources in other locations. It is over 5000 hours a year in total savings."