.cloud Puts Infrastructure in the Hostname: Aruba's Registry, wp.cloud's B2B Canonical, and Why Engineers Still Pick .io/.dev

Open wp.cloud. You land on Automattic's live WordPress-as-a-Service platform—partner docs, infrastructure specs, Forbes Cloud 100 press. Open tech.cloud. In mid-2026 you are more likely to hit a premium lander, a parked page, or a registry upsell than a shipped product. Same suffix, opposite evidence quality. The stub this guide replaces never made that distinction. It duplicated the same five names under "Notable Domain Sales" and "Notable Sites"—all tagged "reported sale (price undisclosed)" without a single NameBio receipt—and recycled daily-TLD AIO boilerplate claiming descriptive TLDs raise CTR because "users browsing search results can tell .cloud URLs are about cloud topics at a glance," then treating CTR as a downstream ranking signal. It also compared domain investing to "owning physical real estate." Unaudited, delete-on-sight.

The story worth telling is not "cheap cloud startup suffix." It is the dictionary word for modern infrastructure baked into the hostname—readable by procurement officers and conference attendees who do not decode .io as input/output—launched by Aruba S.p.A., one of Europe's largest hosting providers, when their own cloud product and ICANN's 2012 new gTLD round aligned. That literal category signal—not engineer in-jokes or Google HSTS preload—is what separates .cloud from .dev, .app, and .io.

Two audiences: buyers hear "cloud infrastructure," engineers hear "I/O" or "HTTPS preload"

.cloud spells cloud—the product category every SaaS buyer already budgets for. Say "acme dot cloud" on a vendor call and nobody asks what the suffix means.

.io hijacks input/output—a mnemonic CS grads decode instantly—and carries Chagos ccTLD sovereignty baggage (see .io guide). .dev and .app are Google Registry TLDs with TLD-wide HSTS preload and localhost collision history on .dev (see .dev and .app guides). .ai is Anguilla ccTLD with separate gccTLD treatment (see .ai guide).

.cloud is a standard generic TLD (gTLD)—no residency rules, no forced HTTPS at the public-suffix layer, no country-code sunset clock. The trade: mainstream infrastructure legibility versus developer-street-cred on .io/.dev and TLS-as-launch-gate rigidity on Google suffixes.

Who runs .cloud in 2026—and why the operator name matters

Registry operator (2026): Aruba PEC S.p.A., a wholly owned subsidiary of Aruba S.p.A. (Arezzo, Italy), per IANA delegation record—last updated 18 December 2025. Retail site: get.cloud. WHOIS/RDAP: whois.nic.cloud, rdap.registry.cloud.

Corporate lineage: ICANN signed the original Registry Agreement with Aruba S.p.A. on 16 April 2015 (ICANN .cloud agreement). An Assignment and Assumption Agreement transferred operation to Aruba PEC S.p.A. on 3 August 2015 (ICANN assignment list). The zone was delegated to the DNS root on 26 June 2015 (IANA report). Do not conflate PEC (current operator entity) with "some random Italian registrar"—Aruba is a hosting and cloud infrastructure company that applied for .cloud when launching its own cloud stack, not a pure portfolio investor like Radix or Google.

Backend registry services: IANA lists Tucows.com, Co. as technical contact with nameservers ns01.trs-dns.com / ns01.trs-dns.net—the Tucows Registry Services stack. Launch-era backend was ARI Registry Services (ICANNWiki); the migration to Tucows is a backend-only change—registrant ownership and DNS stayed live through transition windows, same pattern as Radix→Tucows on .tech.

Contention economics: Unlike .app's $25M ICANN last-resort auction, .cloud cleared contention through a private auction in November 2014 that left Aruba as the sole remaining applicant (ICANNWiki private auction note). No public hammer price—proceeds stayed among losing bidders, not ICANN. That lower acquisition cost shows up in moderate renewal pricing, not premium-tier aggression on every dictionary word.

Launch calendar—and the Pioneer program

| Phase | Dates | Notes | |-------|-------|-------| | DNS delegation | 26 June 2015 | Root zone entry | | Pioneer program | 24 Sep 2015 – 14 Jan 2016 | Early adopters featured on worldof.cloud | | Sunrise (TMCH) | 16 Nov 2015 – 15 Jan 2016 | ICANN sunrise record | | Landrush | 25 Jan – 5 Feb 2016 | Between sunrise and GA | | General Availability | 16 February 2016 | Public registration opens |

Gandi's launch pricing snapshot: Sunrise ~$162/yr, Landrush ~$62/yr, GA shelf ~$31/yr (Gandi News, November 2015). GA pricing has compressed dramatically since—see below.

Aruba's ICANN case study (April 2017) framed objectives: become the domain of choice for cloud industry professionals and a modern generic brand for non-tech adopters—without requiring registrants to operate cloud services. That open-registration posture is why food.cloud (a food-waste social enterprise) and wp.cloud (B2B hosting infrastructure) coexist on the same suffix.

