Moving off BizRobo!: v11.5 and the Classic browser removal

BizRobo! is an RPA product that Open Inc. (renamed from RPA Technologies in June 2024) has offered since 2008. According to Open, it is a version of Kofax’s (now Tungsten Automation’s) RPA product adapted for Japan, and 3,000 companies had adopted it by December 2024. Robots are built in Design Studio, run on RoboServer, and managed in the Management Console; it has mostly been used to work web systems.

Staying on BizRobo! now comes with work to do. Upgrading to the latest version, v11.5, means moving to a new server. The product BizRobo! is built on has removed an old browser engine, and vulnerabilities were disclosed in 2025. This guide sets out what changed, with sources, how to tell which robots to keep in BizRobo! and which to move, and how to migrate.

Key points

• Upgrading to v11.5 means preparing a new server and a test environment and checking robots again. A fix pack also followed MySQL 8.0’s end of support (April 30, 2026)
• In Tungsten RPA, which BizRobo! is built on, the Classic browser was deprecated in 11.4.0 and removed in 2026.1. WebKit is meant to be kept only while the target site doesn’t change much
• With every robot due for some work anyway, now is the time to decide, robot by robot, what to keep and what to move

What changed in BizRobo! (as of October 2026)

v11.5 and the upgrade procedure

BizRobo! Basic, Lite, and mini moved to v11.5 on February 3, 2025. Robots can run on their own, and the Management Console can be reached through an HTTP tunnel, making operation and management simpler.

The official upgrade guide describes moving from v10.7 or later to v11.5 by moving to a new server environment. Overwriting the production server in place is not covered. Even without a new production server, a separate test machine is required. Management Console data moves through backups, and robots are checked in the test environment, fixed in Design Studio where needed, and then moved to production.

In January 2026, fix pack 11.5.0.7 shipped for BizRobo! Basic and Lite v11.5. It officially supports MySQL 8.4, following MySQL 8.0’s end of support on April 30, 2026.

Browser engines

BizRobo! robots work web pages through one of three browser engines: Classic, WebKit, or Chromium. In Tungsten RPA (formerly Kofax RPA), the product BizRobo! is built on, the two older engines changed like this:

• Classic: deprecated in 11.4.0, after which new robots could no longer be created with it. Removed in 2026.1: existing robots can no longer run in Design Studio, nor on RoboServer 2026.1 or later. To keep them running, they must be upgraded to the WebKit browser, after which decommissioned steps and data converters may need replacing or redesigning. Classic-browser robots show an orange icon
• WebKit: does not support the most current web standards and technologies, and is meant for static websites. New robots should be built with Chromium; robots built with WebKit can be kept as long as the target website does not change significantly

When BizRobo! will follow 2026.1 has not been announced. Robots built with the older engines will need upgrading or rebuilding at some point, and that is a good time to decide whether to move them.

The April 2025 vulnerabilities

On April 10, 2025, JVN (run by JPCERT/CC and IPA) disclosed three vulnerabilities in BizRobo!:

• In every version, credentials inside robot files are encrypted with a fixed key, so anyone who knows the key may be able to extract them
• In every version, a flaw in Design Studio’s license activation may allow arbitrary code to run on the Management Console
• In v11.1 and earlier, the import function uses an old library that may likewise allow arbitrary code to run. These versions are past their fix support period, and an upgrade is recommended

Open says the risk comes mainly from users inside the company with permissions, that managing user permissions lowers it substantially, and has published workarounds in its knowledge base.

Pricing

From the official price table and product comparison (as of October 2026). The Lite and Lite+ prices exclude tax; the Basic and mini prices are as shown in the comparison, which does not state how tax is treated.

Product	Annual base fee	Main terms
BizRobo! Lite	¥1.2 million	One concurrent robot, one Design Studio seat. ¥300,000 initial fee
BizRobo! Lite+	¥1.8 million	Two concurrent robots, three Design Studio seats. ¥300,000 initial fee
BizRobo! Basic	¥7.92 million	Server execution and concurrent runs. Separate initial fee
BizRobo! mini	¥900,000	Runs on a PC only; no concurrent runs

Which robots to keep in BizRobo!, and which to move

