Try our new research platform with insights from 80,000+ expert users

NTT-AT WinActor vs Nintex RPA comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 4, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Nintex RPA
Ranking in Robotic Process Automation (RPA)
23rd
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
30
Ranking in other categories
No ranking in other categories
NTT-AT WinActor
Ranking in Robotic Process Automation (RPA)
28th
Average Rating
7.0
Reviews Sentiment
6.6
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the Robotic Process Automation (RPA) category, the mindshare of Nintex RPA is 2.1%, up from 1.8% compared to the previous year. The mindshare of NTT-AT WinActor is 0.7%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Robotic Process Automation (RPA) Market Share Distribution
ProductMarket Share (%)
Nintex RPA2.1%
NTT-AT WinActor0.7%
Other97.2%
Robotic Process Automation (RPA)
 

Featured Reviews

JonathanNg - PeerSpot reviewer
Global Automation Lead - Customer Operations at a energy/utilities company with 10,001+ employees
Helped us identify areas where frontline staff aren't following standard procedures or using unexpected systems, giving us better insight into our end users' workflows
To analyze and make sense of the data generated by Kryon process discovery can be a lot of effort. It's not as automatic as some might think. It really depends on how many processes you have and how actively you use them. But the scalability aspect isn't necessarily about deployment or technical maintenance. It's really about how you analyze and gain insights from the data gathering. I'd rate the scalability a seven out of ten because the solution has been scaling well for a long time. It's very easy to deploy. But getting value out of it at scale can be a challenge, just like with any deployment. We use it mainly for process discovery. We actually proceed it from different teams. So, we have 15 licenses that we rotate with different people, actually through different teams. So, we do discovery for the online team; we gather the results after about two weeks to a month. We analyze those results, and then we deploy them again on the analytics team. We regularly deploy it to different teams. So, it's in constant use. It just runs on the systems through discovery mode most of the time.
reviewer1170825 - PeerSpot reviewer
IT Planning Assistant Manager at a manufacturing company with 10,001+ employees
Frees up employee time but can't run when computer system is locked
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. It would be better if, when we have scheduled a scenario, it would log into the system automatically.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The user-friendly environment allows for easy learning, and the end-to-end workflow management is excellent."
"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."
"As a business user, it's so easy to use. With the recording of the processes, we didn't need to hire a specific developer... we are able to build most of our processes without having to develop the actual development skillset... the simplicity is the biggest win."
"We are able to cope with our clients's demands. No matter how much volume they throw at us, we are able to get it done quickly."
"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."
"[One of the valuable features] is the triggers. It's relatively simple to activate it. You can activate it via Control-M or via email. It has a lot of built-in triggers which enable us to easily activate the jobs."
"Nintex RPA often includes security features, including encryption and user access controls, which ensure the protection of sensitive data and compliance with security standards."
"The task mining aspect has been the most valuable for us. That's why we actually bought it."
"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."
"This software is very smart - it can decide from a picture if we like that condition, and then the robot will do that action."
 

Cons

"Extracting meaningful data requires significant effort. You need a dedicated business analyst who can understand the output."
"When a project is very big, a lot of memory is taken up. Then, machines don't have enough memory. This could be improved upon to be more efficient."
"Kryon could be easier to use, especially in comparison to UiPath."
"The product requires some more time in development. It still has some bugs and some things to work out. They're constantly releasing. They need to continue working out the general issues of using the product at scale, first and foremost."
"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."
"We would like to see having a little more specific documentation, or some of the examples be easier to find. One of the big things that we get directed to now is the Kryon Community page, but a lot of that wasn't in existence or publicized when we started doing our training and education. Now, we're stumbling through using it. For the majority of the time, we have either had to try and interpret what the instructions meant or do a service desk ticket."
"We need stronger governance to know, when a transaction is done, whether it worked or failed; strong logging. That would be helpful."
"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."
"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."
 

Pricing and Cost Advice

"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."
"In addition to the standard licensing costs, there are manpower costs."
"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."
"The product has reasonable pricing."
"Compared to its competitors, Kryon RPA's pricing is very competitive."
"Kryon is slightly more expensive compared to UiPath."
"We've more than broken even over on the license. Year to date, we are at $120,000 in savings."
"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."
"We pay yearly for the agent who runs the processes, plus an additional fee for maintenance costs."
report
Use our free recommendation engine to learn which Robotic Process Automation (RPA) solutions are best for your needs.
881,665 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
9%
Real Estate/Law Firm
8%
Educational Organization
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise7
Large Enterprise18
No data available
 

Questions from the Community

Best RPA tools for IBM iSeries
We have found that Foxtrot (Now NintexRPA) is a very solid solution for IBM iSeries integration using the IBM ACS 5250 emulator, in addition Datamatics TruBot is an alternative solution.
What do you like most about Nintex RPA?
Nintex RPA often includes security features, including encryption and user access controls, which ensure the protection of sensitive data and compliance with security standards.
What is your experience regarding pricing and costs for Nintex RPA?
Although Nintex RPA is expensive, it is somewhat affordable considering its features. I would rate the cost aspect as an eight out of ten.
What do you like most about NTT-AT WinActor?
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.
What needs improvement with NTT-AT WinActor?
The OCR has issues recognizing handwritten data.
What advice do you have for others considering NTT-AT WinActor?
For the repeat tasks, we have two options. The first option is to use the scanner to set up the scheduler. Alternatively, we can use another method where we set up the task or schedule on the manag...
 

Also Known As

Kryon RPA
NTT WinActor, WinActor, NTT-AT Robotic Process Automation Software, NTT-AT RPA
 

Overview

 

Sample Customers

Amazon, Audi, Chevron, Toyota, Uber, Walmart
Exeo Tech Corporation
Find out what your peers are saying about NTT-AT WinActor vs. Nintex RPA and other solutions. Updated: December 2025.
881,665 professionals have used our research since 2012.