Built so we hold as little as possible.
A tool that can deploy to your servers has to earn that access. These are the design decisions behind DeployCode, in plain language.
Your code stays on your server
Source is downloaded, scanned and built on your machine. To plan a deployment we read a small set of files through GitHub; we do not clone or store your repository.
The agent calls out, never in
The agent opens one encrypted connection to us. You do not open a management port, and you do not have to give us an SSH key.
Signed, fixed commands only
The agent accepts a short list of operations such as "deploy this release" or "restart this app". Each one is signed, numbered and time-limited. There is no "run this command" operation.
Secrets encrypted per customer
SSH keys, tokens and environment variables are encrypted with a key that belongs to your organization. They are masked in the dashboard and removed from logs.
Customers are separated in the database
Every record is tied to an organization and the database itself refuses to return another organization's rows, even if application code made a mistake.
Builds cannot reach the host
Repository code builds as an unprivileged user in a container with no Docker socket, limited memory and CPU, and a time limit.
Dangerous settings are dropped
Privileged containers, host networking, host mounts and published database ports in a Compose file are reported and left out of the deployment.
Everything sensitive is recorded
Deployments, secret changes, security-gate overrides and team changes go to an audit log that cannot be edited or deleted.
Least access to GitHub
Read-only access to the repositories you select, through short-lived tokens that never reach your browser.
Three scanners between a commit and production.
They run on your server before each release. Findings above your threshold stop the deployment until an owner or admin decides, with the reason on record.
Code
Semgrep looks for injection flaws, unsafe functions and other common mistakes in your source.
Secrets
Gitleaks finds keys, tokens and passwords that were committed by accident. The values themselves are never reported.
Dependencies and images
Trivy checks your packages and the built image against known vulnerabilities and tells you which version fixes each one.
Found something? Tell us.
Write to hello@ritvexa.com with the details. We will confirm we received it and keep you updated until it is fixed.
Keep control. Lose the busywork.
Connect a server, pick a repository, approve the plan. Free for your first server, no card required.