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.

One pipeline for every idea

Ideas from anyone, scored the same way, ranked in one portfolio.

Benefit you can measure

Hours saved and net benefit come from the automation's own queue items or runs, not a spreadsheet.

Part of one platform

Opportunities link to the automations Orchestrator runs, so delivery and benefit stay connected.

Ideas lost in email

Every idea gets a key, an owner and a phase.

Prioritising by who shouts loudest

A priority score from potential, ease, value and votes.

Benefit nobody can prove

Measured hours saved and net benefit from real runs.

Approvals outside the system

Lifecycle moves can require an approval, recorded on the opportunity.

Automation CoE leads

Run intake, review and prioritisation in one place.

Business teams

Submit ideas and follow them through to production.

Finance and sponsors

Read business cases and measured benefit per automation.

Guided opportunity submission

A guided form with drafts and a duplicate check. Import captured processes as draft opportunities.

Register running automations

Track the benefit of an automation that is already live as an opportunity in Production.

Assessment and priority score

Automation potential, ease, estimated hours saved and votes combine into one priority score.

Business case forecast

Forecast ROI, payback and net present value from costs, rates and estimated hours.

Configurable lifecycle with approvals

13 phases in five stages by default. Moves can require information or an approval.

Measured benefit from real runs

Transactions, hours saved, gross benefit, robot cost and net, counted from queue items or runs.

Portfolio and pipeline

Rank opportunities by priority and move them stage by stage.

Application inventory

Keep the applications your automations use and see which opportunities depend on each.

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