NTT-AT WinActor vs Nintex RPA comparison

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

"All our users have no technical background. But Kryon is really simple and intuitive. Our business adapted very quickly and easily. This is the main thing and it's why we love the system so much. It's why we are always trying to put more processes into the system and make more use cases: because of the simplicity and the intuitive nature of the system."

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

"I like Kryon RPA's ability to use automated and manual processes with any bot."

"What I like most about Kryon RPA is the user experience. I also find the layout and design of the solution better for programming compared to other RPA solutions."

"Nintex RPA doesn't require much coding, and you can drag and drop the activities."

"While we have only explored the simple use cases so far, Nintex RPA has good integration capabilities, such as working well with Gmail and Outlook to automate document handling and notifications."

"The number of commands it gives us to edit and modify is really good. It also captures screen activities and plays them back."

"This software is very smart - it can decide from a picture if we like that condition, and then the robot will do that action."

"The tool's most valuable feature is data import. The OCR feature helps to recognize the data. It can recognize screen and document numbers well."

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

"Nintex RPA is not suitable for PDF automation."

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

"Further simplifying the low-code development process can attract a broader user base by making automation accessible to those with minimal technical skills."

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

"There could be some features to fix compatibility issues with firmware."

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

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

"Something that could be improved is that this solution can't run when the computer is locked, which meant we had to implement it in our own on-prem server as it never auto-locks."

"The OCR has issues recognizing handwritten data."

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

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

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

"We have a yearly license. It's about $5,000 per year."

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

"We're paying in the neighborhood of about $66,000 a year. The cost is fairly similar to its competitors' costs. It might have been a little bit more reasonable than the others, and that cost was with Process Discovery in addition."

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

"They license per robot and we have 25 robots. You get so many robot licenses and can allocate those licenses to either attended, unintended, or Process Discovery bots. If you have 25 licenses, for example, you could have 20 automation bots and five process discovery. This allocation is flexible. There are also maintenance costs."

"We pay yearly for the agent who runs the processes, plus an additional fee for maintenance costs."