The network-layer complement to the defense AI platform position.
A .network coordinate for defense AI platform builders — conveying the interconnected, multi-node architecture that modern defense systems require.
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 Defense resolution surface.
7 of 7 primitives held for defense — 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 Defense row holds 4 matched pairs across the seven primitives.
See the full Defense 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
Defense · Vertical-Specific · 2 compound moats. Architectural surface: Platform.
Layer position: Cross-cutting
Why this is canonical
The .network TLD adds a specific signal: this is not a single-tenant platform but a networked defense AI infrastructure — appropriate for multi-domain, multi-organization, or cross-classification-boundary deployments. Where defenseplatform.ai names the agent-era platform layer, defenseplatform.network names the infrastructure's networked character — resonant with doctrines like JADC2 that treat defense AI as inherently distributed.
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.