Railway and Render are planned Capy deploy targets in 0.9.7; Heroku has no Capy target adapter. You can use the runtime-pair path on all three while each platform retains responsibility for building and deploying your application.
Application setup
Install the CLI in the runtime image or package dependencies. Then wrap the start command:
For a Procfile-based application:
Create the pair with capy deploy and store both generated values in the platform’s environment-variable UI:
Railway and Render can run the start script or a custom start command. On Heroku, ensure @capysc/cli is available at runtime, not only as a development dependency.
Per-environment setup
Create a pair from the matching Capy branch for every staging or production service. Update both values together, then trigger the normal platform deploy or restart. The pair is consumed when the process starts; capy run does not read a local .env in deployed mode.
Because SECRETS_BLOB / PROJECT_KEY preserve existing-environment precedence, delete stale platform variables with the same names as Capy-delivered values when you want the Capy value to be used.
Revoke a pair with capy deploy revoke <deploy-id> to prevent new boots from decrypting it. Last modified on October 2, 2026
