Resolve your doubts

The robots built in Rocketbot can be dynamically executed based on the process requirements.

  • Attended tool mode: from an icon on the desktop.
  • Hybrid waiting (trigger) for an event: keystroke combination, waiting for a file in a shared folder, email inbox, etc.
  • Unattended orchestrated by Rocketbot Orchestrator Center.
  • Unattended executed by cronJob or Windows Task Scheduler.

Configuration instructions are available in our documentation center

Rocketbot offers licenses that adapt to the needs of each company, both in terms of cost, number of robots to run, and “where”.

Each license is associated with a single machine, or “instance”, and is identified by a unique TOKEN. This allows for one developer per machine.

The Developer License allows you to create, test and debug a robot from within the development environment free of charge. The Production license allows you to run BOTs, and depending on the license used, they can be run sequentially or sequentially and in parallel, with capabilities of 2, 4, and up to 10 processes in parallel on the same machine. The number of processes to run depends on the physical architecture and the process. We have SAP cases of six instances running in parallel.

The licensing options and prices are available on our website

Rocketbot is compatible with all types of applications, whether they are desktop or web based.

  • Office 365
  • Google Drive
  • Microsoft Excel
  • Microsoft Word
  • Microsoft Powerpoint
  • Google Sheets
  • Google Docs
  • PDF
  • Microsoft
  • IBM
  • Oracle
  • SAP
  • Salesforce
  • AWS
  • Azure
  • Outlook
  • Gmail
  • Microsoft Exchange

Rocketbot runs on all major operating systems GNU/Linux (Ubuntu 18.04> Server Desktop o Docker), MS Windows (win7>, Server 2012>) and Mac OsX.

This enables a process to be automated and carried out by BOTs, whether on-premises or in public or private Clouds; and implement a fully hybrid BOT architecture or RPA solution.

Whatever your company needs, Rocketbot’s versatility adapts to your infrastructure: On-Premises, Cloud or Hybrid.

Rocketbot can run on any cloud that has a working desktop. The Cloud must be capable of launching a functional desktop.

Therefore, we can work with the major cloud providers in the market.

  • AWS WorkSpaces or Windows 10> Servers
  • Azure and MS Windows /Linux Ubuntu virtual servers.
  • If your server does not have an active desktop, you can use our Docker image, which includes a desktop and Rocketbot Play for immediate use.

Rocketbot requires an active desktop to work. Any service that provides an active desktop is compatible with Rocketbot.

Rocketbot has a Docker image ready to work.

It has the following features:

  • Linux ubuntu 18.04.
  • Desktop active xfce4.
  • No-VNC to connect via browser.
  • Remote desktop clients.
  • Firefox/Chrome browsers.
  • Rocketbot 0.4.9 >.
  • User and password protection.
  • External working folder for robot backup.
  • Based on OpenSource image.

You can access the Docker Rocketbotcl/rocketbot image at the following link

Rocketbot offers a wide variety of modules which allow it to connect with SQL and No-SQL databases available in the market.

  • MySQL
  • SQL Server
  • Oracle SQL
  • MongoDB
  • SQLite

Working with modules enables the straightforward and efficient addition of new database drivers.

You can access the connection modules on under the DataBase section.

Rocketbot offers a vast selection of modules for controlling the primary World Class office tools.

  • Google Docs
  • Google Spreadsheets
  • Google Drive
  • Google Gmail
  • MS Outlook 365
  • MS Office Word
  • MS Office Excel
  • MS Office PowerPoint

Modules for working with these tools can be found at under the Office or Google section.

Rocketbot offers encryption modules for storing information in the MS Windows credential system. Additionally, we provide encryption modules for both code in production and separate data.

  • AES in CBC mode with a 128-bit key for encryption; using PKCS7 padding.
  • HMAC using SHA256 for authentication.


Robots built in Rocketbot are encrypted during production, shielding their code as well as the variables involved.

All robots are encrypted and cannot be changed once they go into production. To “run” a robot, you must have a production license.

It is possible to track the robot’s actions in real-time using Rocketbot’s various display options for each event:

  • Output by terminal screen of events.
  • Log file in “app.log”.
  • Module to dump or load variables to file.
  • Module to see in real-time in a custom floating screen log.
  • Event logs in the R.O.C. (Rocketbot Orchestrator Center).
  • Additionally, the email, SMS, voice, and WhatsApp modules for sending data provide convenient access to the robot’s status on any device at any time.

You can access the tool modules by visiting

Every time a robot is saved in Rocketbot, a copy of its code is created in a SQLite3 database and a version of it is generated. This version is stored in the DB you are using (robot.db by default). You can also export the robot to a .JSON file, which you can use with any version repository, such as GitHub or Bitbucket.

  • Store a new version in the DB each time you save.
  • Export project to another DB and do versioning.
  • Export to JSON and do versioning.

Export to JSON and choose the most fitting versioning tool for your business needs.

The Orchestrator implements role-based user control (RBAC), which enables users to interact with specific areas of the orchestrator based on their assigned roles.

The orchestrator sends robots to configured instances and receives system status information such as RAM, CPU, and disk usage.

After logging in, the connection to the instances is established using encrypted connections.

Control all instances where your robots will run from R.O.C. Rocketbot Orchestrator Center.

R.O.C.’s RBAC system is based on:

  • Data in protected transit using JWT.
  • Login with 2-Step Verification 2FA (Google).
  • Passwords are stored encrypted in a database (Mysql/SqlServer/Postgres) by Hash Argon2 and bcrypt.
  • OWASP Top10 constant check.

Protect your data in transit using rules developed by the U.S. National Security Agency (NSA).

Monitor the status and behavior of the robot and its instance at any time with R.O.C.

  • Instance Type.
  • RAM, CPU and Disk space usage.
  • Connection status.
  • Robot running and stopping.
  • Obtain real-time execution log.
  • Launch and receive real-time data from multiple instances simultaneously.
  • Get runtimes.

Connect to data viewers like Tableau, PowerBi, Kibana, or Qlik.

All records and movements are stored to improve business analytics for timely decision making.

Rocketbot provides modules for cognitive capabilities from major vendors, including:

  • IBM Cloud
  • Google Tesseract
  • Google Vision
  • AWS Rekognition
  • AWS Textract
  • Azure
  • Abbyy
  • OCR Space

Modules can be downloaded from our marketplace.

We provide access to top-rated OCR engines in the market, enabling you to apply OCR to your documents without writing any code.

Rocketbot can connect to terminals from any operating system.

  • Launch D.O.S. applications.
  • Interact with SH terminals.
  • Module connection to SSH terminals.
  • Connection to AS400 / Mainframe terminals using a client such as Putty.
  • Connection through sFTP and FTP systems via terminal or GUI.

Choose the module that best fits your terminal system from our marketplace and gain the ability to control all of your data with just a few clicks.

Minimum requirements
  • Memory: 4GB RAM
  • Storage: 10GB
  • Processor: Intel Core i3-4340 or AMD FX-6300
Recommended requirements
  • Memory: 8GB RAM
  • Storage: 175GB
  • Processor: Intel Core i5

Start your path to automation

If you have questions, require personalized advice or want to see a demonstration of our products, speak to an expert and find out how you can get started in digital transformation