What .cloud is actually good for
The useful test for .cloud is whether the thing behind the name is a service rather than a company. A hosting brand, a storage product, a control panel or a regional API endpoint all read naturally under it, because the word describes the delivery model rather than the industry. That is a narrower claim than the marketing usually makes, and it is the one worth paying for.
Where it works less well is as a general business address. A buyer who has never seen your brand does not guess a .cloud, and for a Swiss audience the guess is .ch. Treated as a second name pointed at a product, .cloud costs little and removes an awkward subdomain. Treated as a replacement for a country extension, it quietly makes you harder to find.
Who runs the registry, and what its rules commit you to
IANA records the sponsoring organisation as ARUBA PEC S.p.A. of Ponte San Pietro in Italy, a subsidiary of the Aruba hosting group, with technical registry operations contracted to Tucows. It is not, as is often written, a generic American registry. Because the operator is Italian, the registry's privacy and WHOIS policy is framed around Italian law, and its published registration policy names Italian courts and authorities as the route by which registrant data can be disclosed.
Two clauses in that policy matter to a buyer. The first is the term and renewal structure: one to ten years, with the registry stating that expiry notices are the registrar's job, not its own. The second is pricing structure: the policy reserves the right to price premium names differently and to renew them above the price charged at registration. We are an Openprovider reseller rather than the registry, so we cannot waive either rule, which is precisely why registration, renewal, transfer and restore are all shown to you before you commit.
