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 https://market.rocketbot.co.

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