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.

Robots and people in one flow

Robot tasks, user tasks and business rules in a BPMN diagram.

Long-running by design

A flow waits between steps for minutes or days without holding a robot.

Part of one platform

Robot tasks run your published processes as jobs; Flow Monitor watches what runs.

Processes split across jobs

One diagram for the whole process.

Robots blocked on waits

Waits hold a token, not a robot.

Changes that break running work

Instances stay pinned to the version they started with.

Lock-in to a private notation

BPMN 2.0 elements and BPMN import.

Process owners

Model end-to-end processes that span robots and people.

Automation developers

Chain automations with waits, approvals and error paths.

CoE architects

Version flows and keep running instances stable through changes.

BPMN 2.0 designer

Events, gateways, sub-processes and boundary events, with BPMN 2.0 import.

Robot, user and rule tasks

Run a process as a job, raise an Action Hub task, evaluate a business rule or call another flow.

Timers and messages

Wait for a timer or a message without holding a robot.

Multi-instance tasks

Run a task once per item of a list, in parallel or in sequence.

Saves that never fail

Drafts save automatically, and modelling problems are listed instead of blocking the save.

Pinned, versioned publishing

Each version records the exact package, Action App and called-flow versions. Running instances keep their version.

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 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.

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 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.