Zone size: mid-tier new gTLD, not .io scale

| Metric | Source / date | Figure | |--------|---------------|--------| | Domains under management | ntldstats.com, mid-2026 | ~760,486 | | Rank among new gTLDs | Same | #23 by volume | | vs .dev | Same snapshot | ~760k .cloud vs ~832k .dev | | vs .io | .io guide | ~1.72M .io—larger, ccTLD-priced | | vs .app | .app guide | ~1.2M active .app—HTTPS-preloaded, Google-operated | | US registrant share | ntldstats.com country breakdown | ~72,656 .cloud names |

Do not confuse zone count with live-product count. A meaningful share of any new gTLD is defensive, parked, or promo-inflated. Aruba markets 100+ accredited registrars on get.cloud—go-to-market breadth, not proof every registered string hosts a product.

Pricing: promo traps and registry premium tiers

Aruba sets wholesale tiers; registrars add markup. First-year promos and renewal reality diverge.

| Tier | Typical range (USD, mid-2026) | |------|------------------------------| | Standard new registration (1 yr) | $2–$6 promo; $5–$16 shelf | | Standard renewal (1 yr) | $16–$22 (Porkbun ~$15.94; Namecheap ~$22.16 per registrar aggregators) | | Transfer | $16–$22 | | Registry premium (short/dictionary) | $100–$5,000+/yr—tier shown at EPP check | | Secondary aftermarket | Sparse vs .com/.io; NamePros tracked 6 reported .cloud sales in 2019 averaging ~$7,271—verify before citing |

Model three years at renewal, not the hero banner. A $1.99 first year can carry $16+ renewals—and premium labels like data.cloud or storage.cloud can jump to $400–$5,000+/yr without warning if the string sits in a higher tier. Always run EPP price lookup before checkout.

Verified roofs—and the brochure names to delete

Skip Mad Libs (startup.cloud, api.cloud, saas.cloud as "notable sites" without live products). These mid-2026 checks return mission-aligned surfaces on .cloud itself:

wp.cloud — Automattic's WordPress-as-a-Service infrastructure platform; canonical B2B product domain with live docs, partner case studies, and Forbes Cloud 100 recognition (wp.cloud; Automattic press, 2026). wordpress.com remains the consumer builder; wp.cloud is the hosting-company channel—exactly the infrastructure story .cloud was built for.

alchemy.cloud — Alchemy Cloud, Inc.'s AI-powered LIMS & ELN for applied science labs; primary product domain (alchemy.cloud). Featured in Aruba/Name.com marketing as a modern SaaS adopter (Name.com blog).

reporting.cloud — Text Control ReportingCloud: MS Word-compatible document generation via REST API in the cloud (reporting.cloud). Live product surface on .cloud, not a redirect stub.

food.cloud — FoodCloud, the Irish/UK social enterprise connecting surplus food to charities; primary domain on www.food.cloud (food.cloud). Cited in Aruba's ICANN case study as non-tech adoption proof.

Counterexamples—delete from "notable adopter" lists:

automation.cloud — Returns HTTP 404 in mid-2026. The old guide listed it twice as both a "sale" and a "notable site" with zero verification.

power.cloud — 301 redirect to hansencx.com/de/powercloud-de/—PowerCloud lives on a .com path, not as a canonical .cloud brand. Holding ≠ building.

artik.cloud — Samsung's Artik IoT platform is discontinued; the hostname now resolves to unrelated survey/spam redirects. A 2015 Pioneer launch does not equal a 2026 roof.

aws.amazon.com / azure.microsoft.com / cloud.google.com — Hyperscalers lead with .com subpaths, not .cloud vanity. Do not infer industry mandate from registry marketing.

Trash the old guide's lazy equivalence between "cloud company" and ".cloud mandatory." The suffix wins when non-engineers must parse infrastructure category from the URL—vendor RFPs, partner decks, B2B infrastructure products—not when your only buyer is an engineer who already prefers .io for I/O semantics or .dev for docs under forced HTTPS.

.cloud vs .app vs .dev vs .io: one table, not four guides

