The network-TLD coordinate for the clinical platform — connecting providers, systems, and agents.
The .network complement to the clinical platform position — a natural fit for a clinical AI platform framed as a provider network, interoperability hub, or multi-organization coordination layer.
Matched pair · recommended together
Recommended: sold as a pair — the matched .ai + .network TLDs cover one coordinate. Each name can be acquired on its own; the set inquiry is the path to the whole position. Click a name to view its lander.
The set
Part of the Healthcare resolution surface.
7 of 7 primitives held for healthcare — a complete resolution surface. One operator holds the row agentic systems resolve to; every competitor who arrives later works with what is left.
Held as a matched pair — the Healthcare row holds 16 matched pairs across the seven primitives.
See the full Healthcare opportunity →Coordinated sets this position belongs to — the coverage it extends. Counts are the live cluster size in the graph.
Primary home
Also appears in
Surfaces this position also reads to — addressability, not exclusivity. A name applicable to a category is not a claim to own it; these are the buyer pools the coordinate speaks to, beyond the clusters it is held in.
Architectural context
Healthcare · Vertical-Specific · 2 compound moats. Architectural surface: Platform.
Layer position: Cross-cutting
Why this is canonical
The .network TLD shifts the framing from a software platform to a connected network — providers, health systems, payers, and clinical AI services connected through a common platform. 'Clinical platform network' names the infrastructure enabling federated clinical AI across organizations. This coordinate is particularly suited to multi-organization, interoperability-first, or network-model clinical platform businesses.
Where it fits
A few directions this coordinate opens —
Illustrative, not exhaustive — held as a transferable canonical position, open to the buyer's own use.