Capy 0.9.7 includes a Vercel deploy target. It uses Vercel’s environment-variable store, so applications read ordinary Vercel variables and do not use capy run in the Vercel build.
Prerequisites
Install and authenticate the Vercel CLI. A linked project directory (.vercel/project.json) is preferred; the target can also use Vercel project and organization identifiers supplied through the Vercel CLI environment.
Run capy deploy from the repository. Choose Vercel, then select the project directory, Vercel environment, Capy branch, and variable set. The target records its configuration in .capy/deploy.json without secret values.
Vercel targets are CI-only in this release. Capy writes selected values to Vercel, creates a deploy PR containing the delivery record, and leaves the code deploy to Vercel’s Git integration after that PR merges. It does not run vercel deploy itself.
For a Vercel Preview target, configure the Git branch that Vercel associates with the preview environment. Use a separate target for production and each preview branch that needs different Capy values.
Next.js
Vercel receives the selected values as normal environment variables. Next.js reads them through process.env during build and runtime according to Vercel’s environment model. Treat values exposed to client-side code as public: Next.js can include those values in browser output based on your application’s own configuration.
To re-enter target setup, run capy deploy --connect --edit; it pre-fills the target when exactly one is saved. Last modified on October 2, 2026
