Trust
Security at VeloPhex
How the platform protects your automations, credentials and data, and which controls stay with you.
Security documentationSecurity model
How the platform protects your automation
Every caller is authenticated and every permission is checked. Secrets stay encrypted until the moment a Robot needs them, packages are verified before they run, and every change leaves a record. These are architectural controls built into the product, not third-party certifications; ask us about the status of any audit or certification your review needs.
Authenticated by default
Every API endpoint requires a signed-in caller. A resource you cannot see returns 404, not 403.
Machine identity
Each Robot holds its own key pair and short-lived tokens scoped to the job it is running.
Encrypted, leased secrets
Envelope encryption with a data key per tenant, and leases instead of passwords in job claims.
Access by role and workspace
Roles and groups assigned at tenant or workspace scope.
Append-only audit
Changes to identity, roles, assets, packages, jobs, queues and machines are recorded.
Verified packages
One signature format across the platform, and every verifier fails closed.
Identity and sign-in
- People sign in with a local account, optionally with two-step sign-in (TOTP), or through single sign-on with OpenID Connect, including a Microsoft Entra ID preset. The session lives in a server-side cookie (HttpOnly, Secure, SameSite=Strict) with a fixed lifetime, and account lockout and password rules are enforced. Passwords are hashed with PBKDF2-HMAC-SHA512.
- Personal access tokens (
vpx_pat_…) for CI and the SDK are shown once and stored only as keyed HMAC-SHA256 hashes. - Studio signs in through your browser with OAuth, keeps its token in Windows Credential Manager and refuses to send it over plain HTTP.
- Robots enroll with a single-use enrollment key that is bound to the first host that uses it. The Robot generates its own key pair, and the private key never leaves the machine. It authenticates with OAuth client credentials and
private_key_jwt(RFC 7523): asymmetric algorithms only, replay protection, assertions valid for at most 5 minutes and access tokens for 10. Keys can be rotated, and revocation takes effect at the next token issue. - Each job gets its own execution token, valid only while the attempt runs and scoped to that job, workspace and Robot.
Secrets and encryption
- Envelope encryption. Assets and credentials are encrypted with AES-256-GCM. Each tenant has its own data key, wrapped by a key-encryption key, and each value is bound to its tenant, key and purpose. Data keys can be rotated and re-wrapped, and production refuses to start with the development key. The key-encryption key can be held in Azure Key Vault or AWS KMS.
- Credential stores. Every tenant gets a built-in store named "Orchestrator", and can add external vaults: Azure Key Vault, CyberArk, Delinea Secret Server, AWS Secrets Manager, HashiCorp Vault, GCP Secret Manager or BeyondTrust Password Safe.
- Credential leases. A job claim never carries a password. The Robot redeems a lease, bound to one intended use, seconds before launch. The secret is never persisted or logged, and if the store is unreachable the job returns to Pending without using up its retries.
- On the machine. Robot secrets are protected with Windows DPAPI in access-controlled files, logs pass through a secret redactor, and sensitive workflow state is DPAPI-protected.
- In transit. TLS is terminated by the bundled Caddy server (automatic Let's Encrypt, an internal CA or your own certificate), with HTTP/2, HSTS, a content security policy and Host-header checks.
- At rest. On-premises, encryption of the database and storage volumes follows your disks or storage service, on top of the application-level encryption of secrets.
Access control
- Permission-based roles. Built-in roles include Administrator, Workspace Administrator, Operator, Viewer, Automation Developer and Automation User. Roles are assigned to people or groups at tenant or workspace scope, with a separate platform-administrator policy.
- Workspaces are the unit of access for packages, jobs and queues. A machine only runs jobs from the workspaces assigned to it.
- Checked everywhere. Every endpoint requires an authenticated caller, and an automated test checks every controller action for an authorization rule.
- Tenant scoping. Every tenant-owned record carries its tenant, data access is always scoped to a tenant, and PostgreSQL row-level security enforces the same boundary in the database. Blob storage and the package feed are partitioned per tenant.
Audit
- Append-only audit events record scope, actor, action, entity, data, correlation ID, IP address and time. They cover identity, roles, assets, packages, jobs, queues, triggers and machines, and you can read them in the UI or through the API.
- Signed webhooks deliver events to your systems, with retries, a dead-letter list and a deliveries view.
Network model
- Robots connect outbound only: HTTPS for claims, leases, results and downloads, plus one outbound WebSocket for commands. No inbound ports are opened on Robot machines.
- Short-lived download grants. Packages are fetched through presigned S3 URLs, Azure SAS tokens or the API.
- Rate limiting before authentication, with separate policies for sign-in, registration, Robots, uploads and feed reads.
- Trusted proxies only. The API will not start without a trusted-proxy network configured.
Supply chain
- One signing implementation across Studio, Robot and Orchestrator: a detached signature (RSASSA-PSS-SHA512 or ECDSA-SHA512), with signers pinned by thumbprint or public key rather than by certificate authority. A signed timestamp lets a signature outlive its certificate, and every verifier fails closed.
- VeloPhex packages must carry the VeloPhex signature on the Orchestrator, the Robot and Studio. For your own packages you can require signatures and choose the trusted signers, and a signature that is present is always verified.
- File-level integrity. Package manifests list the SHA-512 of every file and unlisted files are refused. The Robot checks the package hash and extracts it with a safe extractor that blocks path traversal and archive bombs.
- Checked before every start. The workflow executor is verified by hash and Authenticode signature with a pinned signer. Each attempt then runs in its own process inside a Windows Job Object with memory and process limits and an environment built from empty.
- Transparent releases. Each release carries a CycloneDX SBOM, third-party notices, SHA-256 checksums and build provenance. Container base images are pinned by digest, and the build fails on moderate or worse dependency advisories.
Deployment choices
Choose where Orchestrator runs
Compare deployment optionsOn-premises
You run Orchestrator in your data center or cloud account, and your data stays in systems you operate.
VeloPhex cloud
VeloPhex runs Orchestrator. Each tenant has its own data key, package feed and access scopes.
Dedicated cloud
A single-tenant Orchestrator run by VeloPhex for your organization only.
Responsible disclosure
If you believe you have found a security vulnerability in VeloPhex, email security@velophex.com with a description, the steps to reproduce it and the affected component or version. Please give us reasonable time to investigate and fix the issue before you disclose it publicly, and do not access, change or delete data that is not yours while testing. We will acknowledge your report and keep you informed as we work on it.
For configuration guidance, hardening steps and the full security model, read the security documentation.
Bring your hardest deployment questions.
Talk to an architect