Kryon RPA Overview

Kryon RPA is the #3 ranked solution in our list of best RPA tools. It is most often compared to UiPath: Kryon RPA vs UiPath

What is Kryon RPA?

The Kryon RPA Platform sets the standard for secure, scalable and cost efficient robotic process automation management and optimization. It’s also among the most business-user friendly platforms on the market.

Kryon RPA is also known as The Leo Platform.

Kryon RPA Buyer's Guide

Download the Kryon RPA Buyer's Guide including reviews and more. Updated: June 2021

Kryon RPA Customers

HPE

Kryon RPA Video

Pricing Advice

What users are saying about Kryon RPA pricing:
  • "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."
  • "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've more than broken even over on the license. Year to date, we are at $120,000 in savings."
  • "Licensing costs are about $100,000 a year without any additional costs."
  • "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."
  • "We have a yearly license. It's about $5,000 per year."

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Adam Staude
Manager, Application Support at a consumer goods company with 1,001-5,000 employees
Real User
The tool helps with speed to market, efficiency, and accuracy

What is our primary use case?

We use it to automate a lot of data entry or do manipulation in regards to our ERP system. We are still pretty new with the solution. We have maybe a dozen wizards right now. Some of them are different variants of similar wizards. For the most part, it is used all around our ERP system. E.g., if we have a new product that we're going to make, we take the information from marketing and engineering. That gets handed off to the bot, then the bot enters that information into our ERP. This is a pretty intensive manual entry process. Everything that we use is on-premise.

Pros and Cons

  • "The bot is typically about twice as fast as a person and more accurate, as long as the data going in is good. That is the biggest advantage."
  • "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."

What other advice do I have?

I would really recommend the tool. I definitely see a lot of value with it. Just in the few release notes that I have read for some of the versions they've released since we installed it, it sounds like they are still adding a lot of features and functionality. We are very excited to get this upgrade under our belts and see what new things the new version brings to the table. It has been a great value-add for us personally and easy to use. We are happy with what we bought. No buyer's remorse here. The biggest challenge that we have had isn't even with the tool. It is with the business funding…
JM
Senior Systems Analyst RPA at a hospitality company with 10,001+ employees
Real User
Allowed us to be more responsive and competitive with less human involvement

What is our primary use case?

We use it for unattended automation and attended automation. We are working on automating a lot of the support processes that we do within our call centers which are very repetitive. In addition, there are rates and pricing in another area where we have introduced automation. We have some automated processes running multiple times a day to evaluate rates, provide reporting, and perform rate updates, as needed, without human intervention. We are also looking at streamlining some areas on our franchise side, where we are building properties out in our systems and updating their property… more »

Pros and Cons

  • "Attended automation has diverted 34 percent of training calls to our tech support centers."
  • "We have been using Kryon Process Discovery for about a year now. With our initial tests and monitoring just a couple people, we were able to identify 79 possible use cases within a one-month period."
  • "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."
  • "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."

What other advice do I have?

Take your time. Don't rush it. Ensure that you have a few good use case scenarios to start working with, because if you don't have something to work on right out of the gate, the system will just be sitting there doing nothing as part of the evaluation. You should know a handful of processes which are good candidates that you can use as initial proofs of concept just to make sure that it will fit your needs. You want more than one, so if you do move ahead, you actually have some work to do. Kryon is easy to use. Somebody who is not tech savvy at all might have a bit of trouble picking things…
Learn what your peers think about Kryon RPA. Get advice and tips from experienced pros sharing their opinions. Updated: June 2021.
511,773 professionals have used our research since 2012.
LP
Business Analyst at a financial services firm with 1,001-5,000 employees
Real User
Helps us find and prioritize processes that are ripe for automation, while .NET plugins make it scalable

What is our primary use case?

We only use unattended bots right now. We build processes to help business departments in our company to improve processes through automation of pretty easily "bot-able" ideas.

Pros and Cons

  • "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."
  • "At first, we had problems with the object detection but in this latest release it has been better, and I think it keeps getting better."

What other advice do I have?

The biggest lesson we've learned through our time using it is the .NET component for scaling. One of our biggest lessons is to use that wherever possible because it makes things so much quicker. Also, if you look at some of our old bots that we built versus some of the bots we build today, it's crazy that we even knew what we were doing. The process flows and understanding what can and can't be bot-able, have gotten way better. My advice would be to have a team. Make sure there's a developer so you can do plug-in things and make sure that you understand the setup and the admin tool. That was a…
BD
IT Consultant & Robotics Business Analyst at a insurance company with 201-500 employees
Consultant
Very user-friendly for developers and we've seen increased operational efficiency

What is our primary use case?

As a company in the insurance industry, we use it for various functions within finance, such as identifying duplicate invoices, reporting, some operations functions - moving information from one system to another - as well as claims-processing.