Robot	Recommendation	Why
Works an internal system with Chromium, whose screens rarely change, and runs reliably	Keep in BizRobo! and upgrade	Repeating fixed steps in volume on a server is RPA’s strength
Built with the Classic browser	Decide whether to move it when it has to be reworked	If it needs work anyway, moving it then costs less
Works an outside web system with WebKit, and its screens change without notice	Move to automation that recovers when screens change	WebKit is meant to be kept only while the site doesn’t change much
Only a Design Studio developer or the vendor’s partner can fix it	Move to automation business staff can fix in conversation	No waiting for whoever built it each time it stops
The other system offers an API or CSV exchange	Replace with the official integration	Sturdier, faster, and more reliable than working the screen
Needs judgment or a person’s check, such as reading invoices	Move to automation that combines AI with human approval	People judge, AI operates
Nobody knows who built it or what it does	Investigate and record it first, then decide	Moving it without the facts leaves gaps in the work

For how to investigate robots whose builders are gone, see Taking over an RPA bot whose builder has left.

How to migrate

1. Collect the robots and their run records: export robots, schedules, and run records and errors from the Management Console
2. Mark the robots that need rework: check in Design Studio whether each robot was built with Classic, WebKit, or Chromium, and whether it works desktop applications
3. Check where credentials are kept: list the robots that keep passwords inside the robot file
4. Order by how often they stop and what it costs: choose the order from failure counts, the impact on the work, and the effort to fix
5. Move it with the migration tool: it reads the robot and makes a workflow with the same steps. What to act on and what to wait for are written in words, marking where a person judges and checks
6. Prove it on one robot: run it on the same screens and data as production, and check run time, success rate, and how easily it recovers when it stops
7. Run side by side, then switch: run alongside BizRobo! through a busy period such as month-end, compare the results, then switch
8. Review licenses and servers: before preparing a server for v11.5 or renewing, fit the number of concurrent robots and the product to the robots you keep

RPA migration steps explains each step in detail.

How a robot’s parts move

In a BizRobo! robot	In the words of the work
Clicking or typing into an element found by a tag finder	Name the target by its label on the screen, as in “type into the invoice number field”
Waiting for a page to load or an element to appear	Write the condition, as in “check that the list is shown”
Looping over tags or Excel rows	Write “for each row of the list” and handle each row
Branching	Write the condition in words, and send hard calls to a person
Error handling	Resume from the step that failed, and notify the person in charge
The password store, or credentials in the robot file	Keep them as secrets, referred to by name in the steps; AI never receives the value
Schedules in the Management Console	Set them as the workflow’s schedule
Working desktop applications	As on the web, name the target by its label on the screen

BizRobo! and Kitewell compared

	BizRobo!	Kitewell
Who builds	Staff who can use Design Studio, or the vendor’s partners	Business staff, in conversation with the AI assistant, reviewing and applying each change
When a screen changes	Fix the robot in Design Studio	When the learned steps don’t work, AI rereads the screen, relearns the step, and repeats it from then on. The relearned step is recorded in the run log
Credentials	Kept in robot files or the password store	Kept as secrets; AI never receives the value
Judgment and approval	Handled by people outside the robot	People decide in approval steps, and when and how they decided is recorded
Where it runs	Servers (RoboServer) or PCs	macOS and Windows PCs, and servers or closed networks in your company
Updates	v11.5 means moving to a new server	Updated automatically
Price	Lite ¥1.2 million a year (one concurrent robot, excluding tax); Basic ¥7.92 million a year	On-premises ¥50,000 per computer a month (¥600,000 a year, excluding tax). One computer runs several workflows

BizRobo! and Tungsten RPA details come from official materials as of October 2026. Products change, so check each vendor’s official site for the latest.

Decide what to move before you upgrade

Before you upgrade BizRobo! or replace its server, Descarty assesses, at no cost, which robots to move and which to keep. We take your Management Console’s list of robots and schedules, their run records, and your current contract, decide for each robot whether to stop, keep, move, or replace it with an API, and compare three years of cost for upgrading to v11.5, rebuilding on Power Automate Desktop, and moving to Kitewell.

We also move one robot that often stops to Kitewell at no cost and show it running. How it works and what it costs are on “Moving off RPA.”

Sources

• Open: Business transfer from Tungsten Automation Japan (March 28, 2024), BizRobo! official site, BizRobo! Lite pricing
• Impress IT Leaders: BizRobo! series Ver11.5 released (February 2025)
• BizRobo!: BizRobo! Basic v11.5 upgrade guide, Fix pack 11.5.0.7 released (January 16, 2026)
• Tungsten Automation: Upgrade Basic Engine Robots (11.4.0), Upgrade Basic Engine Robots (2026.1), Types of browsers (11.5.0), About transition to CEF (2025.2)
• JVN: JVN#30641875 Multiple vulnerabilities in BizRobo! (April 10, 2025)
• Open: Vulnerabilities found in BizRobo! and countermeasures (April 11, 2025)