Login
Updated on June 24, 2026

Robility Manager

Estimated reading: 6 minutes

This section outlines the server infrastructure, operating system, software, and access requirements necessary for the successful installation and operation of Robility Manager. These prerequisites must be validated and available before deployment activities commence to ensure a stable, secure, and supported platform environment. 

Operating System & Platform

1. Server Type: Windows Server – on-premises physical, virtual machine, or cloud VM.
2. Operating System: Windows Server 2022 and above Newer LTS releases are acceptable provided they support .NET Framework 4.8.1 + and IIS 7.5+.
3. File System Access: Administrative rights to create custom folders for web binaries, log archives, and configuration files.

Required Software Stack 

Component Minimum Version Notes
.NET Core 8.0 and above Required for hosting applications using the ASP.NET Core hosting model.
Internet Information Services (IIS) 7.5 IIS role and required features must be installed and configured as described in Section 3.5.
Microsoft SQL Server 2019 The service account used for installation must have permissions to create and manage databases.
SSL Certificate TLS 1.2+ Certificate should be issued by a trusted Certificate Authority (CA) or a valid self-signed certificate for non-production environments.

Hardware Sizing – Pilot

This section outlines the recommended hardware configuration for Pilot, Proof-of-Concept (POC), or limited-scale deployments of the Robility Platform. The following minimum topology is recommended:

Module Unit Description
Server Module 1 Server Hosts the Robility Platform web modules, including RobilityManager, RobilityService, and the platform log file storage location.
Server Module 1 Server Hosts the Microsoft SQL Server database engine. For pilot or small-scale deployments, a shared SQL Server instance may be used.
Client Module 1 Machine RobilityDesigner installation for workflow developers to design, test, and publish automation workflows.
Client Module As Needed One machine per robot execution environment with RobilityRunner installed to execute published automation workflows.

Hardware Sizing – Production

This section provides the recommended infrastructure sizing for production deployments of the Robility Platform. Resource requirements may vary based on the number of active robots, concurrent workflow executions, transaction volumes, data retention policies, and overall platform utilization. The sizing recommendations below represent the minimum baseline for a production environment and should be scaled appropriately as the deployment grows.

Component CPU Memory (RAM) Storage
Robility Manager Web Tier 8 vCPU 32 GB 250 GB SSD
Robility SQL Database Tier 8 vCPU 64 GB 512 GB SSD

IIS Roles & Features

Robility Manager is hosted on Microsoft Internet Information Services (IIS). Prior to installation, the required IIS Server Roles and Features must be enabled on the target Windows Server to support application hosting, authentication, secure communications, and administration.

The following IIS components should be installed and configured:

Common HTTP Features

These features enable the web server to serve application content and handle standard HTTP requests.

a. Default Document
b. HTTP Errors
c. Static Content

Security

These security components support authentication, authorization, SSL/TLS communication, and access control.

a. Request Filtering
b. Basic Authentication
c. Centralized SSL Certificate Support
d. Client Certificate Mapping Authentication
e. IP and Domain Restrictions
f. URL Authorization
g. Windows Authentication

Management Tools

These tools provide administrative capabilities for managing and maintaining IIS.

a. IIS Management Console
b. IIS Management Scripts and Tools (Optional)

Additional Recommendations

1. Configure HTTPS using a valid SSL/TLS certificate issued by a trusted Certificate Authority (CA).
2. Ensure the IIS Application Pool identity has the necessary permissions to access application files, logs, and configuration directories.
3. Enable IIS logging for troubleshooting, auditing, and operational monitoring.
4. Apply the latest Windows Server and IIS security updates before deployment.

Note: All required IIS roles and features should be installed and verified before commencing the Robility Manager installation process.

Database Prerequisites

1. SQL Server Edition: Standard or Enterprise, version 2019 or higher.
2. Database: An empty database named ‘Robility’ to be pre-created.
3. Service Account: Dedicated SQL login with database creation, db_owner, and DDL permissions.

Information to be collected and shared with the Robility Support team:

a. Server name / instance
b. Database name
c. User ID (must have database create permission)
d. Password 

Networking, DNS & SSL

1. Domain Name: A fully qualified domain such as ‘Robility.companyname.com’ to be registered in the customer DNS server, pointing to the IIS web server.
2. SSL Certificate: A trusted CA-issued certificate (preferred) or a self-signed certificate bound to the FQDN in IIS for HTTPS communication.
3. Inbound Ports: 443 (HTTPS) open from all Designer and Runner endpoints to the Manager server. Port 80 may remain open during initial validation only.
4. Outbound Ports: 443 from Manager to Blob Storage, license server, and CDN endpoints (see Section 6).

Mail Server

RobilityManager triggers notifications, password resets, and workflow alerts via SMTP. The mail relay must support modern authentication (OAuth 2.0 / token-based). Provide:

1. SMTP host and port
2. Authentication type and credentials / app password
3. From-address (e.g., noreply-robility@companyname.com) provisioned in the mail tenant

Storage

RobilityManager uses Storage for platform files, features, and uploads. Provision a storage account and provide:

1. Azure
2. AWS
3. GCP or DB

Storage Allocation for RobilityManager

Asset Size Comments
Core Binaries 2500 MB – 2750 MB Web application binaries deployed on the IIS server, including all platform components and supporting libraries required for execution.
Log Files 300 MB Max (30 Files) Log files are limited to a maximum size of 10 MB per file per day. Older log files are automatically archived and purged using a FIFO (First-In, First-Out) retention policy to control storage utilization.

End-User Browser Requirements

RobilityManager web console is supported on the following browsers from any user machine that needs portal access:

1. Microsoft Edge – latest and stable
2. Google Chrome – latest and stable
3. Internet Explorer 11 (for legacy compatibility)

Security, Identity & Account Requirements

1. Service Accounts: Pre-provisioned service accounts for IIS application pool, SQL Server connection, and Runner robot logon. Document each account with intended scope and rotation policy.
2. Firewall Rules: Approved inbound 443 from Designer/Runner subnets to Manager; outbound 443 from Manager and all clients to Azure CDN and Sutherland endpoints (Section 6).
3. Endpoint Protection: Antivirus / EDR exclusions configured for the Robility install paths, log folders, and binaries on Manager, Designer, and Runner machines. Coordinate with the Infosec team for the exclusion list.
4. Group Policy: Ensure that GPOs do not block .NET Framework, IIS WCF activation, or unattended logon required by Runner.
5. SSL / TLS: TLS 1.2 enabled on the OS; legacy TLS 1.0/1.1 may be disabled per customer security baseline.

Licensing

1. Customer ID and Password: Issued by Sutherland for license activation against the Robility license server.
2. License Activation: Performed post-installation through the Manager web console; the Manager server must have outbound HTTPS access to https://licenseserver.sutherlandglobal.com.
3. Initial Admin Sign-up: After license activation, the first administrator user is created through the Sign-up flow on the Manager portal. 

URL Whitelisting

The following URLs must be allow-listed at the proxy, firewall, and endpoint protection layers from both the Manager server and all client machines. These endpoints handle license validation, feature downloads, and product updates.

1. Robility Hub: https://robility.sutherlandglobal.com/Robilityrepository  
2. License App: https://licenseserver.sutherlandglobal.com
3. Document Portal: https://docs.robility.ai/

Next - Deployment Pre-requisites Robility Flow
Share this Doc

Robility Manager

Or copy link

CONTENTS

Powered By Sutherland

Robility Chatbot
Robility Assistant
Online