Pros and Cons

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

    What other advice do I have?

    You do need someone with some development knowledge. Not necessarily everybody involved has to know development, but as a resource, it would definitely be important to have. A straight business-user who isn't strong in IT or development wouldn't be able to do half the things that we've done. Having someone with a development background, at the very least as a support person, internally, is tremendously valuable. As for saving time when launching new automations, we don't have anything to compare with because we didn't have an automation solution beforehand. It's new to the company. I would say…
    MA
    RPA Developer at a tech services company with 10,001+ employees
    Real User
    It is very easy to learn and implement, but the products has limitations due to its lack of interoperability with Citrix

    What is our primary use case?

    We manage customer accounts: their orders, modifications, account cancellations, and back office stuff. For example, our clients are network marketing teams. Therefore, they will have accounts for multi-level marketing (MLM). They want their orders and accounts modified. For some of them, we want to change their subscriptions or cancel their accounts. These are all submitted as requests through online forms. Then, we will take them and do the modifications. We do this process automatically through Kryon. All our bots are actually licensed for unintended, but we are not able to use them. So, we… more »

    Pros and Cons

    • "It has been helpful in reducing the manpower and error rate since we are able to run tasks 24/7 without interruptions. As humans definitely take breaks and there may be absenteeism that is unexpected, the solution provides continuous work. Humans tend to make errors once in a while, but the solution has almost zero percent errors."
    • "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."
    • "Another major drawback is OCR. We are not able to read scanned documents correctly in a reliable way. There is always some margin of error. Some of the processes require us to read scanned documents, and you need to ensure that it is 100 percent accurate. Without that level of assurance, you can't automate such tasks."

    What other advice do I have?

    It is a good solution if you're not using any virtual machines, like Citrix. It would be better if you get a demo or automate a simple task using Kryon. Get them to show you a proof of concept so you can understand what other challenges that you will have rather than blindly implementing it. Definitely, get a demo to see how efficient it is. Seeing it in action helps a lot. We are not completely moving to a digital transformation. Even our management doesn't agree with 100 percent digitized solutions. They still want some level of human involvement, as well as for auditing. The humans in our…
    Justin Kruse
    Operations Consultant at LTCG
    Consultant
    Process Discovery gives us a framework and outline on how to make automation work from end-to-end

    What is our primary use case?

    We use it for rapid process automation, but we also have Process Discovery. We use it for billing and collections, business administration, and insurance.

    Pros and Cons

    • "We use PowerBuilder as our application building codex. Kryon adds flexibility when we have the functionality of SQL, where we can take sets of data out of the back-end and run complex computations or do a bunch of data validations inside the wizard. It can save us sometimes dozens of steps, then if we were to try and do those same reviews using the user interface completely. The balance that we get from using Kryon RPA, alongside being able to screen scrape and frequent screen, gives us an advantage that we haven't had previously with any of our other attempts at robotic process automation."
    • "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."

    What other advice do I have?

    Understand that you need to have a very well-documented framework of what you plan to automate. Not necessarily the idea of, "I want to automate this task." But, as a company, don't be narrow-minded to believe that these are the only tasks that we can automate. You'll find that there are a lot of groups which are doing things that you may not know of that you can automate very quickly. Be very open-minded when you start working with the solution, because you'll find that a lot more doors are open than you originally anticipated. As with anything in software suites, you are always going to have…
    Yaniv Straus
    Delivery Manager at Delek
    Real User
    Saves us significantly in man-hours and helps reduce human error

    What is our primary use case?

    We mainly use it for creating automated processes from previously manual processes, to make existing processes faster, better quality and more efficient. We currently have three processes implemented in production and the fourth is going live next week. It's not heavily used, so far. The first one is small. It just enters the US dollar currency into our ERP system. It's a daily task each morning. The second one involves an external, third-party systems from which we export a report and import it into one of our systems. It used to be done on a daily basis by an employee and now it's being done… more »

    Pros and Cons

    • "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."
    • "It would be better to have [upgrades] done automatically, like an application on your smartphone. Or even if done manually, the upgrade should just be "next, next, next," and it's upgraded, rather than making it a project to upgrade."

    What other advice do I have?

    Take the training course. At least the person who is going to program the robots has to have some background in information systems in general and in more specific, operation systems, in programming and in Office, of course. He has to have a technical orientation, database knowledge would help him, as well as system analysis capabilities. In terms of ease of use for business users, the only users are me and 2 other persons in the information systems department. Currently, we have only unattended implementations and no attended implementations which would require a user in the organization to…
    Michal Sagi Shamir
    Manager of Organization, Methods and Knowledge Management at Max by Leumi
    Real User
    Helps reduce employee errors and enables us to decrease monitoring of employees

    What is our primary use case?

    Our primary use case is two back-office processes from a specific area, an area which was very complicated. In the credit card world, there is a process called a chargeback, when the customer says he didn't do a specific transaction, or it's not the right amount. This process has a very long, complicated and regulated process behind the scenes, after the conversation with the customer. We used a robot to automate a lot of the process, to make it shorter, easier, and to save a lot of agents working on the process. Every week or two weeks we are bringing on a new process with the robot. We are… more »

    Pros and Cons

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

    What other advice do I have?

    We have a lot of people coming to us to learn from our process, so we've been providing advice already. First of all, it's important to do a very smart business analysis, from the business side, and not automate exactly the way it was done before. Really think about ways you can improve and make the business logic, the business rules behind the scenes, more effective. This is very important. It's also important to look at becoming independent with the solution from the beginning. We have only started to plan for that now. The authorization issues within our company also took a lot of time, so…
    See 10 more Kryon RPA Reviews
    Buyer's Guide
    Download our free Kryon RPA Report and get advice and tips from experienced pros sharing their opinions.