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.

Shared, typed records

Entities with typed fields and rules, shared by automations and people.

Same data everywhere

Workflows, Python, the web app and the HTTP API use one API.

Part of one platform

Lives in Orchestrator workspaces, with its roles, and runs next to your jobs and queues.

Spreadsheets as a database

Typed fields, unique rules and revisions.

Duplicate writes on retry

Retried writes can be made safe.

Automations tied to one workspace

Entities are addressed by name.

Data nobody can audit

Every record carries who created and changed it, and when.

Automation developers

Keep state and reference data out of spreadsheets.

Operations teams

Read and correct records in the web app.

Integration teams

Read and write the same records over HTTP.

Typed entities and fields

Entities such as Invoice or Vendor with typed fields, required, unique and indexed rules, and choice sets.

One API for everyone

People in the web app, workflows, Python and other clients use the same API and error catalogue.

Workflow activities

Six activities in the Orchestrator activities pack read and write records.

Python runtime access

Read and write records from Python automations with velophex.runtime.

Portable by name

Automations address entities by name, so they run unchanged in another workspace.

Import, export and filters

Filter, sort and page records, import and export them, and make retried writes safe.

Roles and limits

Data Hub roles per workspace and enforced limits per plan.

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