zordhalo/runs-on.dev

Free subdomains for developers. Claim yourname.runs-on.dev in seconds,
then point it wherever you like.
Claim a name
 · 
Quickstart
 · 
Guides
 · 
Records
 · 
Policy
Claiming a name writes one file to this repository. That file is the record. It is the only
thing that makes the name resolve, and you can read it without asking anyone.
json
"name": "yourname",
"owner": { "github": "yourname" },
"claimedAt": "2026-01-01T00:00:00.000Z",
"records": {}
There is no hidden database. The registry is this directory, the history is the git log, and
the rules are in lib/.
## Why this exists
A real top-level domain means an ICANN application. The 2026 round's
evaluation fee alone is $227,000, before you've built or run a registry to
back it. That's not a plausible way to get a custom-looking address for a
side project.
runs-on.dev gets the same feeling: a distinctive ending instead of
vercel.app or github.io, for the price of one domain, about $10 a
year, by giving away subdomains under it. This is a subdomain registry,
not a TLD. Every name you claim lives under runs-on.dev, which Advance
Labs registered and is responsible for. Saying that plainly, instead of
dressing it up as something bigger, is the whole basis for trusting it.
There's prior art doing exactly this: is-a.dev,
js.org, eu.org.
## Claim a name
Go to runs-on.dev, sign in with GitHub, and type
the name you want. If it's available, claiming it writes a record to
domains/ .json in this repo, as shown above, and the name is live
within seconds. One name per GitHub account. See
docs/claiming.md for eligibility rules, the
per-account limit, and why they exist.
## Point it at your own hosting
By default a claimed name serves a small profile card built from your
GitHub account. To point it at your own site, forward email, or a plain
redirect instead, there are two ways to change its record.
From the site. Sign in and open
runs-on.dev/manage. Pick a record type, fill
it in, and save. That writes a commit to domains/ .json in this
repository, exactly as a merged pull request would, and DNS follows within
seconds. The form offers the record types in the combinations DNS actually
permits, so it cannot build a record the schema would reject.
By pull request. Still supported, and the right choice when you want the
change reviewed before it lands:
1. Fork this repo.
2. Edit domains/ .json, adding a record under records (and
optionally subdomains, for a one-level-deep entry like atproto).
3. Open a pull request. CI validates the change against
schema/record.schema.json; once it's
green and merged, a workflow pushes the record to DNS automatically.
Both paths enforce the same rules, from the same code in
lib/edit.js: only the owner may change a record, and
owner, claimedAt, and name are immutable once set.
| Type | Shape | Coexistence |
| CNAME | a hostname string | Alone: cannot sit next to A, TXT, or MX. |
| A | 1+ IPv4 addresses | With TXT, MX. |
| TXT | 1+ strings, up to 255 chars each | With A, MX. |
| MX | 1 to 5 { priority, value } entries | With A, TXT. |
| URL | one absolute http(s):// string | Alone: cannot sit next to anything, not allowed under subdomains. |