.cloud Domain Names
.cloud domain names, where services live
Here is an ending that describes a delivery model. A visitor reading yourproduct.cloud knows the thing is hosted, subscribed to, always running; for a SaaS or platform brand, that address is the elevator pitch. Register from $10.99/yr, and the renewal figure appears on screen before payment.
.cloud
Extension
Shown
Renewal before checkout
Live
Availability results
Free
DNS management
The Extension
Why .cloud?
When the 2012 new-gTLD round put .cloud into the root, its audience showed up almost immediately: SaaS products, hosting platforms, infrastructure tools, plus the status pages and consoles orbiting all of those. Inside an address the word earns its place. Hosted-and-managed is what the industry means by 'cloud', so the ending signals a delivery model in the way .store signals a checkout. Point a console at app.yourname.cloud and it reads as precisely what it is.
All the way down it behaves as a standard gTLD: registration open worldwide, auth-code transfers, the usual post-registration locks, WHOIS privacy included free with us. Sell uptime and your registrar disciplines turn into product disciplines. Keep the name registered to the company itself, automate renewals years ahead of when you need them, and treat DNS as the production dependency it obviously is. Before checkout you see renewal and registration together, as on every ending across this estate.
Good Fit
.cloud works best for
- SaaS products and hosted platforms
- Infrastructure, DevOps and monitoring tools
- Product consoles, docs and status pages
- Cloud consultancies and managed-service brands
With Every Name
Included with every domain
The delivery model in the name
Read the address and the ending has already said 'hosted service', before a single pixel of the page renders. Positioning like that is one job the strapline can drop.
DNS treated as production
Edit a zone right down to the individual record, hold delegation yourself, pull an export whenever you feel like it. Run a platform and the domain is uptime.
Registrar honesty as standard
Premium strings are flagged, renewal is quoted next to registration, and a transfer code follows any request. House rules here.
Common Questions
Questions about .cloud
Is .cloud only for cloud-industry companies?
Most naturally there, yes, but nothing restricts it and the register is open to anyone. Ask whether 'cloud' says something true about what you actually sell. On a hosted product the word adds information. Stapled to an unrelated trade it merely puzzles people. Read the entire address out to your best customer and see whether it survives the journey.
Should the SaaS itself sit on the .cloud or the .com?
A common pattern runs the pair together: company and marketing under the .com, the product console or the app itself under the .cloud, each ending doing the job it names. Nothing wrong with a single-name setup either. Pick one canonical address, redirect its sibling permanently, and hold that line so search standing accumulates in one place.
Which registrar settings matter most for a platform's own domain?
Whichever ones protect uptime: the company named on the registration with years of term bought up front, auto-renew pointed at a card somebody actually tracks, registry locks switched on, a contact mailbox that gets read. Let a platform's domain lapse and the console, the API and the status page go dark together, all three. Everything gets armed at registration.
Keep Browsing
Other endings worth a look
Registration and renewal figures for every ending we carry are on the price list.
Read the whole domain price list or transfer a name you already hold.
Put the .cloud on the register before someone else does.
Search runs live against the registry, WHOIS privacy costs nothing where the registry allows it, and the renewal figure is shown before you pay.
Search .cloud Names