System Requirements

Estimated reading: 5 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

Component	Minimum	Recommended	Comments
Designer	1 Machine	1 Machine	RobilityDesigner installation for workflow developers to design, test, and publish automation workflows.
Runner	As Needed	As Needed	One machine per robot execution environment with RobilityRunner installed to execute published automation workflows. Note: Runner supports both persistent and non-persistent execution environments.

Component	Minimum	Recommended	Comments
Processor	Quad-core (4 CPU cores), 2.0 GHz or faster, 64-bit (x64)	Octa-core (8 CPU cores), 2.0 GHz or faster, 64-bit (x64)	A 64-bit processor is required.
RAM	16 GB	32 GB or more	Higher memory is ideal for large automation projects or enterprise-grade applications.
Display Resolution	1920 × 1080	1920 × 1080	Applies to both desktop and laptop environments. Robility Manager is not optimized for resolutions below 1920 × 1080.
VDI Display Resolution	Dynamic / Native Matching	Dynamic / Native Matching	Default User Experience: When a VDI session is launched through standard clients such as Citrix Workspace, VMware Horizon, or Azure Virtual Desktop, the remote session automatically scales to match the endpoint's screen resolution, including 1080p (1920 × 1080), 1440p, 4K (3840 × 2160), or multi-monitor layouts.
Storage	100 GB HDD with at least 20 GB of free disk space	100 GB or larger SSD with at least 40 GB of free disk space	Refer to the disk space requirements below.
Installer	100 MB	100 MB	Installed on the developer workstation. Includes the core application binaries required for Robility Designer.
Features / Activities	300 MB – 1 GB	300 MB – 1 GB	Storage requirement varies depending on the activity packages, connectors, extensions, and features installed.
Log Files	300 MB Max (30 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.

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

Software	Minimum / Supported	Comments
Operating System	Windows 10 (22H2, 21H2, and 20H2, Pro, Enterprise; 64-bit) Windows 11 (64-bit) and above Windows 11 24H2 (64-bit) Windows Server 2019, 2022 and above	A supported 64-bit Windows operating system is required.
.NET Framework	Version 4.8.1 or higher	.NET Framework 4.8.1 is recommended. Ensure the latest .NET Framework updates are installed.
Browser	Google Chrome – Latest stable version Microsoft Edge – Latest stable version Internet Explorer 11 – Legacy compatibility	Browser extensions must be installed for browser automation.

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.

Network Access & Message Traffic

Component	Requirement	Comments
Network Access	HTTPS connectivity to the RobilityManager FQDN	Required for communication with RobilityManager.
Outbound Connectivity	Outbound HTTPS access to license, CDN, and feature update URLs	Refer to the applicable URLs for required outbound access.
Network Connectivity	Stable internet or private network connectivity	Required for reliable connectivity to RobilityManager.
TLS	TLS 1.2 or later	TLS 1.2 or later must be enabled.
Runner Traffic	2 heartbeat requests / minute	Baseline traffic generated by each Runner to RobilityManager.
	2 workflow requests / minute when idle	Traffic generated by each idle Runner.
	2 status requests / minute when running	Traffic generated while a workflow is running.
	20 transaction requests / minute when waiting on a transaction	Traffic generated when the Runner is waiting on a transaction.
	5 transaction requests / minute on average	Average traffic depends on workflow 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.

System Requirements

Hardware

Disk Space

Software

Recommended Cloud VM services

Network Access & Message Traffic

Additional Requirements

System Requirements

CONTENTS