Contact

AI-First Hosting: Let Your AI Run Your Domains, DNS, SSL and Servers on NameOcean

A glowing AI assistant connected to a domain, DNS records, a certificate lock, a mail envelope and a server

AI assistants have become very good at writing code. Ask Claude or ChatGPT for a landing page or a small web app and you get something that works in minutes. Then comes the part nobody enjoys: buying a domain, copying DNS records from one tab into another, waiting for a certificate, setting up an email address, finding a server and getting the code onto it. The AI wrote the app, but it could not touch the infrastructure, so you did that part by hand.

NameOcean is the domain registrar and hosting platform we run at Yuix Networks, and we rebuilt it around a simple idea: everything you can do in the dashboard, your code and your AI should be able to do too. We call it AI-first hosting and domains.

Say what you want, your AI does the setup

Once your AI assistant is connected to your NameOcean account, a conversation like this is all it takes:

You: Is myshop.ai available? How much is it for two years?

AI: Yes, myshop.ai is available. Here is the price for two years. You can register it on nameocean.net, and I'll set it up once it's yours.

You: Point myshop.ai to my server, turn on SSL and forward hello@ to my Gmail.

AI: Done: an A record for myshop.ai and www, a free wildcard SSL certificate, and hello@myshop.ai forwards to your Gmail. Your Gmail gets a confirmation email first.

The AI shows you what it is going to change, then makes the change. No DNS records copied by hand, and no guessing which of the five tabs you left open has the right value.

Three ways in, one set of rules

The REST API, the command line tool and the MCP server run the same code, with the same permissions and the same activity log. You pick whichever fits.

MCP, for your AI. Add one URL to ChatGPT, Claude, Claude Code, Cursor, VS Code or OpenCode. You sign in in the browser; there is no key to paste. In Claude Code it is one line:

claude mcp add --transport http nameocean https://nameocean.net/mcp

The CLI, for your terminal. One binary for macOS, Linux and Windows. Every command can print JSON, which makes it just as useful for scripts and coding agents as for people:

curl -fsSL https://nameocean.net/install.sh | sh
nameocean login
nameocean dns add kahvebot.com A @ 203.0.113.10
nameocean ssl issue kahvebot.com --wait

The REST API, for your code. JSON in, JSON out, scoped keys, idempotent retries, webhooks and an OpenAPI 3.1 spec:

curl -X POST https://nameocean.net/api/v1/dns/kahvebot.com/records \
  -H "Authorization: Bearer $NAMEOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type": "A", "hostname": "@", "ip": "203.0.113.10"}'

There is also an llms.txt that describes the whole API in a form a language model can read in one go, so even an assistant without MCP can figure out how to use it.

Everything a project needs, from one account

  • Domains. Search, register, renew and transfer, with WHOIS privacy included.
  • Free DNS. Our own nameservers and every record type. With DNS as code, the whole zone is a single YAML or JSON file: you or your AI change the file, preview exactly which records would be created, changed and deleted, and apply it in one transaction.
  • Free SSL. Wildcard Let's Encrypt certificates that renew themselves.
  • App servers. Deploy with git push. Logs, environment variables and free nightly backups, all reachable from the API. Bind a domain to a server and NameOcean adds the DNS records, issues the certificate and sets up HTTPS for you.
  • Email. Mailboxes on your domain, free forwarding, inbound email delivered to your app as a webhook, and an API for sending from your app.
  • Webhooks. Signed events for domains, DNS and SSL, with retries and a delivery log.

Put together, "build me a small app and put it online at myshop.ai" stops being a list of chores and becomes one conversation: the AI writes the code, pushes it to your server, binds the domain, and the site is live over HTTPS.

Your AI works for you, not on its own

Handing infrastructure to an AI only makes sense if it cannot do anything you did not agree to. That is the part we spent the most time on:

  • Your AI cannot spend your money. It can check domain prices, but registering and renewing are done by you. The MCP server has no tool that registers, renews or pays. A paid server takes two calls: the first returns the price for the AI to show you, and the second runs only with your yes.
  • Permissions are yours to set. Every key and every connected app has only the access you give it: read-only, DNS only, or everything.
  • Dangerous tools are labelled. Tools that delete, stop or overwrite are marked as destructive, so AI clients that confirm such actions ask you first.
  • Secrets never reach the model. Mailbox passwords and environment variable values stay out of the conversation; you read them in the dashboard.
  • Everything is logged. Every change appears in the activity log, with the app or key that made it. You can disconnect an app at any time, and API keys and app connections require two-step login.

Try it

Start with a domain, or bring one you already have: free DNS, SSL and WHOIS privacy come with every domain, and everything is scriptable from day one. Then connect your AI and ask it to do the rest.

nameocean.net/ai-domains