| Dimension | .cloud | .app | .dev | .io | |-----------|----------|--------|--------|-------| | TLD class | gTLD | gTLD (Google Registry) | gTLD (Google Registry) | ccTLD (BIOT / Chagos) | | URL semantics | "Cloud infrastructure"—plain English | "Mobile/app product" | "Developer/docs/infra" | "Input/output"—engineer code | | HTTPS policy | Optional (registrar/host) | TLD-wide HSTS preload | TLD-wide HSTS preload | Optional | | Typical buyer | B2B SaaS, hosting stacks, infra platforms | Consumer apps, PWAs | Docs portals, SDK sites, PaaS hostnames | DevTools, infra APIs, indie games | | Zone (mid-2026) | ~760k | ~1.2M active | ~832k | ~1.72M | | Renewal reality | $16–$22 standard | $16–$24 standard; Google premium tiers | $15–$22 standard | $50–$65+ climbing wholesale | | Registry operator | Aruba PEC (hosting co.) | Charleston Road / Google | Charleston Road / Google | Identity Digital / ICB | | Registry risk | Aruba portfolio economics | Google Nomulus stability | Google Nomulus + localhost history | Chagos/ISO tail risk | | Disputes | Standard UDRP | Standard UDRP | Standard UDRP | WIPO UDRP variant |

Choose .cloud when procurement, partners, and non-technical stakeholders must read "cloud" in the hostname. Choose .io when your buyer already lives on fly.io-class URLs. Choose .dev when you ship engineer docs under forced HTTPS. Choose .app when you canonicalize consumer product identity with the same preload contract.

SEO and AI search: descriptive, not a ranking cheat code

Google treats .cloud as a standard gTLD—no geographic targeting, no special ccTLD handling. John Mueller's standing guidance applies: keywords in the TLD are not a ranking signal.

The old guide's CTR chain—"descriptive clarity raises click-through → CTR is a downstream signal"—is speculative attribution without controlled studies on .cloud specifically. SERP snippets show the title and meta description, not the suffix alone. Do not buy .cloud expecting algorithmic lift from the label.

For AI surfaces (ChatGPT Search, Perplexity, Google AI Overviews): models cite pages with authority and freshness, not TLD semantics. wp.cloud appears because Automattic and WordPress are known entities, not because .cloud whispers "cloud computing" to model weights. food.cloud surfaces because FoodCloud is a documented social enterprise—not because of schema templates. No audited AIO preference layer exists for descriptive gTLDs; do not bolt on FAQ markup expecting citation dividends.

Neutral SEO playbook: canonical tags, HTTPS, Core Web Vitals, and content quality—see SEO-friendly domain names.

One routing question—not a who-should matrix

Skip symmetric columns. Ask:

Must a non-engineer instantly understand your URL carries cloud/SaaS/infrastructure meaning on an RFP cover sheet—or are you buying developer fashion where .io / .dev already win the room?

Choose .cloud when you ship B2B cloud platforms, hosting infrastructure, SaaS with infrastructure story, or partner-facing APIs where something.cloud reads cleaner than somethingcloud.com or something.io to mixed audiences, you will canonicalize public marketing on .cloud (not just defensively register), and you accept registry premium tier checks on short dictionary names. Pair with defensive .com before enterprise procurement—see Domain Hacks.

Skip .cloud when your buyer is pure engineers who already decode .io (→ .io guide), when you ship API docs under forced HTTPS (→ .dev guide), when consumer app identity with preload rigidity matters (→ .app guide), when AI product signaling beats "cloud" in plain English (→ .ai guide), when mainland China is core (exotic gTLD ICP complexity—keep .cn/.com.cn operational), or when you want the cheapest long-term renewal on a developer vanity suffix (→ .com guide).

Alternatives worth comparing:

• .io — Engineer I/O semantics; larger zone; ccTLD sovereignty stack.
• .dev — Google HSTS preload; docs/infra identity.
• .app — Consumer/mobile product surface; HTTPS-preloaded.
• .tech — Plain-English "technology" without "cloud" category lock-in.
• .digital — Broader digital-transformation semantics; Identity Digital portfolio.

FAQ

Who operates .cloud in 2026?

Aruba PEC S.p.A., subsidiary of Italian hosting company Aruba S.p.A., on Tucows backend registry services per IANA.

Do I need to run cloud services to register .cloud?

No. .cloud is an unrestricted gTLD open worldwide. Aruba's own case study highlights non-tech adopters like food.cloud.

How does .cloud compare to .io for startups?

.cloud = plain-English "cloud infrastructure" for mixed audiences. .io = engineer I/O fashion with ccTLD registry risk. Test with your actual buyer—not Twitter consensus.

Are .cloud domains expensive?

Standard renewals run $16–$22/yr at major registrars. Short and dictionary names hit registry premium tiers—always EPP-check before purchase.

Is .cloud good for SEO?

Neutral as a gTLD. Rankings follow normal quality signals—not suffix semantics.

Does UDRP apply?

Yes—standard UDRP for this gTLD.

What happened to Samsung's artik.cloud?

Artik IoT was discontinued. Do not cite 2015 Pioneer launches as 2026 adoption proof without live-DNS checks.

---

Stress-testing cloud brand architecture across suffixes? Our domain search checks .cloud, .io, .dev, and 1,000+ extensions in one pass—or read Brand Name vs Domain Name before you canonicalize on brand.cloud.