is-a-dev/register

Worth trying if you want a short, developer-flavored domain for a portfolio, blog or project page and are comfortable working through a GitHub pull request. It is not a replacement for a domain you control outright.

The problem

You want a personal site to live at something like yourname.is-a.dev rather than a long GitHub Pages or hosting-provider URL, and you do not want to buy and configure a domain just for a side project. Registering normally means a registrar, DNS panel and renewal bookkeeping. Here the request itself is a pull request: you fork the repository, follow the documentation to describe the records you want, and open the PR. After review and merge, the DNS records are published within a few minutes according to the README, and you have a subdomain pointing at your existing hosting or redirecting to it.

What's different

Registration is handled through the repository rather than a web control panel. This makes the process public and reviewable: each subdomain request is a change you can read, the maintainers can ask for corrections, and a record of who holds which name stays in version control. The trade-off is that the workflow is GitHub-shaped. You need to fork the repo, follow a documented request format and keep an eye on the PR if changes are requested, because the README says unresolved requests will be rejected.

The README is unusually direct about one failure mode: it warns that AI-generated requests "WILL always get it wrong" and will delay the domain. That is a strong claim from the project, but it signals that exact file format and record syntax matter. A visual walkthrough by a third party is linked for people who find the written documentation sparse. The service is backed by Cloudflare's Project Alexandria program for DNS management, but the subdomain is still delegated from the is-a.dev zone rather than being yours to move elsewhere.

An early commenter on Hacker News raised a point worth keeping in mind: visitors may not realize that traffic to a subdomain can be hijacked by whoever controls the parent domain. That comment dates from 2020, so it describes the trust model rather than a specific current incident. The practical read is that this is a convenient public address, not a security boundary.

Who should try it

Good fit: a developer with a portfolio, demo or small project page hosted on GitHub Pages or any existing host, who wants a readable URL and does not mind the pull-request process. It also suits people who already use GitHub daily and can review their own JSON-style record request before submitting.

Poor fit: a business or anyone who needs to guarantee the address persists, because the name lives under a domain you do not own and the terms are set by the service. It is also a poor fit if you need the request handled quickly and privately, since each request is public and reviewed. If you simply want a free host without a custom-looking address, an existing provider URL may be less work.

Requirements and limitations

The main requirement is a GitHub account and willingness to fork, edit and submit a pull request in the documented format. The README points to separate documentation for the exact request instructions; the visual guide is a third-party blog post, not official docs. Once merged, records are said to publish within minutes, but that depends on the request being correct and merged.

Ongoing upkeep matters more than setup. The subdomain is not a registered domain you can transfer or renew yourself, so its long-term availability is tied to the service and its terms. If you need to change DNS later, you go through another PR. Abuse is handled through a dedicated issue template, which suggests the maintainers police the namespace, but it also means your use is subject to review and removal.

HotRepo's take

The only dated HotRepo observation is a single daily-board appearance on 2026-10-25 at 11,632 stars and +30 that day; that is a snapshot, not a trend, and interest cannot yet be judged as rising or fading. A 2020 Hacker News thread drew 2 points and 2 comments, which indicates discussion volume only. The repository itself dates to October 2020, so this is an established service rather than a new experiment.

Adoption judgement: try it for a personal page where a friendly URL is a nice-to-have, and read the record-format documentation carefully before opening the PR. Before relying on it, confirm the current terms and whether you are comfortable that the subdomain stays under the service's control.