Deploy CenterTurn off auto-deploy on Vercel, Render and more. Deploy what changed with one click. Your agent pushes 40 times. You deploy once. Works great with Claude Code: let the agent push, you decide what ships.
Install#
brew tap pschmetzer/tap && brew trust pschmetzer/tap && brew install --cask deploy-centerOr download the zip, unzip it and drag Deploy Center to Applications. Free, MIT, signed and notarized by Apple. Website: deploycenter.app.
Only the CLI (macOS, Linux, WSL, CI; no app): deploys on its own, checked against the
release's SHA-256, into ~/.local/bin without sudo. Or with Homebrew on macOS and Linux:
curl -fsSL https://deploycenter.app/install.sh | sh
brew install pschmetzer/tap/deploysDocker, CI keys and first steps: Install the CLI.
Homebrew notes and requirements#
Homebrew 6 asks you to trust a third-party tap once (brew trust). Without admin rights, add
--appdir="$HOME/Applications". Updates: the app updates itself (Check for Updates … in the app menu); brew upgrade --cask --greedy deploy-center also works.
| What | Needed for | Install |
|---|---|---|
| macOS 15 or newer, Apple silicon or Intel | the app | |
jq | everything (the app asks for it if it is missing) | brew install jq |
| Vercel CLI, which needs Node.js | Vercel | npm i -g vercel, then vercel login |
| Render API key | Render | dashboard.render.com → Account Settings → API Keys |
GitHub CLI gh | optional: what is waiting (New changes, commits and PRs) | brew install gh, then gh auth login |
The app finds vercel from nvm, volta or fnm only if your login shell sets them up (~/.zprofile, not only ~/.zshrc).
See Troubleshooting.
How it works#
- Connect. Vercel uses your
vercel login. For Render, paste an API key; it is stored in your macOS keychain. - Turn off auto-deploy. One click for all projects. A push now builds nothing.
- Deploy when you want. The app shows what is waiting. Select all changed + Deploy is the daily deploy.
New to it? Try it safely: look first, then one project, then all.
Batching many pushes (AI agents)? Safe deploys: only green CI, a health check with rollback, deploy windows and a risk light.
What it changes, and how to undo it#
| What Deploy Center does | How to undo it | |
|---|---|---|
| Vercel | Removes the project's Git connection. It writes down the repo and branch in ~/.config/deploys/vercel-repos.json first. | Project → Settings → Git → connect the repository again. |
| Render | Sets the service's auto-deploy to Off. The service stays connected to its repo. | Service → Settings → Build & Deploy → Auto-Deploy → On Commit. |
To turn auto-deploy back on: deploys vercel autodeploy-on <project>|--all and deploys render autodeploy-on <service>|--all, or in each dashboard. Uninstalling does not turn it back on.
Deploy hooks and GitHub workflows that deploy keep working; deploys triggers lists them. On Render, a
Blueprint with auto-sync can turn auto-deploy on again: add autoDeployTrigger: off to your services in
render.yaml. Details: Auto-deploy off and back on · Uninstall.
Next steps#
- Try it safely: look first, then one project, then all
- CLI reference: every
deployscommand - Troubleshooting when a message is unclear