Platform
Deployment options
Self-hosted RPA and automation on your own infrastructure, or Orchestrator run for you in the VeloPhex cloud or a dedicated cloud.
Talk to an architectWhy it matters
Own the infrastructure, keep the platform
Infrastructure ownership
Self-host Orchestrator in your data center or cloud account, or let VeloPhex run it for you.
Data where you decide
On-premises, queue items, logs, packages and credentials stay in storage you operate.
The same Robots everywhere
Robots run on your Windows machines and connect outbound only, whichever option you choose.
Compare
Three ways to run Orchestrator
Studio and Robots install on your Windows machines in every option. What changes is who runs the control plane.
| At a glance | On-premises | VeloPhex cloud | Dedicated cloud |
|---|---|---|---|
| Who runs Orchestrator | Your team | VeloPhex | VeloPhex |
| Tenancy | Your own installation | Shared, with a data key and package feed per tenant | Single tenant: a cell for your organization only |
| Where it runs | Your data center or cloud account | VeloPhex-operated cloud | VeloPhex-operated cloud, dedicated to you |
| Install and upgrades | You, with Docker Compose | VeloPhex | VeloPhex |
| Database, storage and backups | You: PostgreSQL 18 and local disk, S3-compatible or Azure Blob storage | VeloPhex | VeloPhex |
| TLS certificates | Let's Encrypt, an internal CA or your own | VeloPhex | VeloPhex |
| Robot machines | Yours, outbound only | Yours, outbound only | Yours, outbound only |
| Users, roles and workspaces | You | You | You |
| Data location | Wherever you run it | Agreed with you before you start | Agreed with you before you start |
Who each option is for
On-premises
For teams whose policies keep the control plane inside their own network. Run Orchestrator with Docker Compose on a Linux host (4 vCPU, 8 GB RAM minimum), and bring PostgreSQL 18 or use the bundled database.
VeloPhex cloud
For teams that want to start without running servers. VeloPhex operates Orchestrator and its upgrades, and your tenant gets its own encryption key, package feed and access scopes.
Dedicated cloud
For teams that want a cell of their own without the operations work. VeloPhex runs a single-tenant Orchestrator for your organization, with its own database, API, gateway and worker.
Data residency
Orchestrator stores queue items, job records, logs, packages and encrypted credentials. On-premises, all of it stays in the database and storage you operate. In the VeloPhex cloud and a dedicated cloud, we agree where your data is stored before you start.
In every option, Robots run on your own Windows machines. The applications and files they automate stay in your network, and Robots reach Orchestrator over outbound HTTPS only.
The same in every option
- One Windows Setup with three profiles: Developer, Attended and Unattended.
- The same signed package format, package feed per tenant and REST API.
- The same security model: key-pair Robot identity, encrypted and leased secrets, workspace RBAC and an append-only audit log.
- A database schema that only changes additively, so an upgrade can be rolled back by rolling back the image.
Read more about security at VeloPhex and how the platform scales.
Bring your hardest deployment questions.
Talk to an architect