DunOps connects to your stack and runs the deployment work — DNS, certs, rollbacks, credentials — through a chat thread. You describe the outcome. It handles the ops.
Talks to the stack you already run on
Point DunOps at a repository and a domain. It reads your deploy, creates the DNS record, issues the cert, and verifies HTTPS — in the time it takes to write the message. No tab-switching. No propagation prayer.
.next| Op | Type | Name | Value | TTL |
|---|---|---|---|---|
| add | CNAME | docs | cname.vercel-dns.com | Auto |
| add | TXT | _vercel | vc-domain-verify=… | Auto |
| keep | A | @ | 76.76.21.21 | Auto |
dunops.com zone and request a new Let’s Encrypt cert for docs.dunops.com. Rollback is one click — your zone snapshot is taken automatically.Connect your CI and your host. DunOps watches for green builds and promotes on your signal — or on a schedule you set. Every promotion is logged, reversible, and requires no one to find the right button in the right dashboard.
9c4a7b19c4a7b1 to claw-code-parity · iad1Describe what's wrong. DunOps reads your recent deploys, identifies the last stable build, and rolls back — or tells you exactly why it can't. No war room. No runbook. No one has to own the 3am shift.
14:02 UTC, ~3min after deploy a91f3b. Suspected cause: changed middleware ordering in src/auth.ts. Suggested: roll back to e210cc8 (last healthy).e210cc8e210cc8 on Vercel (api-gateway)#incidentsAny DunOps thread can become a Playbook — a typed, parameterized graph you run from a button, a webhook, or another chat. Same steps. Same approval gates. Same outcome, every time.
Connect Vercel, Cloudflare, GitHub, AWS, or 40+ other providers in under a minute. DunOps reads everything. It writes nothing until you approve the plan.
Hosting & Runtime
Code & CI
Observability
Notify & Secrets
Scripts break silently. AI assistants hallucinate permissions. IaC is powerful but it isn't a chat. Here's where each one actually sits.
| What you need | DunOps | Scripts + dashboards The status quo | Generic AI ChatGPT · Cursor · Copilot | IaC Terraform · Pulumi |
|---|---|---|---|---|
Time to first working action From idea to a real change applied, on day one. | Minutes | Hours, if it works | Code, not action | Days of scaffolding |
Understands natural language Describe the outcome, not the syntax. | Native | Bash flags | Native | HCL / TypeScript |
Shows diff before running DNS, env vars, alias changes — visible up-front. | Every action | Inline maybe | Code diffs only | terraform plan |
Enforces approval gates Apex DNS, prod aliases, credential rotation pause. | Per-scope policy | If you remembered | Not the model's job | Via PR review |
Full audit trail Every plan, tool call, approval, signed and searchable. | Built-in | Shell history | Chat history only | tf state + git |
Reusable without re-writing Same flow, drift-free, parameterized at run time. | Playbooks | If you wrote it | Not a concept | Modules |
Manages complex multi-resource state State files, drift detection, large-scale graphs. | Per run, no state file | DIY | DIY | Core competency |
Runs entirely offline / air-gapped No network, no model calls, no audit upload. | Cloud product | Bash on a laptop | Cloud product | CLI runs local |
Not built for DevOps teams with ticketing systems. Built for the people who are the DevOps team.
You're building three things at once. You don't have time to remember which Cloudflare account holds which domain. DunOps holds that context for you.
Two reviewers on every prod DNS change. One audit trail your team can actually read. No more “wait, who deployed this?” in Slack at 9pm.
Twelve client workspaces. One interface. No credential sprawl, no missed renewals, no emergency Sunday morning.
“I ship 3 side projects a month. Dun keeps them straight.”
user · what's live and what's stale
dun · 4 live · 1 paused · stale: weekend-app · indie-news pinged 12d ago
Adi · acme-blog · indie-news · weekend-app · slow-cal
“13 client workspaces. One audit log per client, no missing.”
user · audit acme · 7 days
dun · 31 changes · 0 unapproved · 2 reverted · CSV ready
Mira · 13 workspaces · audit ready
“Two reviewers required for prod DNS — agent enforces it.”
user · drop CNAME api.acme.com
dun · blocked — prod DNS needs 2 approvers · invited @theo
Theo · seed-stage · prod safety on
Start on the free plan. Upgrade when your shipping cadence demands it — not before.
Hobby
Get started. No card.
Pro
For active shippers.
Team
For teams with standards.
Questions about volume or enterprise? Talk to us
A typed, parameterized graph behind a chat thread. Action nodes, decision gates, retry edges, parallel fan-outs — saved, named, and re-runnable from a button, a webhook, or another chat. Eleven ship with every new workspace; you can save your own once canvas authoring lands.
It plans first. Every request becomes a typed graph of steps you can read top-to-bottom before anything runs. Tools are restricted by workspace scope; risky steps (apex DNS, prod aliases, credential rotation) always pause for a human go. No autonomous mutations, ever.
Provider tokens are encrypted at rest and scoped per workspace. We never log, ship to a model, or surface them in chat — they live inside the connector adapter that calls the provider on your behalf. You can rotate or revoke any token from the integrations panel.
The Hobby plan is free forever: 1 workspace, 1 user, 20 workflow runs / month, 3 connected providers. No card. You hit a paid plan when you bring teammates in, want more runs, or need 2-key prod approvals — not before.
First-class connectors today: Vercel, Cloudflare, AWS, Render, Fly.io, Kubernetes, GitHub, GitLab, CircleCI, GitHub Actions, Datadog, Sentry, PagerDuty, Grafana, Slack, Linear, Notion, 1Password, Vault, Doppler. If it has an HTTP API, MCP bridges it. If it doesn't yet — request it, we add new connectors weekly.
Every mutating run takes a snapshot first. One click reverts — DNS records, alias swaps, credential rotations, env vars. The rollback is part of the same audit trail, signed and reversible for 24h.
No. DunOps drives the dashboards you already pay for. You keep your accounts, your billing, your OAuth scopes. We're read-only until you approve a change.
You already have an AI that writes the code. Give yourself one that ships it.
