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.

From requirement to defect

Requirements, test cases, executions and defects stay linked, so coverage gaps show.

Tests that run on Robots

Automated test cases run as jobs on the same Robots as production.

Part of one platform

Lives in the Orchestrator web app and reads your workspaces, processes and jobs.

Untested automation changes

Releases and requirements show what still needs a test.

Results scattered across tools

Report results from CI, Studio and Robots into one project.

Flaky tests hiding defects

A flaky cases report and defect aging.

Audit questions about testing

Versioned test cases and a history on every item.

QA leads

Plan release testing and report quality.

Automation engineers

Link automated tests and rerun failures.

Manual testers

Record step-by-step results and raise defects.

Releases and requirements

Plan what to test per release and link test cases to the requirements they verify.

Versioned test cases

Manual, automated or hybrid test cases. Every change creates a new version.

Static and dynamic test sets

Group test cases as a fixed list or by a rule.

Automated runs on Robots

Automated test cases run as Orchestrator jobs on your Robots. Rerun only the failures.

Manual results step by step

Testers record each step's result, with attachments.

Results from CI and Studio

Report results from pytest, Playwright, JUnit and other frameworks, or from Studio.

Defects linked to results

Raise defects from failed results and link them to test cases and requirements.

Coverage and quality reports

Coverage matrix and gaps, execution summary, requirement status, defect aging and flaky cases.

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