System Requirements

Estimated reading: 4 minutes

This section outlines the hardware and software requirements to ensure the optimal performance of Robility Designer and Runner Enterprise across all deployment models—on-premises, cloud, or hybrid.

By following the recommended system configurations, you can maintain system stability, avoid compatibility issues, and achieve seamless and efficient operations. Meeting these requirements is key to delivering a secure, reliable, and high-performing Robility environment for your organization.

Hardware

1. Processor:

Minimum: Quad-core (4 CPU cores), 2.0 GHz or faster, 64-bit (x64)
Recommended: Quad-core (4 CPU cores), 2.0 GHz or faster, 64-bit (x64)

2. RAM:
Minimum: 16 GB
Recommended: 16 GB or more (ideal for large automation projects or enterprise-grade applications)

3. Display Resolution Requirements:
Desktop:
Minimum: 1024 x 768 (Note: Robility Manager is not optimized for this resolution)
Recommended: 1600 x 900

Laptop:
Minimum: 1024 x 768 (Note: Robility Manager is not optimized for this resolution)
Recommended: 1366 x 768

4. Storage Requirements:
Minimum: 100 GB HDD with at least 20 GB of free disk space.
Recommended: 100 GB or larger SSD with at least 40 GB of free disk space. Refer the disk space below.

Disk Space

Component	Size	Comments
Installer	100 MB	Installed on the developer workstation. Includes the core application binaries required for Robility Designer.
Features / Activities	300 MB – 1 GB	Storage requirement varies depending on the activity packages, connectors, extensions, and features installed.
Log Files	300 MB Max (30 Files)	Each log file is limited to a maximum size of 10 MB per day. Archived log files are managed using a FIFO (First-In, First-Out) purge policy to control disk usage.

Software

1. Operating System:
a. Windows 10 (22H2, 21H2, and 20H2, Pro, Enterprise; 64-bit)
b. Windows 11 (64-bit) and above
c. Windows 11 24H2 (64-bit)
d. Windows Server 2019, 2022 and above

2. .NET Framework Requirements:
a. Version: 4.8.1 or higher (4.8.1 is recommended)
b. Ensure the latest updates for the .NET Framework are installed.

3. Browser:
Supported for automation:
a. Google Chrome (latest stable version)
b. Microsoft Edge (latest stable version)
c. Internet Explorer 11 (for legacy compatibility)
Extensions must be installed for browser automation.

Network Access & Message Traffic

1. HTTPS connectivity to the RobilityManager FQDN.
2. Outbound HTTPS to license, CDN, and feature update URLs. Click here to refer.
3. Stable internet or private network connectivity to Robility Manager.
4. TLS 1.2 or later enabled.

Runner:

Each Runner generates the following baseline traffic to RobilityManager (used for bandwidth and load balancer sizing):

1. 2 heartbeat requests / minute.
2. 2 workflow requests / minute when idle.
3. 2 status requests / minute when running.
4. 20 transaction requests / minute when waiting on a transaction.
5. 5 transaction requests / minute on average (depends on processing time

Additional Requirements

1. Administrator Rights:
Required for installation and specific features, such as setting up browser extensions.

2. Excel/Office Integration Requirements:
Microsoft Office (versions 2007, 2010, 2013, 2016, 2019, or 365 desktop editions) is required for automating tasks in Excel and Outlook.

3. Robility Manager Requirements:
For users integrating Robility Designer with Manager:
a. Ensure the system can establish communication with the Manager server.
b. SSL/TLS 1.2 is mandatory for secure communication.

4. Windows Registry:
Read & Write access is required during the installation of Robility Designer and Runner to configure essential registry entries for proper functionality.
Administrative Rights: Necessary for installing the Robility Runner.

5. Remote Desktop:
The Remote Desktop option must be enabled to support Robility Runner Auto Login for service accounts and user accounts.

6. URL Whitelisting:
Specified URLs must be whitelisted to ensure the proper functioning of Robility Designer and Runner across all deployment models. Click here to refer.

7. Group Policy:
For Robility’s Chrome and Edge browser automation, specific group policy configurations and prerequisites must be enabled. Click here to refer.

8. VM Name Requirements:
While creating virtual machines or Citrix environments, the machine name must not contain special characters. Only hyphens (-) and underscores (_) are permitted, and they should be used only within the name, not at the beginning.

9. User Account:
Dedicated service account with login rights, ideally non-interactive for unattended execution.

10. Auto-logon:
Auto Logon should be configured for unattended execution. Click here to refer.

Recommended Cloud VM services

The recommended Windows Virtual Machine (VM) services for hosting Robility Designer and Robility Runner in the cloud provider.

Cloud Provider	Recommended VM Service
Microsoft Azure	Azure Virtual Machine (Windows) configured with the recommended Windows Server operating system and sizing based on the deployment environment.
Amazon Web Services (AWS)	Amazon EC2 Windows Instance configured with the recommended Windows Server AMI and compute resources required for the Robility platform.
Google Cloud Platform (GCP)	Compute Engine Windows Virtual Machine configured with the recommended Windows Server image and appropriate CPU, memory, and storage allocation.

System Requirements

Hardware

Disk Space

Software

Network Access & Message Traffic

Additional Requirements

Recommended Cloud VM services

System Requirements

CONTENTS