Point your name at your own hosting

By default a claimed name serves a small profile card built from your GitHub account. Pointing it at your own site is a two-file edit and a pull request, no DNS panel involved.

The flow

  1. Fork the registry.
  2. Edit domains/<name>.json, adding a CNAME, A, or TXT record under records.
  3. Open a pull request. CI validates the change against the record schema; once it is green and merged, a workflow pushes the record to DNS automatically.

One file per pull request, and the path must match domains/<name>.json. Only the recorded owner may edit their own record.

Vercel

{
  "name": "you",
  "owner": { "github": "you" },
  "claimedAt": "2026-01-01T00:00:00.000Z",
  "records": { "CNAME": "cname.vercel-dns.com" }
}

Add you.runs-on.dev as a custom domain on the Vercel project (Project → Settings → Domains). It shows this exact CNAME target.

GitHub Pages

{
  "name": "you",
  "owner": { "github": "you" },
  "claimedAt": "2026-01-01T00:00:00.000Z",
  "records": { "CNAME": "you.github.io" }
}

Replace you with your GitHub username or org. You also need a CNAME file in the Pages repo itself containing you.runs-on.dev, GitHub's usual custom-domain setup.

Netlify

{
  "name": "you",
  "owner": { "github": "you" },
  "claimedAt": "2026-01-01T00:00:00.000Z",
  "records": { "CNAME": "apex-loadbalancer.netlify.com" }
}

Add you.runs-on.dev as a custom domain in the Netlify site's settings so it can issue a certificate for it.

Cloudflare Pages

{
  "name": "you",
  "owner": { "github": "you" },
  "claimedAt": "2026-01-01T00:00:00.000Z",
  "records": { "CNAME": "you-project.pages.dev" }
}

Replace you-project with your Pages project's own *.pages.dev subdomain, then add you.runs-on.dev as a custom domain in the Pages project's settings.

A and TXT records

A CNAME can't sit next to an A or TXT record at the same name, that's a DNS constraint, not a rule this registry invented. If you need both a routing target and a verification string (a domain-verification TXT, for example), use A with your host's IP addresses instead of CNAME, since A and TXT can coexist.

"records": {
  "A": ["203.0.113.10"],
  "TXT": ["verification-string-here"]
}

Full reference

Field-by-field detail, validation rules, and how a merged record actually reaches DNS: docs/records.md in the registry.