Inflectra Rapise vs Nintex RPA comparison

"We always use the product for end-to-end automation test cases."

"The most valuable feature of the solution is its versatility."

"It's pretty straightforward to set up."

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

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

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

"The initial setup process is easy."

"The recording capability is valuable because of the amount of data it captures automatically. It's quite good. It means less development, and fewer configuration settings to fill in after you're done."

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

"Inflectra Rapise needs to expand its ability."

"It would be good if there could be more integration of Inflectra Rapise, since not all customers use the same tool for test management and automation integration."

"The maintenance is very difficult. We've only been using the platform for three months, so I'm not sure if that will continue, but right now it's an observation I've had."

"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 need better training and community support in Indonesia."

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

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

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

"With the customer support, there have been some times where we have had to go through explaining the issue a couple times because it has gone through a couple of people's hands. There have been a couple of scenarios where we have had to re-explain the issue and bring somebody new up to speed on what is going on or what the problem is."

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

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

"I rate the product's price an eight on a scale of one to ten, where ten means very good pricing."

"We pay no more than $50 annually for support of each one of the licenses."

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

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

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

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

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