Register a .run domain

The most natural home for .run is a tool that does something on command — a pipeline that builds and deploys code, a scheduler that fires a job at midnight, a workflow engine that chains a series of steps together. For this category the word is not a stretch; it is a literal description of the product's job. pipeline.run, build.brand.run or a standalone brand.run tells a developer scanning a list of tools exactly what to expect before they open the docs. That clarity matters in a crowded devtools market where engineers judge a product in seconds from its name and its landing page, and a domain that states its function plainly saves everyone a beat of confusion. It also gives the product room to grow sub-brands sensibly: docs.brand.run, status.brand.run and api.brand.run all read consistently, because the root word already sets the right tone of something active and operational rather than a passive brochure site.

Because .run is genuine English vocabulary, it works just as well outside software for anyone in the business of actual running. A city marathon, a local parkrun-style weekend group, a running-shoe retailer, a coached training-plan app or a physiotherapy clinic specialising in runners can all use the extension exactly as written, with no pun required and no explanation needed. citymarathon.run or coach.run reads immediately and warmly to the audience it is built for, and it has the added benefit of standing out visually against the sea of .com addresses in the same space. Race organisers in particular benefit from a domain that doubles as a small piece of branding on flyers, bibs and sponsor decks — the extension itself becomes part of the event's identity rather than just a technical necessity. For this audience .run offers something rarer than cleverness: a domain ending that simply says, correctly, what the whole organisation is about.

A .run ending carries no built-in ranking boost from search engines — Google treats gTLDs like .run the same way it treats .com for ranking purposes, and no extension gets extra credit simply for its letters. What actually moves the needle is the usual set of fundamentals: fast pages, solid content, clean structure and real backlinks, all of which matter regardless of what comes after the dot. Where .run does help is in the same soft, human ways every well-chosen domain helps — a short, real-word name is easier to remember, easier to say over a call, and easier to type correctly than a long or hyphenated alternative, and all of that indirectly supports click-through and repeat visits.

The branding upside is sharper than the SEO one. Because "run" is a common, recognisable verb, a .run domain tends to look intentional rather than accidental — visitors are unlikely to mistype it or misread it as a typo of something else, a real risk with more exotic new gTLDs. For a developer tool or automation product, the word choice does a small amount of positioning work on its own, hinting at speed and action before a visitor reads a single line of copy. As with any gTLD, it is worth adding the domain in Google Search Console and submitting a sitemap so indexing starts promptly, but there is no special configuration or workaround needed beyond that.

Against .dev, the difference is emphasis. .dev is Google Registry's ending for developer identity broadly — personal sites, portfolios, documentation, tools aimed squarely at other developers — and it requires HTTPS by default. .run is narrower and more literal: it says the product executes or automates something, which is a stronger fit for a pipeline, scheduler or CI tool specifically than the general "I am a developer" signal of .dev. If your product's whole point is that it runs a process, .run states that more precisely; if you want a general developer-facing identity, .dev is the broader choice.

Against .app, both are Google Registry endings with built-in HTTPS enforcement and both suit software products, but .app leans toward consumer-facing applications — something a non-technical user opens and taps — while .run leans toward backend, automation and process-oriented tools. Against .com, the trade-off is the familiar one: .com remains the default a mainstream audience assumes, and it is worth registering defensively even if you lead with .run, but for a technical product aimed at developers and technical buyers, a short, meaningful .run domain often does more descriptive work than a long or already-taken .com name would.