dunops.com/Docsbeta
Open app →

Getting started

Quick start

From zero to your first deployment in under 10 minutes.

Note

DunOps never executes mutations without your explicit approval. Every action shows a plan first — you approve it, then it runs.
1

Create your account

Go to dunops.com/login, enter your email address, and receive a one-time code. No password is ever stored.
2

Connect GitHub

Navigate to Settings → Integrations → GitHub and click Authorize. DunOps reads your repositories, branches, and latest commits so deploy flows know what to ship — no extra re-auth required once connected.
3

Connect your deployment platform

Navigate to Settings → Integrations and pick your platform — Vercel, Netlify, Fly, Heroku, or Railway. Paste your API token or click Connect with OAuth. DunOps validates the credential immediately and confirms which products are accessible.
4

Type your first intent

Open a new chat thread and describe what you want in plain English:
New chat thread
Deploy main to production

DunOps detects your stack, confirms the branch, and shows you a deployment plan. Approve it and it ships.

Save it as a Playbook

Once a flow works, save it as a Playbook. Next time, run it in one message instead of describing every step.

Connect GitHub

GitHub is DunOps's source of truth for repository context. Connecting it lets DunOps resolve branch names, read the latest commit SHA, and understand your project structure before proposing a deploy.

DunOps uses OAuth — no Personal Access Token to generate or rotate. You can revoke access at any time from your GitHub Authorized OAuth Apps page.

Note

DunOps only requests read access to your repositories. Write access (for features like auto-committing environment variable stubs) is opt-in and scoped to repositories you explicitly select.

Connect Vercel

Vercel is the most common deploy target for DunOps users. To connect, navigate to Settings → Integrations → Vercel and either:

  • OAuth (recommended) — Click Connect with Vercel. DunOps is added as a first-party integration on your Vercel team.
  • API token — Generate a token in Vercel → Settings → Tokens with Full Account scope and paste it into DunOps.

Warning

Vercel API tokens grant broad access to your account. Store them only in DunOps — never paste tokens into a chat message.

First deploy

With GitHub and Vercel connected, open a new chat thread. You can be as specific or as brief as you like:

Examples
Deploy main to production
Deploy the latest commit on feature/checkout to the staging environment
Promote the current staging build to prod

DunOps parses your intent, resolves the branch against your connected GitHub repo, identifies the matching Vercel project, and surfaces a plan card. The card shows:

  • Provider and project name
  • Branch, latest commit SHA, and commit message
  • Target environment (production, preview, or custom)
  • Any environment variables that will be affected

Click Confirm to trigger the deployment. DunOps streams the build log in real time and notifies you when the deployment is live. If anything goes wrong it shows you the error and proposes a fix — still behind the same approval gate.

Next steps

Connect a provider →

Detailed steps for every supported integration — OAuth, API tokens, and permissions needed.

Key concepts →

Approval gates, plan cards, playbooks, and the confirm-before-mutate model explained.