VeloPhex Robot

The Windows agent that runs workflow and Python automations, next to a person or in the background. It connects to Orchestrator outbound only, proves its identity with its own key pair and verifies every package before it runs.

Attended and unattended

Run next to a person with the Assistant, or in the background as a Windows service.

Workflows and Python

One agent runs Studio workflows and Python automations, each attempt in its own limited process.

Part of one platform

Enrolls with Orchestrator, takes jobs over an outbound connection and reports logs and results back.

Credential sprawl

Secrets are leased for one purpose seconds before use, never stored or logged.

Network exposure

HTTPS and one WebSocket out to Orchestrator. Nothing listens on the machine.

Untrusted packages

Hash and signature checks before anything runs.

Lost results on unstable links

Results, logs and attempt state wait on the machine until the connection returns.

Operations teams

Run unattended back-office work on a schedule or from a queue.

Employees at their desk

Start attended automations from the Assistant when they need them.

IT and security teams

Run automation on machines that open no inbound ports.

Request a demo Check automation fit

Attended & unattended

Workflow and Python runtimes

The Robot reports its runtimes, so jobs go only to machines that can run them.

Key-pair machine identity

A single-use enrollment key enrolls the machine. Its private key never leaves it.

Outbound-only connection

HTTPS and one WebSocket out to Orchestrator. No inbound ports on Robot machines.

Credential leases

A secret is redeemed for one purpose seconds before launch, never stored or logged.

Package verification

Hash and signature checks and a safe extractor before anything runs.

Process limits per attempt

Each attempt runs in its own process inside a Windows Job Object with memory and process limits.

Isolated Python environments

Each Python package gets its own environment, built from its uv lock file from your package index or an offline wheelhouse.

Resilient by design

Results, logs and attempt state wait on the machine and are sent when the link returns.

SAP GUI, Java and Citrix automation

UI automation for SAP GUI, Java applications and Citrix or RDP sessions.

Enterprise Automation

Automate end-to-end processes across ERP, CRM and legacy systems with governance built in.

Hybrid Automation

Run Orchestrator on-premises or in a dedicated cloud, with Robots next to the systems they automate.

Automation Modernization

Move existing bots to a modern platform one process at a time, without a big-bang rewrite.

VeloPhex Studio

The Windows IDE for building automations: a visual designer for sequences, flowcharts and state machines, C# expressions with IntelliSense, a live debugger, UI element capture, Git and publishing to Orchestrator.

VeloPhex Orchestrator

The control plane for your automation estate: tenants and workspaces, jobs, queues with SLAs, triggers, encrypted assets and credentials, a package feed per tenant, Robot fleets and an append-only audit log. Run it on-premises, in the VeloPhex cloud or in a dedicated cloud managed by VeloPhex.

VeloPhex Python SDK

Write automations as typed Python functions. The SDK turns type hints into input and output schemas, gives your code assets, secrets, credentials and queues at run time, and packs it into the same package format as Studio workflows.

VeloPhex Launchpad

The automation pipeline in Orchestrator. People submit ideas, reviewers assess and score them, approvers decide, delivery teams build them, and Launchpad measures the benefit from the automation's own runs.

VeloPhex QA Hub

Quality management inside Orchestrator: releases, requirements, versioned test cases, test sets, executions on your Robots and defects, with coverage and reports in one project.

VeloPhex Action Hub

When an automation reaches a decision it should not make alone, it raises a typed task. Someone claims it, fills in the form and picks an action, and the automation gets the decision as data and carries on.

VeloPhex Flow Studio

Draw BPMN flows that combine robot tasks, people's tasks, timers and messages. A flow waits between steps for minutes or days without holding a robot, and every published version is pinned for the instances that run it.

VeloPhex Flow Monitor

See how many flow instances are running, which stopped at an incident and how each step performs against its target, then resolve incidents, retry in bulk or migrate instances to a newer version.

VeloPhex Agents

Build an agent from instructions, a model and the tools it may use: your processes and your vector stores. It runs as a job on your Robots, records every step and stops for a person's approval before a process tool call.

VeloPhex Data Hub

Keep business records such as invoices, vendors or claims in typed entities in a workspace. Workflows, Python automations, people and other systems all read and write them through one API.