Deployments
Deploy a branch
Tell DunOps which branch to deploy and where. It fetches the latest commit, builds the deployment plan, and waits for your approval.
How it works
1
Describe your intent
Type what you want in a chat thread — no flags, no CLI commands. Just plain English.
2
Review the plan
DunOps shows the provider, project, branch, commit SHA, and target environment before touching anything.
3
Approve
Click Confirm — DunOps triggers the deployment and streams status back to the chat.
4
Monitor
DunOps reports when the deployment is live or if it failed, including a direct link to the deployed URL.
Example prompts
Type in a chat thread
Deploy main to production
Deploy the hotfix branch on Vercel
Push my latest commit to the staging environmentWhat DunOps checks before deploying
| Check | What happens |
|---|---|
| Branch exists | DunOps reads your connected repo to confirm the branch is there |
| Provider connected | Vercel / Netlify / Fly / Heroku / Railway — must be linked in Integrations |
| Project identified | DunOps finds the matching project from your provider account |
| Your approval | Deploy never runs until you confirm the plan card |
Tip
You can specify a commit SHA instead of a branch:
Deploy commit a1b2c3 to production