Jiffy.ai Automate vs Nintex RPA comparison

"I found the invoice data extraction very exciting. It is really good."

"The most valuable feature is the computer vision or OCR. That has a lot of use cases in real life. A lot of man hours can be saved, as we've seen in the finance processes... The feedback I have gotten from the team is that the OCR is quite powerful."

"It removes the burden of having to do some tasks manually. However, we are just using it in production for a single project. It saves us a lot of time in terms of extracting that information. So far, it has made a big impact."

"It is a one stop solution for automating process. The modular way that is assigned and works together follows a certain logic, and it encompasses a wide range of processes in a very structured and logical manner."

"The way Jiffy.ai integrates into existing infrastructure has been great for us. Our company is pretty stringent when it comes to cyber security and integrating with our apps... We've definitely had very strong scrutiny over this platform and this work, and even within that, it's been really successful at being able to integrate."

"The biggest driver was the cost savings. We wanted to improve productivity and save costs. Therefore, we gave most of the mundane tasks currently being done by a human to a bot. Some of the mundane tasks were reading invoices and keying in the data. We are talking about 15,000 documents every day. That is a huge volume that needs a lot of people. With the bot, it is just a fraction of the cost, because there is a huge savings in terms of manpower."

"Its initial setup process was quite efficient."

"With the customization option, we can write custom expressions using its compatibility with Python or other programming languages."

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

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

"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 most valuable features for our organization are the automatic processes which save main power in the back office."

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

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

"Attended automation has diverted 34 percent of training calls to our tech support centers."

"The recording feature enables us to record what we're doing, like typing or clicking the mouse, and to identify objects on the screen. We basically teach the program how to type, instead of a person. That's the most powerful feature."

"Initially, in version 3, Jiffy.ai did not have support for containerization. In our environment, we are heavy users of containers and container illustrators. So, the initial deployment option was running based on individual hosts that we deployed in the cloud. That created a singularity in the way that we deployed services in our system."

"When using UiPath automation, we could just Google issues if we were stuck with something. In the initial days with Jiffy.ai, we could not get that type of information from Google because there wasn't much of a community."

"The setup process could definitely be better."

"The solution's support services need improvement."

"The UI or the UX has room for improvement. The approach for designing the workflow is not that straightforward. It's quite difficult."

"They are still new in the market. Or, at least, they are still a small player. They require a lot of improvement in terms of learning material as well as the community developers. If you compare Jiffy.ai to an established solution, like UiPath, you can go to YouTube and find a lot of learning material posted by UiPath, partners, and other people in the community. However, for Jiffy.ai, you won't find that available in the market. Because of this it is very hard for us to find talent in the market. Most of the developers in the market are used to the bigger players. For Jiffy.ai, if you search a resume because you are trying to find someone who has used Jiffy.ai, you won't be able to find it. So, when we onboard a new person, we want them to learn this new system, but it is a bit hard for them to pick up because there are no external learning materials on the Internet."

"The solution has just not closed the gap of being accessible to non-IT users. If you are a non-IT person, then this all looks like gobbledygook. Maybe that is something that can be improved upon."

"I believe this is also being addressed, but a lot of the platform work, as we were putting in new versions or making some updates, was, ironically, very manual. It's improved greatly, but I would imagine that's an area that they're probably still working on, on the backend, to help when it comes to what we need to do for platform support."

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

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

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

"Kryon RPA need to enhance the robustness of our multi-board architecture to ensure the availability of bots on multiple machines."

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

"From our experience, the product is not suitable for end users."

"The solution's price is reasonable."

"The licensing is not expensive; it is quite cheap. The expensive part is to support and maintain it. Understandably, we engage them to do a lot of work that could have been done by our own staff, if we had an RPA team. I wouldn't hold that against them. It is just that the cost of support is on the higher side for us."

"I like that it is very cost-efficient."

"If cost is of concern, then start with Jiffy. If cost is not your main concern there are a few premium products out there, but they come with a huge price tag."

"Its license is yearly. There are no additional costs to the standard fee. It is a standard license."

"The pricing is quite competitive. As a small player in the market, they are quite aggressive in their pricing. With the features that they offer, it is quite worth the value."

"The pricing and license make sense. They have a model based on the concurrency of the workforce, which is very suitable in our case. The savings are great on the licensing cost."

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

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

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

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

"Kryon is slightly more expensive compared to UiPath."

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

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

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