Use your own domain

Every server answers at its own address on sokie.cloud, like majestic-lobster-123.sokie.cloud. On Pro and Scale it can also answer at a domain of yours. There are two ways, and they work together:

• A workspace domain, like mcp.acme.com. You verify it once, and every server in the workspace gets a name under it, like stripe-billing.mcp.acme.com. Servers you make later get theirs as they're made.
• An exact domain for one server, like billing.acme.com, from that server's Settings tab.

Sokie gets the certificate for each name and renews it. The sokie.cloud address keeps answering either way, so clients set up with it never break. Custom domains are for production only: previews stay on sokie.cloud.

Use a subdomain

A custom domain must be a subdomain of a domain you control, like mcp.acme.com, never the bare acme.com: a bare domain can't hold the CNAME record that points it here. For a workspace domain, pick a subdomain just for Sokie, since every name under it will point here.

Verify a workspace domain

1. In Settings, under Workspace, open Domains, type the domain and choose Add domain. Or run sokie domains add mcp.acme.com --wait.
2. At your DNS provider, add the two records Sokie shows:

The TXT proves the domain is yours. The CNAME sends every name under it to Sokie. Sokie looks every minute and shows each record as found. Most providers take a few minutes, some up to an hour. Once both are found the domain is verified, and each server's name gets its certificate, usually within two minutes.

Keep both records. The certificates renew through the CNAME.

A server's name starts as its own name, made into a hostname: a server called "Stripe billing" answers at stripe-billing.mcp.acme.com. Two servers with one name get -2, -3 and so on. To rename one, open its Settings tab and change the name in the Address card. Renaming moves the address: clients on the old name stop reaching it.

Give a server an exact domain

On the server's Settings tab, in the Address card, type the domain and choose Add domain. Or run sokie domains add billing.acme.com --server <slug> --wait. Then add its two records:

The TXT stops anyone else from claiming your domain in Sokie before you do: only the claim that matches it is served. A name under your verified workspace domain needs no TXT, since the domain is already proven.

Once it's live, the exact domain is the address Sokie shows for the server, in its header, the Connect panel, sokie commands and webhooks. Turn off Show it as the server's address to keep it answering without showing it.

Add the records at your DNS provider

Sokie looks up who runs your domain's DNS and says so above the records, like "Your DNS is at Cloudflare", with a link to its DNS settings and what its form wants. Most providers add your domain to a record's name for you, so you type _sokie.mcp rather than _sokie.mcp.acme.com; the steps show the exact names to type. sokie domains add prints the same.

At some providers you can add both records in one step. Where Sokie has set this up with yours, the page shows Add records at and your provider's name: your provider shows the two records for you to approve, then sends you back to Sokie, which checks them at once. Everywhere else, add the records by hand.

At Cloudflare

If your DNS is on Cloudflare, set the records to DNS only (the grey cloud). A proxied record hides the CNAME, and the name never reaches Sokie.

When something's wrong

The Address card and the Domains page say what Sokie found:

• Waiting for DNS: the records aren't there yet. Check their names and values; some providers add the domain to a name for you, so _sokie.mcp.acme.com is typed as _sokie.mcp.
• Points elsewhere: the name has another record, like an A record for an old service. Replace it with the CNAME, or pick another subdomain.
• Getting a certificate: the record is right, and the certificate is on its way. A CAA record that doesn't allow Let's Encrypt or Google Trust Services holds it up.

Sokie looks every minute for the first hour, then every fifteen minutes, and stops after three days. Check now looks at once and starts again. A live name is looked at once a day, and a webhook can tell you when one goes live or stops working.

Plans

Custom domains come with Pro and Scale. On another plan the names stop answering but stay listed, and they come back when the workspace returns to Pro or Scale. A workspace has one workspace domain, and a server one exact domain.

Remove a domain

Choose Remove on the Domains page or the Address card, or run sokie domains remove <domain> --yes. The names stop answering at once, and the server's sokie.cloud address keeps working. You can then delete the DNS records.