runs-at.devClaim yours

Quickstart

Claim a name and get it working

Start to finish, no other page required.

1. Sign in

Go to runs-at.dev and click Sign in with GitHub. This starts an OAuth flow and sets a signed session cookie, nothing more.

2. Pick a name

Type a name into the field on the home page. Availability is checked as you type. A name is 2 to 32 characters, lowercase letters, numbers, and internal hyphens only, never a leading or trailing hyphen.

Claiming also requires your GitHub account to be at least 30 days old with at least one public repository, and one name per account. Both are checked at claim time, not just in the form.

3. Claim it

Click Claim it. This writes domains/<name>.json straight to the public registry, no pull request needed for the claim itself. The write only succeeds if the file does not already exist, so two people racing for the same name never both win.

domains/you.json

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

you.runs-at.dev resolves immediately after this, over HTTPS, serving a profile card built from your GitHub account. There is nothing left to provision, since a wildcard DNS record already points every name at the app.

4. Point it somewhere

The profile card is fine to leave as is. To send the name somewhere else, sign in and open runs-at.dev/manage, pick a record type, fill it in, and save. That commits to domains/<name>.json the same way a merged pull request would, and DNS follows within seconds.

The shortest thing to point at needs no hosting at all: a URL record, which the app itself redirects, with no DNS to wait on.

domains/you.json

"records": { "URL": "https://github.com/you" }

The form only offers record types in the combinations DNS permits, so it cannot build a record the schema would reject, and it edits subdomains entries too. You can still do all of this by pull request instead: fork the registry, edit the file, open a pull request, and CI validates the same rules the form does.

Want it pointed at your own site instead? Same idea, a different record. See the guides for your host, or the full record reference for every field and rule.