Where .software wins and where it does not
The argument for .software is character economy plus category. Software companies almost always end up with a compromise .com, the product name with get, try, use or app bolted on, and every one of those adds friction to a name that has to be typed, dictated in a support call and printed in documentation. Moving the category to the right of the dot recovers the clean product word and keeps the meaning, which is the same trade a lot of teams already make with .io or .app.
It is a poor fit in two specific situations, and it is worth being direct about both. The first is enterprise sales, where procurement and security reviewers still treat a .com as a proxy for permanence, and a non-.com address costs you explaining time you would rather spend elsewhere. The second is developer-facing tooling, where .dev has become the convention and carries an actual technical property that .software does not. If the audience is engineers who will paste your domain into a terminal, .dev is the more natural choice.
The registry history, and why it matters
IANA delegated .software in May 2014 to United TLD Holdco, part of Rightside, and records the current sponsoring organisation as Dog Beach, LLC following a transfer completed in June 2021. Dog Beach is one of the entities Identity Digital contracts through, which is why .software sits under the same operational policies as the rest of the portfolio, an acceptable use policy, an IDN policy, a reserved names policy, but it is a different contracting entity from Binky Moon, which holds extensions such as .agency and .farm. If you are checking a registry agreement or filing a complaint, that distinction is the one that matters.
Operationally the extension behaves like any ICANN-contracted gTLD, and we register it as an approved Openprovider reseller with no extra data collection. The one thing we would flag for a software business specifically is dependency risk. A domain that appears in package registries, update endpoints, licence checks or CI configuration is infrastructure, not marketing, and losing it to an unread renewal notice is a supply-chain incident rather than a downtime incident. Put the registrant contact on a monitored team address rather than an individual's, keep the registrar lock on, and consider a longer term.