Kryon RPA Reviews

We use it to automate some processes that require no human intervention. Currently, we have three projects: dispute resolution, settlement reconciliation, and consolidation.

I find it very easy to use and customize. The bot can be configured dynamically to use dynamic values, and we can use attended bots to interact with the flow of the bot. Also, it's very seamless to interact with Excel files and web app pages. So far, we have not encountered any issues while building using the action blocks.

We have also used its functionality to call REST services and SOAP services, and we can make use of JavaScript or Python scripts. There are a lot of functionalities that we can leverage.

Areas, where I see some room for improvement would be the use of reading details from an Excel file. Most of the time, it's difficult when I say looping through a huge data set, and it's very difficult for the bot to interact with those data sets unless it starts offering the Excel file. As of today, from the reports I've worked with, I noticed that most reports are empty columns and two rows. So if Kryon can associate with that and extract those deposits into a variable, and the tools can easily fit out to column dash and two rows and columns, it will be nice. But as of today, the bot doesn't have the functionality to detect variables. We have to do it on the Excel file itself.

I also noticed that when it comes to the use of bots, not everyone has the same knowledge, and it can be difficult to do certain research unless you have advanced knowledge of what you need to do. I also noticed that in the community, most people don't use it, and it's quite difficult when you need certain support.

We started using it about a year ago, in 2022. The version we use is 22.3.1.

Based on how we use it, it has no breakdowns. It's very stable. I mean, it's been months since we encountered any breakdowns.

Everyone has access to it, so around ten people are using Kryon RPA in our organization.

We have contacted the customer service and support team before. We were facing some issues with the console, which is the administration page where we see expenses, expanded entries, bots, and successfully run lines. At some point, we were unable to connect to the page, so we had to contact the support team. They came in and resolved the issue.

The support was good, but our relationship with Kryon's support team is very good. So I would rate it as good.

Positive

I have in-depth knowledge of Kryon RPA and other similar tools. I have used Ui Path and Blue Prism in the past, and I find Kryon to be similar and easy to use.

I have a good understanding of all the action blocks and how to use them, which makes it easy for me to set up and use Kryon.

I would say the installation is not complex. When we did our own installation for a vendor due to some permissions and restrictions, it took us around two to three days. But normally, if we don't have those issues, I can say the installation is quick and straightforward. It didn't even take me a full day to install and set up the solution.

The price is affordable. The license is based on the number of bots and users.

We had some back and forth using the setting tools of the RPA solution and noticed that other RPAs were costly. We found that Kryon RPA was cost-effective and had features other apps didn't have.

I would give Kryon RPA an eight. As a developer, I find it easy to use. The codes are written in a language that is understandable. They also have documentation available on their website that explains how the tools work. The way the tools are built is simple to understand. The steps can be split into different parts, and there can be more than one step for a particular bot. The fundamental aspects of the process build are easy to understand. Additionally, the build has current and account notes explaining what each step does. 

Overall, Kryon RPA is easy to understand, which is why I gave it an eight. I would definitely recommend using the solution. 

I have been using it for a few clients and office stations, including banking, insurance, and a major internet provider. 

The most valuable features of Kryon RPA include exceptional in-build management, simple transcription management, and deployment features. 

The user-friendly environment allows for easy learning, and the end-to-end workflow management is excellent. Additionally, the maintenance and management costs are comparatively low in terms of licenses, and the adaptability is also noteworthy. Overall, they have developed good features.

There are a few areas that can be improved. Firstly, Kryon RPA needs to enhance the robustness of its multi-board architecture to ensure the availability of bots on multiple machines. 

Secondly, Kryon RPA should focus on improving document extraction. When compared to other integrated products, such as those offered by its competitors, its document extraction capabilities need more attention. 

Additionally, Kryon RPA should work on enhancing the allocation response for multiple bots to maximize their utilization.

These are the key aspects that require improvement, along with the inclusion of a high availability feature. While I hope the data is stored in the cloud, I'm not entirely certain. However, it's crucial to ensure seamless integration with third-party vendors to enhance the usage of the product console.

The security aspect of Kryon RPA is good, which is why several banking and financial institutions are using it. As for stability, it ultimately depends on meeting the expectations of the individual customers.

I would rate the scalability a seven out of ten.

