How should buyers use the vendor directory?
Start with the infrastructure layer that constrains the decision: capacity, power, cooling, fiber, interconnection, finance, or development. Then use the provider profiles and source-backed buyer guides to compare fit, caveats, and the questions to verify before procurement.
| Vendor layer | Buyer question | Next step |
|---|---|---|
| Capacity platforms | Where can AI workloads be deployed with enough power and density? | Review capacity, colocation, and provider profiles. |
| Fiber and interconnection | Which providers connect campuses, clouds, carriers, and exchanges? | Review fiber, interconnection, and profile pages. |
| Cooling vendors | Which cooling architecture fits the rack density and facility design? | Review liquid cooling provider comparisons and cooling profiles. |
| Power and finance | What cost, utility, and procurement constraints shape the shortlist? | Review power, cost planning, and onsite power profiles. |
What belongs in a provider profile?
A useful provider profile should explain the buyer problem the company helps solve, the infrastructure layer it operates in, public evidence for capability claims, buyer-fit caveats, and related source records. Profile coverage should not imply a universal ranking or current availability without a sourced, date-aware claim.
Which provider profiles are available?
The directory now includes profile pages for recurring infrastructure entities across colocation, GPU cloud, cooling, power, microgrids, interconnection, and advisory work. Use those pages as a first-pass diligence layer, then verify facility, product, power, cooling, network, pricing, and delivery details directly with the provider.