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.

Typed Python automations

Type hints become input and output schemas; assets, secrets and queues come from the runtime client.

AI agents with your framework

LangChain, LangGraph, CrewAI or a model SDK as ordinary locked dependencies.

Part of one platform

velophex pack builds the same package format as Studio, run by the Robot Python runtime and governed by Orchestrator.

Scripts with no operations layer

Schedules, queues, retries and logs come from Orchestrator.

Secrets in code

Read secrets and credentials at run time instead of storing them.

Dependency drift

Pin PyPI packages in a uv lock file; each package gets its own environment on the Robot.

Untested changes

velophex run executes an automation locally before you publish it.

Automation engineers

Write automations in Python with the tools they already use.

Data and AI engineers

Run Python AI agents with vault-held model keys and queue-driven work.

Teams with scripts on cron

Move scripts onto schedules, queues and retries with a record of every run.

Request a demo Check automation fit

Typed entry points

@velophex.entrypoint turns type hints into input and output JSON Schemas.

Runtime client

Read assets, redeem secrets and credentials, and work queue items from your code.

Business errors

Raise BusinessError for final outcomes. Other errors follow the retry policy.

Local runs

velophex run executes an automation on your machine before you publish it.

One-command packaging

velophex pack builds the same package format as Studio. Add --sign to sign it.

Locked dependencies

Pin pandas, httpx or other PyPI packages in a uv lock file.

Python AI agents

Build agents with LangChain, LangGraph, CrewAI or a model SDK as ordinary locked dependencies. Model keys come from the vault at run time.

Python Automation

Give developers a real Python framework for automation, with the operations layer included.

Automation Modernization

Move existing bots to a modern platform one process at a time, without a big-bang rewrite.

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

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.