RPA platform

An enterprise RPA platform built for Python and AI agents

Build robots visually or in Python, run them attended or unattended on Windows, and govern them from one Orchestrator, on-premises or in the cloud.

Request a demo Explore the platform

What is an RPA platform?

An RPA (robotic process automation) platform is the software used to build software robots, run them on machines and manage them at scale. It has three parts: a designer to build automations, robots that execute them against applications, and an orchestrator that schedules jobs, stores credentials, assigns work and keeps an audit trail.

VeloPhex covers all three, and adds what most teams now need from RPA: real Python next to the visual designer, AI agents for the steps rules cannot handle, and a control plane you can run on-premises or in the cloud.

The platform

Everything an enterprise RPA program needs

Studio

Visual designer for sequences, flowcharts and state machines, with a live debugger, UI element capture and Git.

Python SDK

Typed Python automations with assets, secrets and queues, packaged like any Studio workflow.

Robot

Attended and unattended Windows Robots with key-pair identity and outbound-only connections.

Orchestrator

Jobs, queues with SLAs, triggers, encrypted credentials, RBAC and an append-only audit log.

Evaluate

What to check in an RPA platform

The questions that separate a pilot from a program that scales.

Question	Why it matters	VeloPhex
Can engineers write real code?	Complex logic is easier to test and review in code	Python SDK, same packages and Robots as Studio
Where can the control plane run?	Data residency and security policies	On-premises, VeloPhex cloud or a dedicated cloud
How do robots hold credentials?	Stored passwords are a top RPA risk	Leased per job from an encrypted vault or your own
Can it handle unstructured work?	Emails, documents and judgement calls	Python AI agents today; managed agents in beta
Is every change audited?	Auditors ask who changed what and when	Append-only audit across identity, packages, jobs and queues

How it works

Follow one invoice from inbox to ERP

AP mailbox and portals

Invoice workflow

Matching rules

Collect and capture

3-way match

AP review

Post to ERP

Invoices queue

Build the process once

Model the steps in the Studio designer and write the tolerance rules in Python. Both sit in one project, go through the same review and ship as one package.

VeloPhex Studio

Robots do the repetitive work

Robots collect invoices from the AP mailbox and supplier portals, capture header and line data, and match each invoice to its purchase order and goods receipt.

VeloPhex Robot

People only see the exceptions

Low-confidence fields and invoices outside tolerance land in a work queue with the reason attached. AP works through that list while everything else keeps moving.

Orchestrator keeps it on schedule and on record

Orchestrator schedules the robots, retries failed items and keeps the queue moving. Every invoice posted to the ERP is logged, and every change to the process leaves an audit record.

VeloPhex Orchestrator

Comparing RPA vendors?

The buyer's guide compares eight enterprise RPA platforms, including UiPath, Automation Anywhere, Blue Prism and Power Automate, on the same criteria.

Read the RPA platform buyer's guide Python SDK quickstart

RPA platform questions

What does an RPA platform include?

A designer to build automations, robots that run them on machines, and an orchestrator that schedules jobs, stores credentials, distributes queue work and records an audit trail. VeloPhex provides Studio and the Python SDK, Robot, and Orchestrator.

What is the difference between RPA and AI agents?

RPA follows rules you write, so the same input gives the same result. AI agents use a model to choose the next step, which suits unstructured input but needs limits and review. VeloPhex runs both, so a robot can hand a judgement step to an agent and carry on.

Can I build RPA in Python?

Yes. The VeloPhex Python SDK turns typed Python functions into automations with access to assets, secrets and queues. They are packaged, signed and run on the same Robots as Studio workflows.

Can VeloPhex run on-premises?

Yes. Orchestrator runs in your data center or cloud account with Docker Compose or Kubernetes, or VeloPhex runs it for you in the VeloPhex cloud or a dedicated cloud. Robots run on your Windows machines in every option.

Does VeloPhex support attended and unattended robots?

Yes. Robots run next to a person through the Assistant app, or unattended in the background as a Windows service, with Developer, Attended, Unattended and Headless profiles.

Free tools

Is your process a fit for RPA or AI agents?

Automation Fit Assessment

Assess your business process in approximately six minutes. Answer 14 practical questions to discover whether rule-based automation, AI agents, or a coordinated combination of robots, agents, APIs, and human decisions is the best fit.

Automation ROI Calculator

Estimate hours returned, annual savings and payback from your own assumptions.

See VeloPhex RPA on your own processes

A 45-minute technical session with our product team.

Request a demo