About DunOps
Built by devs who kept breaking their own DNS.
DunOps exists because the vibe-coding stack has a hole in it. Claude, Cursor, and Windsurf made writing code feel effortless — but the moment you wanted to ship that code, you were back to juggling registrar tabs, cloud consoles, and shell CLIs that each speak a different dialect.
So we built the thing we wanted: an agent you can talk to the same way you talk to Claude, that happens to know your DNS, your cloud, and your CI — and can actually do the work when you approve.
Why we started
The same week we shipped an indie project, three separate things went sideways: a CNAME pointed at a dead Vercel project, an MX record got silently overwritten by a registrar's "helpful" default, and a staging subdomain leaked because nobody remembered it existed. None of it was hard to fix. All of it was hard to notice. We'd been writing AI-assisted code for months, but the operational surface of our own projects was still a spreadsheet and a prayer.
DunOps started as a chat interface over our own domains. Then it started watching for drift. Then it started proposing fixes. Now it's what we wish had existed the first time we broke production at 2am.
What we're building toward
The short version: the operational layer of the vibe-coding stack.
Chat-first today
Describe intent in plain language — inspect records, deploy apps, wire domains — without opening five consoles.
Autonomous drift watch
Background agents that notice when something shifts — a DNS edit, an expiring cert, an outage on a dependency.
Guardrails, not gates
Policy lives next to the agent. Writes you want automatic stay automatic; writes that scare you route through approvals.
Every provider, one surface
Cloudflare, Vercel, Azure, Route53, Render, GoDaddy — one chat, one diff, one source of truth.
Talk to us
Product questions, partnership ideas, bugs, feature requests — all of it lands in the same inbox and we read every one. If you're a dev who'd use this, we especially want to hear from you.