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

Nintex RPA vs akaBot comparison

 

Comparison Buyer's Guide

Executive Summary

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

akaBot
Ranking in Robotic Process Automation (RPA)
18th
Average Rating
9.0
Reviews Sentiment
6.7
Number of Reviews
2
Ranking in other categories
Agentic Automation (9th)
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
 

Mindshare comparison

As of January 2026, in the Robotic Process Automation (RPA) category, the mindshare of akaBot is 0.3%, up from 0.1% compared to the previous year. The mindshare of Nintex RPA is 2.0%, up from 1.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Robotic Process Automation (RPA) Market Share Distribution
ProductMarket Share (%)
akaBot0.3%
Nintex RPA2.0%
Other97.7%
Robotic Process Automation (RPA)
 

Featured Reviews

Duy Lương Minh - PeerSpot reviewer
Senior Software Engineer at a university with 201-500 employees
User interface streamlines task automation and improves efficiency
akaBot made a noticeable difference at Wika because it is lightweight and easy to use, and moreover, akaBot has a forum to answer many questions. The ease of use stands out because the design of akaBot is very friendly. The best features that akaBot offers in my experience include the UI automation in the browser or in the Windows application. What I appreciate most about the UI automation in browsers or Windows applications is the auto-generate selector in a browser and Windows application. This feature makes a difference because it reduced most of the time developing the bot.
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.

Quotes from Members

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

Pros

"The cost is affordable, and it fits our requirements."
"akaBot made a noticeable difference at Wika because it is lightweight and easy to use, and moreover, akaBot has a forum to answer many questions."
"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."
"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 task mining aspect has been the most valuable for us. That's why we actually bought it."
"The advanced Excel functionalities are really convenient because we work a lot with spreadsheets. It’s also easy to use the HTML selectors. It’s just a click and it picks it up. There’s not a lot of no hard-coding with it."
"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."
"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."
"The most valuable features for our organization are the automatic processes which save main power in the back office."
"The number of commands it gives us to edit and modify is really good. It also captures screen activities and plays them back."
 

Cons

"I used UiPath before akaBot, and I think UiPath has more features than akaBot."
"If they can provide more intelligent automation, it would be beneficial."
"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."
"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."
"Kryon RPA need to enhance the robustness of our multi-board architecture to ensure the availability of bots on multiple machines."
"We have found some difficulties regarding the integration with legacy systems where the screen has elements in the Hebrew language. The connection to Hebrew, right-to-left systems, is more challenging."
"We need stronger governance to know, when a transaction is done, whether it worked or failed; strong logging. That would be helpful."
"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."
"I would expect that in the first year there is no ROI. It has to be measured over three or five years."
"It could be more reliable in spying HTML."
 

Pricing and Cost Advice

Information not available
"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."
"It is very cheap. I would rate the pricing a three out of ten, with ten being expensive."
"In addition to the standard licensing costs, there are manpower costs."
"We've more than broken even over on the license. Year to date, we are at $120,000 in savings."
"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."
"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."
report
Use our free recommendation engine to learn which Robotic Process Automation (RPA) solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
15%
Computer Software Company
11%
Real Estate/Law Firm
8%
Manufacturing Company
8%
 

Company Size

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

Questions from the Community

What is your experience regarding pricing and costs for akaBot?
The pricing is low and the setup process is very easy.
What needs improvement with akaBot?
akaBot should integrate more artificial intelligence in their product.
What is your primary use case for akaBot?
As an RPA developer, my main use case for akaBot is to automate repetitive tasks in many industries such as banking and manufacturing. I specifically use akaBot in Wika to automate repetitive tasks.
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.
 

Also Known As

No data available
Kryon RPA
 

Overview

 

Sample Customers

1. Aetna 2. Accenture 3. Adidas 4. AIG 5. Air France KLM  6. Allstate 7. Amazon 8. American Express 9. AmerisourceBergen 10. Aon 11. Apple 12. ATT 13. Autodesk 14. Bank of America 15. Barclays 16. Bayer 17. Berkshire Hathaway 18. Boeing 19. BNP Paribas 20. Citigroup 21. CocaCola 22. Comcast  23. ConocoPhillips   24. Cisco Systems  25. CocaCola  26. Dell 27. Disney
Amazon, Audi, Chevron, Toyota, Uber, Walmart
Find out what your peers are saying about Nintex RPA vs. akaBot and other solutions. Updated: December 2025.
881,082 professionals have used our research since 2012.