For a server you manage, use the token-and-instructions path from capy deploy. It produces SECRETS_BLOB and PROJECT_KEY for a non-interactive capy run startup.
systemd service
Place the pair in a root-owned environment file outside the repository:
Add the generated values to /etc/my-app/capy-runtime.env using your normal protected host configuration process:
Then configure the service:
Install Capy with the release installer or npm before enabling the unit. The standalone installer uses /usr/local/bin when that folder is on your PATH and writable, otherwise ~/.local/bin. Install it in a service account’s PATH or use the absolute path that the installer reports.
capy run calls the Capy service when the process starts, decrypts in memory, and then starts the child. The server needs outbound connectivity then. A revoked pair prevents the next restart from decrypting; it does not change the environment of a process that is already running.
Containers on a VPS
Use the same protected env file with Docker:
--init is useful when the application creates child processes. The image should use the capy run entrypoint described in Docker.
Use a pair per environment. To change values, mint a new pair from the appropriate Capy branch, update the protected file, and restart the unit or container. Revoke an unused pair with capy deploy revoke <deploy-id>. Last modified on November 20, 2026