Skip to content

About

Grab your own cool'runs-on.dev' subdomain to use for free forever.

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

 
 

Repository files navigation

runs-on.dev

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

names claimed tests license: MIT


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.

{
  "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/<name>.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, edit its record and open a pull request:

  1. Fork this repo.
  2. Edit domains/<name>.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.
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.

Nine hosting providers, a URL redirect, email forwarding, a Bluesky handle, and Discord verification, each with the exact record to copy, are in docs/guides.md. The same walkthroughs render on the site at /docs/guides/<provider> with more detail per provider; the markdown file is the compact version for reading here.

Once a name serves your own site, docs/seo.md covers what changes when that site lives on a subdomain: robots.txt and sitemaps are per host rather than per domain, redirect names cannot rank, and a name needs its own Search Console property.

Two worked examples

Vercel, the shortest path from claim to a live custom domain:

"records": { "CNAME": "cname.vercel-dns.com" }

Add you.runs-on.dev as a custom domain on the Vercel project; it shows you this same CNAME target.

A Bluesky handle, which needs no hosting at all, just a subdomain entry:

"subdomains": {
  "_atproto": { "TXT": ["did=did:plc:abc123"] }
}

Full record reference, the subdomains grammar, and why CNAME can't coexist with anything else: docs/records.md.

How it works

A single wildcard *.runs-on.dev DNS record points every possible subdomain at one Vercel project, so an unclaimed or record-less name still resolves with a valid HTTPS certificate and gets served the profile-card page. Claiming a name is therefore a git commit, not a DNS write. Pointing a name at your own hosting merges a record into domains/<name>.json, and a GitHub Actions workflow pushes that exact record to Vercel's DNS API on merge, which then takes priority over the wildcard for that one name. More detail, including the two write paths and the token split, in docs/architecture.md.

The rules

Everything CI checks on a domains/** pull request, so you can verify a PR yourself before opening it:

  • One file per pull request.
  • The path must match domains/<name>.json, matching ^domains/([a-z0-9-]+)\.json$.
  • Renaming a record is refused outright. Claim a new name instead.
  • owner and claimedAt are immutable once set; only the recorded owner may edit or remove a record.
  • New names are claimed on the site, never by pull request; that's the only path that checks account age, public-repo count, and the one-name-per-account limit.
  • An owner may delete their own record by pull request; a maintainer can do the same under POLICY.md.

See lib/pr.js for the implementation CI actually runs, and docs/contributing.md for the full breakdown of what it checks.

Self-hosting

This is an open registry, not a hosted product with a private backend. Running your own copy under a domain you own means:

  • Fork this repo and rename it; REGISTRY_REPO in .env.example points at wherever the fork lives.
  • Register your own domain, point a wildcard record at your deployment, and add it to Vercel (or adapt scripts/sync-dns.mjs and lib/dns.js for a different DNS provider).
  • Change ROOT in proxy.js and the hostname literals in app/page.jsx and app/sites/[name]/page.jsx from runs-on.dev to your domain.
  • Create your own GitHub OAuth app and set GITHUB_CLIENT_ID / GITHUB_CLIENT_SECRET.
  • Review data/reserved-*.json and adjust lib/eligibility.js for your own abuse tolerance.
Local development
npm install
npm run dev

The claim flow needs a signed-in GitHub session, and the session and OAuth cookies are set Secure (see app/api/auth/github/route.js and .../callback/route.js). A Secure cookie is dropped by the browser over plain HTTP, so the GitHub sign-in flow cannot be exercised on http://localhost. This is correct for production: runs-on.dev is on the HSTS preload list, so it's always HTTPS there, and a cookie that only ever travels over HTTPS shouldn't get a Secure-free code path just for local convenience.

To exercise sign-in locally, serve the app over HTTPS with a locally-trusted certificate, mkcert being the simplest way:

mkcert -install
mkcert localhost

Then run next dev behind a TLS-terminating proxy pointed at it, and set APP_ORIGIN to the https:// URL you're serving from so the OAuth redirect URI matches. Everything that doesn't touch sign-in, name validation, schema checks, the blocklist, the record UI, works over plain http://localhost without any of this. See .env.example for every variable the app reads.

Contributing

Bug fixes, blocklist additions, and doc improvements are welcome. See docs/contributing.md for how to add to the blocklists, run the tests, and what CI checks.

npm install
npm test

License

The code in this repository is MIT licensed. The bundled profanity blocklist (data/reserved-words.json) is seeded from LDNOOBW/List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words (English list) and keeps its own CC BY 4.0 license; see data/README.md.

Credits

The idea of giving away free subdomains under one registered domain isn't new; credit to is-a.dev for the prior art, and to js.org and eu.org for more of it.


Operated by Advance Labs, which registered runs-on.dev and is the party responsible for what runs under it. See POLICY.md.

About

Grab your own cool'runs-on.dev' subdomain to use for free forever.

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages