Anyone holding more than a few dozen domains runs the same scattered setup. Registrar dashboards in one tab, DNS at Cloudflare in another, a spreadsheet for renewal dates and acquisition costs, a marketplace account for asking prices, and a mental note about which names have a live site. Each piece works. Together they don’t add up to a system.
DNOS.org reads as Domain Name Operating System, and that expansion describes the missing product almost word for word.
One Domain, One Object
The idea is a self-hosted control plane that treats every domain as a single record. Registrar data, nameservers, DNS records, SSL status, redirects, email routing, deployment target, renewal date, purchase cost, asking price and site status all live in one place. Once the data sits together, the hard questions get easy. Which names renew next month and still point at a parking page? Which sites lost their certificate? Which redirects chain through three hops before they land?
The real leap is making it programmable. A command line with dnos status, dnos audit, dnos deploy, dnos redirect and dnos dns diff turns portfolio upkeep into something scriptable and repeatable. Infrastructure teams got this years ago with Terraform. Domain owners are still clicking through web panels.
It doesn’t need universal integration on day one. Cloudflare plus one registrar covers a large share of serious portfolios, and every connector after that widens the market.
Who Buys This Name
The audience is wider than it looks. Domain investors, agencies running client sites, SaaS companies with dozens of brand and country domains, and registrars that want a power-user product all live with this problem every week. The operating system metaphor also scales well: start with portfolio management, then grow into a platform with plugins and an API.
Four letters, and a .org suited to an open-source core. Once someone hears the expansion, the acronym explains itself.