Windows and Linux
Same workflow, either runtime. One of the few RPA vendors to support production-scale Linux deployments in regulated industries.
Primo RPA Robot
The execution runtime that runs
where your enterprise runs
Primo RPA Robot executes automated workflows on Windows or Linux, attended or unattended. It interacts with applications and systems the way a human user does — including legacy interfaces, Citrix, virtual desktops, and remote environments where APIs aren't available.
Capabilities
Execution designed for enterprise environments
Attended and unattended
User-facing assistance for analysts and operators. Background execution for scheduled and event-driven workloads.
Triggered any way you operate
Runs on a schedule, on a system or business event, or on demand. Both foreground processes that need the user interface and background processes that run silently are supported.
Virtual and remote environments
Native automation of applications in Citrix, RDP, VMware Horizon, and other virtual desktop infrastructures, including legacy interfaces where APIs aren't available.
Broad application coverage
Interacts with desktop, web, terminal, and enterprise applications the way a user does, with a large library of ready actions and 100+ integrations.
Secure execution
Encrypted credential storage, role-based access, real-time transaction monitoring, compliance-ready audit trails.
Robot is the runtime layer that executes what Studio builds and Orchestrator dispatches. When a workflow is deployed from the development environment and queued for execution, Robot carries it out — on the operating system, machine type, and session the deployment requires. See how Robot fits into the full platform →
Linux is the runtime, not a port
Most RPA platforms were designed for Windows desktops, with Linux added later as a thin compatibility layer. Primo RPA Robot was built from the start to run natively on both — same activity library, same connectors, same workflow definitions. This is what made a full-scale RPA-to-Linux migration in regulated banking possible without rebuilding processes from scratch.
Read the Linux migration story →Execution at scaleWhat Robot is built
What Robot is built
to handle.
2
Operating systems, one workflow
Supported activities and connectors share the same workflow definitions across Windows and Linux runtimes.
24/7
Continuous unattended execution
Across scheduled and event-driven workloads.
1,000s
Concurrent robots per deployment
Designed to scale; actual capacity depends on deployment topology.
100+
Ready integrations
Across desktop, web, terminal, and API surfaces.
Figures represent design-capability ranges and platform defaults. Actual results depend on deployment configuration, workload, and environment.