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.

Agents with guardrails

A person approves each process tool call with its exact arguments.

Tested before they go live

Evaluate a version against known cases and gate publishing on the score.

Part of one platform

Runs as jobs on your Robots, uses your processes as tools and keeps model keys in Orchestrator.

Agents acting unchecked

Process tool calls wait for a person's approval.

Black-box runs

A trace of every model call, search and tool call.

Model keys on machines

Keys stay in Orchestrator. Robots never see them.

Regressions after a change

Evaluations score each version before it is published.

Automation teams

Add reasoning to processes without giving up control.

AI engineers

Ship agents with traces, versions and evaluations.

Risk and compliance

Review every step and every approved tool call.

Agent builder

Instructions, a model, optional input and output schemas, and the tools the agent may use.

Processes as tools

Agents call your published automations. Each process tool call waits for a person to approve it.

Vector stores

Load documents from an automation and let agents search them as a knowledge tool.

MCP servers

Register Model Context Protocol servers in a workspace so automations can call their tools.

Runs on your Robots

Every run is a job on a Robot with the Python runtime. Model keys stay in Orchestrator.

Step-by-step traces

Every model call, search, tool call and approval, with tokens, duration and cost.

Evaluations and publishing gate

Score a version against a dataset of known cases and block publishing below a threshold.

Versioned agents

Published versions are unchangeable snapshots of the definition, its tools and its model.

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