Datamatics TruBot vs Nintex RPA comparison

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

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

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

"We use Kryon Studio to develop new wizards and we use the features to capture elements from the screen and automate processes... The screen capture allows us to interface with systems which don't have an API, or where the API is very expensive, and it allows us to do on-screen integration."

"We use PowerBuilder as our application building codex. Kryon adds flexibility when we have the functionality of SQL, where we can take sets of data out of the back-end and run complex computations or do a bunch of data validations inside the wizard. It can save us sometimes dozens of steps, then if we were to try and do those same reviews using the user interface completely. The balance that we get from using Kryon RPA, alongside being able to screen scrape and frequent screen, gives us an advantage that we haven't had previously with any of our other attempts at robotic process automation."

"We have been using Kryon Process Discovery for about a year now. With our initial tests and monitoring just a couple people, we were able to identify 79 possible use cases within a one-month period."

"The thing that we find the most value in is the Process Discovery component and the ability to really see what users are doing on a day-to-day basis. We're starting to make sense of the processes that they're doing and getting visibility into what they're doing. Overall, the Process Discovery is very good."

"The full-service automation aspects and the process discovery are the most valuable features of Kryon RPA."

"The friendliness of the software is good because people without any technical background can start off on it. This solution makes it easy for us to use it, as there is no learning curve. With no learning curve, the development time turnaround decreases."

"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."

"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."

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

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

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

"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."

"It could be more reliable in spying HTML."

"Nintex RPA is not suitable for PDF automation."

"The process discovery tool of Kryon RPA could be improved because of its limitations."

"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."

"There are limitations on integrations with other platforms like ServiceNow. There are some issues integrating. It's not a really an open system. The product, its design, etc., is really good, but they have to look at the openness, how to integrate with other products which are available in the market, as well as with our own solutions. You can do integration but it is not so easy."

"What we are lacking is OCR, the ability to read text. We would like it to have the ability to take a page which is free text and analyze it, and then for the robot to know what to do next. This ability does not exist in Kryon products."

"At first, we had problems with the object detection but in this latest release it has been better, and I think it keeps getting better."

"The tool is expensive."

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

"We are probably saving $6000 to $8000 a month in labor costs. It's not a ton, but we're right around $60,000 to $80,000 a year with our current deployment."

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

"Kryon is slightly more expensive compared to UiPath."

"In addition to the standard licensing costs, there are manpower costs."

"The price is affordable."

"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."

"For an unattended robot it's $6000 a month."