The support provided by Kryon, along with the learning academy and online forums, has been quite responsive.

The initial setup of Kryon RPA can be considered moderate. It is neither overly complex nor extremely easy. However, the configuration deployment and client version setup are relatively more user-friendly compared to other products.

Initially, the deployment was mostly on-premises as we explored the project's capabilities and conducted proofs of concept (POCs). This was during a period when the organization was also using AWS and Azure. However, gradually, we migrated to the cloud to leverage the product's features and capabilities. Initially, on-premises deployment was necessary for testing purposes. Now, the implementation and deployment process has been simplified, and we primarily use cloud apps.

The initial setup itself only took a few days. However, the duration of implementation and deployment depends on the complexity of the project or process being automated. Once the implementation is completed, the migration to the production environment is usually quick, taking only a few hours or days, but in some cases, it can take a few weeks.

The implementation timeframe varies based on the complexity of the specific use case we are working on.

The pricing is moderate compared to other products, and I would consider it to be economical.

The licensing features are very good, including the option for shareable licenses. The overall cost is moderate and economical.

Overall, I would rate the solution a seven out of ten. 

Kryon RPA is used in different departments such as Human Resources, Programming, Planning, Production, Commercial, etc. I use it when I program tasks for clients, in particular, to program the bots in client environments.

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.

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.

My experience with Kryon RPA is two years.

Kryon RPA is a stable solution, but its stability depends on the version installed in your environment. The most recent version of the solution isn't as stable and has a lot of problems that even the support team isn't able to solve. It's better to use an old version of Kryon RPA that's more stable than the newer versions.

Kryon RPA is not scalable. Other RPA software has more scalability.

On a scale of one to ten, where one is bad and ten is good, my rating for Kryon RPA support is four. The response time from the support team and the time it takes to solve problems need to be faster.

Neutral

The initial setup for Kryon RPA is very easy, and if you compare it with other RPA software, it's easier.

I saw ROI from Kryon RPA, but I don't have the exact values, and that would be confidential. If I were to rate ROI on a scale of one to ten, I would give it a seven.

I have experience with Kryon RPA for many versions, such as 19.3, 20, and 21. I'm a developer who provides services to clients, so I develop and create tasks in Kryon RPA for clients.

Two professionals take care of the deployment and maintenance of Kryon RPA. One specialist deploys it, and the other person is in charge of the IT infrastructure.

My advice to others looking into implementing Kryon RPA is to deploy in small blocks that can be reused in many jobs or many other tasks.

My rating for Kryon RPA is six out of ten.

I use Kryon RPA to make bots for the telecommunication and banking industries. 

I like Kryon RPA's ability to use automated and manual processes with any bot.

Kryon RPA's integration with other solutions could  be more seamless. 

I've been using Kryon RPA since 2019. I started at my previous company about four years ago, then I took another position at Banco Pichincha Ecuador. I'm a development architect working as an independent consultant at the bank. 

Kryon RPA is scalable. It's easy to create bots and schedule when they should run.

Kryon RPA's interface isn't as developer-friendly as UiPath's. I'd also like to see more seamless integration with other solutions. For example, with UiPath, we can use a lot of APIs. I also like Orchestrator from UiPath. We can control all of the robots that we're developing in the machines in the bot runners. UiPath Apps is a new tool that I like.

Microsoft also has some amazing tools, like Power Automate Desktop, Power Apps, and Power Automate Online. These tools can integrate with bots on Power Automate Desktop.

I Kryon RAP 10 out of 10. I recommend starting with easy processes. You should discuss the processes with the client, and go over things like cost, tools, time, and other things that are critical for the business.

I primarily use Kryon RPA for attended and unattended bots and back-office automation. I've also used it for fulfillment cases in the retail domain, where it's been working quite well.

Kryon could be easier to use, especially in comparison to UiPath.

I've been using Kryon RPA for five years.

Kryon RPA is very stable - we've not had many disruptions, and the product is updated regularly.

The scalability's good, and it's flexible in terms of how you want to scale it up.

We've received good support from Kryon.

The initial setup is straightforward, without any issues.

Kryon is slightly more expensive compared to UiPath.

We evaluated Automation Anywhere and Blue Prism and found Kryon to be more approachable.

I would recommend Kryon to those thinking of installing it and would give it a score of nine out of ten.