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

Jiffy.ai Automate vs NICE Robotic Automation comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Jiffy.ai Automate
Ranking in Robotic Process Automation (RPA)
25th
Average Rating
8.2
Number of Reviews
8
Ranking in other categories
No ranking in other categories
NICE Robotic Automation
Ranking in Robotic Process Automation (RPA)
23rd
Average Rating
7.6
Number of Reviews
7
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2024, in the Robotic Process Automation (RPA) category, the mindshare of Jiffy.ai Automate is 0.4%, up from 0.3% compared to the previous year. The mindshare of NICE Robotic Automation is 0.6%, up from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Robotic Process Automation (RPA)
 

Featured Reviews

JG
Removes the burden of having to do some tasks manually
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. However, in the latest version release (4), they have full support for containerization. This has been a great improvement and one of the driving factors for switching from version 3 to version 4 very soon. The containerization capability will make a huge difference in our deployment process, because it doesn't create exceptions in the way we would deploy services. All the rest of the system is containers, so if you now have a product from a vendor that doesn't support containerization that means you must have a different process of deploying services, then accompany it with corresponding policies, because we have policies on how systems need to be configured to be reliable, secure, etc. Also, there are the BCDR aspects of it: the disaster recovery and business continuity. So, if you're introducing a new way of deploying services, now you need to have a BCDR plan dedicated to that as well, as opposed to deploying everything using a single model of deployment (mainly containers). Therefore, this will simplify a lot of things, in terms of DevOps.
Harish G V - PeerSpot reviewer
Quicker compared to other bots but not very user-friendly
There is a need for NICE to be more user-friendly. It should be designed in such a way that any developer can easily develop bots. For instance, Power Automate provides a good example of a user-friendly design that NICE can learn from. Moreover, in terms of documentation, there is very little available for NICE, making it challenging to implement the bots. So, documentation should be improved as well. There are a lot of additional features that could be included in NICE. As the NICE Robotic Automation claims, it is a low-code solution, but that is not entirely true. They need to concentrate on the prerequisites and building blocks. There should be more options available internally that are easy to use and well-developed.

Quotes from Members

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

Pros

"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."
"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."
"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."
"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."
"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."
"I found the invoice data extraction very exciting. It is really good."
"Provides good automation features."
"Through interfaces called Callout (created with HTML code) it is possible to create a strong interactivity with the user. These interfaces can be extremely dynamic in relation to the behavior of a local or remote robotic flow."
"NICE is one of the only vendors that does attended and unattended out-of-the-box. Using the unattended processes we've been able to build a "feature library." We break each process down into workable chunks that we can save into a big library. The next time we come to automate a task, we already have chunks of that automation built."
"It is easy to deploy. To do the automation in NICE, you really need to use your programming expertise. There are no inbuilt features in it, and you have to create all the required features, which can be very interesting for a programmer."
"The deployment of NICE Robotic Automation is easy."
"What we've done with the RTI client is that we've brought it into a bit more of a 21st-century feel. Our agents have the ability to move around when they want, click into stuff. They use it according to how their conversations go with the customer."
"It is a kind of desktop automation. Its licensing model is a little bit different. It tends to be individual automation specific to a role. It excels at that."
 

Cons

"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."
"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."
"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."
"The solution's support services need improvement."
"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."
"There is a need for NICE robotics to be more user-friendly."
"We haven't found it to be as powerful as some of the other platforms. From a true RPA perspective, it is pretty far behind some of the other solutions. It has emerged as a more desktop automation kind of tool, but it lacks a lot of enterprise features. It is not really a true RPA because of its licensing, which is kind of user-initiated. It would be nice it can be deployed at a more enterprise licensing model versus a user-based model. It didn't have autonomous automation so far, and they have just released this feature. They have kind of hodgepodged a bunch of products together to get there, but it is not as seamless as other solutions."
"[During the upgrade] any issues, where it couldn't remotely connect to upgrade, I needed the floor plan so I could go to that PC and have a look at it. Often it was either that the PC was switched off or had a bug or some other application needed to be reset."
"Its connectivity with other applications should be improved. In the version that I was using, it would just stop interacting with the other application. Its graphical interface should also be improved. It should have a user-friendly interface. Sometimes, people find it very difficult to understand. One of the obstacles that I faced while programming was that if I needed any kind of help, there wasn't much content on the internet. It can be very difficult to find a solution for a particular issue."
"There are a few areas for improvement in the installation phase"
"The solution is not as intuitive as it could be and integrating took a lot of time."
"The one thing I'd like to see, and NICE is already heavily investing in it, is improvement in the user interface itself. They call it the Designer and it's what the developers use. It is a bit clunky; that is the polite way to put it. I'd like to see it be a bit more user-friendly, a bit more intuitive, and to move to something a bit more web-based..."
 

Pricing and Cost Advice

"I like that it is very cost-efficient."
"The solution's price is reasonable."
"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."
"Its license is yearly. There are no additional costs to the standard fee. It is a standard license."
"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."
"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."
"As per my understanding, UiPath has a much lesser cost than NICE, but I am not sure."
report
Use our free recommendation engine to learn which Robotic Process Automation (RPA) solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
25%
Computer Software Company
11%
Transportation Company
10%
Healthcare Company
9%
Computer Software Company
20%
Financial Services Firm
15%
Educational Organization
7%
Energy/Utilities Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Jiffy.ai Automate?
Its initial setup process was quite efficient.
What is your experience regarding pricing and costs for Jiffy.ai Automate?
The solution's price is reasonable in terms of its performance. The licensing costs approximately $10,000 per year. There are no additional costs involved.
What needs improvement with Jiffy.ai Automate?
The solution's support services need improvement.
What do you like most about NICE Robotic Automation?
Through interfaces called Callout (created with HTML code) it is possible to create a strong interactivity with the user. These interfaces can be extremely dynamic in relation to the behavior of a ...
What is your experience regarding pricing and costs for NICE Robotic Automation?
In the configuration phase, you need to have a certain degree of knowledge of Windows and Linux environments. That said, the wizards and manuals are of good quality. For the price, I would say that...
What needs improvement with NICE Robotic Automation?
There is nothing so relevant to complain about except a few more options in the debug monitor (which is already very powerful and useful right now). There are a few areas for improvement in the ins...
 

Learn More

Video not available
 

Overview

 

Sample Customers

Southwest Airlines
HelpLine, Telefonica Spain, Banca Popolare Di Sondrio
Find out what your peers are saying about Jiffy.ai Automate vs. NICE Robotic Automation and other solutions. Updated: October 2024.
816,406 professionals have used our research since 2012.