Faq - Automate your Processes | Rocketbot

Clear your doubts and automate your processes

Minimum System Requirements

Processor

Intel Core i3-4340 or AMD FX-6300

Storage

10GB

Memory

4GB RAM

Recommended settings

Processor

Intel Core i5

Storage

175GB

Memory

8GB RAM

Further questions

Robots built in Rocketbot can be run dynamically depending on the process need of the process.

  • Assisted tool mode: from an icon on the desktop.
  • Hybrid waiting (trigger) for an event: key 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
Please find how to configure in our documentation center https://docs.rocketbot.co

Rocketbot has licenses that adapt to each company's needs, not only in costs, but also in the number of robots that need to be run, and in "where" they need to be run. Each license belongs to a team or "instance" and is identified by a unique TOKEN. This allows one developer per machine. The Developer license allows you to build a robot for free and run it from the development environment. The Desktop license allows you to run sequential production processes and the Servers license (Docker, WorkSpaces, MS Windows) allows you to run "several processes" in parallel. The number of processes to run will depend on the physical architecture and the process. We have SAP cases of six instances in parallel.

You can always find license and price variants on our website https://rocketbot.com

Rocketbot is compatible with any type of application. These can be desktop and web-based.

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

Rocketbot is designed to run on the three most important operating systems GNU/Linux (Ubuntu 18.04> Server Desktop or Docker), MS Windows (win7>, Server 2012>) and Mac OsX.

This allows a process to be run both on Desktop and servers, making Hybrid Processing possible.

This versatility allows having the process in a Docker Linux server and the data taken from Windows services, to be shown in a Desktop Mac web, with a fully hybrid infrastructure.

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

Rocketbot can run on any Cloud with an active desktop. This means it must be able to raise a work desktop.

This allows us to work with the leading Cloud providers in the market.
  • AWS WorkSpaces or Windows 10 Servers>
  • Azure and virtual servers MS Windows /Linux Ubuntu.
  • If your server does not have an active desktop you can use our Docker image which contains a desktop and Rocketbot Play ready to work.

Rocketbot needs an active desktop to work. Any service offering one is compatible with Rocketbot.

Rocketbot has a Docker image ready to work.

It has the following features:

  • Ubuntu 18.04 Linux.
  • Xfce4 active desktop.
  • Non-VNC for connecting via browser.
  • Remote desktop clients
  • Firefox/Chrome browsers.
  • Rocketbot 0.4.9 >.
  • User and password protection.
  • External work folder for robot backup.
  • Based on OpenSource image

Rocketbot has a wide variety of modules that allow you to connect to most databases on the market, both SQL and Non-SQL.
  • MySQL
  • SQL Server
  • Oracle SQL
  • MongoDB
  • SQLite

Working with modules allows us to add new database drivers simply and efficiently.

Rocketbot has a wide variety of modules for controlling office tools from the main World Class vendors.
  • Google Docs
  • Google Spreadsheets
  • Google Drive
  • Google Gmail
  • MS Outlook 365
  • MS Office Word
  • MS Office Excel
  • MS Office PowerPoint
You can find the modules for these tools at https://market.rocketbot.co in the Office or Google section.

At Rocketbot, we have data encryption modules. These can be stored in the MS Windows credentials system. There are also encryption modules, both for production code and separate data.
  • AES in CBC mode with a 128-bit key for encryption; using PKCS7 padding.
  • HMAC using SHA256 for authentication.

Robots created in Rocketbot are encrypted when they move into production, protecting the entire code and the variables used in them.

When moved into production, all robots are encrypted and cannot be modified. You will need a production license to “run” them.

It is always possible to know what the robot is doing in real time. Rocketbot has several methods showing each event:
  • Terminal screen event output.
  • Log file in "app.log".
  • Module for dumping or loading variables to file.
  • Module to view a customized log in a floating screen in real time.
  • Event logs in R.O.C. (Rocketbot Orchestrator Center).
  • Along with modules for sending data via email, SMS, Voice over phone, WhatsApp and R.O.C., learning about the status of your robot is easy
You will find the modules to work with these tools at https://market.rocketbot.co.

Every time a robot is saved to Rocketbot, a copy of the code is created in an SQLite3 database. This creates a version thereof and it is stored on the DB being used (default robot.db).
The robot can also be exported to a .JSON file, which can be used in any version repository such as GitHub or Bitbucke.
  • Saves a new version on the DB for each save.
  • Export project to another DB and do versioning.
  • Export robot to JSON and do versioning.

Choose to export to JSON and you can version your code with the tool that best suits your business.

The Orchestrator has role-based access control (RBAC) which allows interaction with the orchestrator parts depending on the user role. The Orchestrator sends the robots to the configured instances and receives all the system status information (RAM, CPU, Disk, etc.). Upon logging in, connection to the instances is made with encrypted connections.

Control all your robot running instances from the R.O.C. Rocketbot Orchestrator Center

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

  • In-transit data is JWT-protected.
  • 2-Step 2FA Login (Google).
  • Passwords are encrypted into a database (Mysql/SqlServer/Postgres) by Hash Argon2 and bcrypt.
  • OWASP Top10 Constant Check.

Protect all your in-transit data in with rules created by the US NSA

With the R.O.C., you can monitor the status and behavior of the robot and its instance at any time.

  • Type of Instance.
  • RAM, CPU and Disk space usage.
  • Connection status.
  • Running and stopping a Robot.
  • Get real time execution log.
  • Launching and obtaining real-time data from several instances simultaneously.
  • Obtain running times.

You can connect to data viewers such as: Tableau, PowerBi, Kibana or Qlik.

All records and transactions are saved to create analytical improvements for the business and make timely decisions.

In Rocketbot we have cognitive capacity modules from the most important vendors such as:

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

Modules can be downloaded from our Marketplace.

We connect to the best OCR engines on the market. Apply OCR to your document without writing any code.

Rocketbot has the ability to connect to terminal systems from any type of operating system.

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

Choose the module that best suits your terminal system in our Marketplace and you will control your entire data in a few clicks.

Download our PDF to learn more.

To download complete the following form.