Updated August 21, 2026

What is Velo

Velo is the remote execution layer for enterprise-app automation. You keep SAP, Salesforce, and the rest of the stack. Velo absorbs the runtime, scale, and security needed to run validations from CI or a third-party tool.

Two ways in:

• REST — API key or dashboard JWT. Any system that can POST /executions (Rev-Trac today).
• Test engine — Robot Framework via robotframework-velo-cli (Copado CRT today). Same pattern for Playwright and later engines.

What Velo does

• Runs suites against supported app clients (UI or headless) in managed containers
• Streams live logs and records session video when the client has a display
• Provides a dashboard for teams to trigger runs, view results, and manage suites
• Exposes a CLI and REST API for CI/CD and ALM tools
• Reaches private systems via an outbound-only tunnel, or via client-specific paths (for example SAP Router)

App clients and engines

A client is the surface under test. An engine is the script runner. They are not the same thing.

See the support matrix for remote vs local, and core concepts for how clients, engines, and images fit together.

Who it's for

Velo is for test engineers, QA leads, and platform/DevOps teams that already write automated tests against enterprise apps and need those tests to run remotely — in CI, from Copado CRT, or from any REST client — without owning the execution farm.

How it fits your workflow

Your suite (Robot, Playwright, …)
        │
        ▼
  REST or engine CLI  ──►  Velo  ──►  Engine × client image
        │                                  │
        ▼                                  ▼
   Live logs                          Your app client
   Recordings                         (on-prem or cloud)
   Artifacts

Next steps

• Check the support matrix — is your client supported?
• Follow the Quickstart to run the first suite.
• Read Core concepts if you need the model first.