United States · 346 unclaimed supplier records · Reviewed 28 September 2026

Build the US evidence path before the supplier list.

A neutral buyer framework for turning location, load, utilities, connectivity, permitting, safety and delivery needs into a comparable United States supplier research set.

Browse US suppliers

Project basis

Start with the operating case—not company names

A national search becomes useful only after the project has a place, load, resource and delivery basis. Freeze what is known, label what is assumed and give every open condition an owner and decision date before comparing providers.

Input 1

Operating mandate

Define the IT load, availability outcome, growth envelope, operating horizon and decision dates. Separate a screening assumption from a committed requirement.
Input 2

Location and authority map

Name the site, land position, utility territories, permitting authorities, emergency services and every state, local, Tribal or federal interface that needs confirmation.
Input 3

Resource envelope

Record the requested electrical capacity and energisation profile, cooling and water basis, backup-power concept, connectivity outcome, land take, logistics and workforce demand.
Input 4

Delivery and evidence model

Set package boundaries, accountable designers, procurement route, acceptance authority, operations handover and the dated evidence that moves each decision gate.

Official screening

Use each federal source for the question it can answer

Hazards and community resilience

Use FEMA Hazard Explorer and RAPT to structure an initial location screen, then commission the current site-specific studies required by the owner, lender, insurer and relevant authorities.

Power, cooling and efficiency

Use DOE's data-centre design guide to test IT conditions, air management, cooling, electrical systems, heat recovery and metrics. Convert the chosen operating basis into package requirements and acceptance evidence.

Water and environmental route

Identify the applicable water, wastewater, stormwater, air and land routes with the responsible state, local, Tribal and federal authorities. EPA resources help locate the evidence; they do not issue one national data-centre approval.

Backup and on-site generation

Define normal, emergency and temporary operating cases, fuel and run-hour assumptions, emissions sources, monitoring and the permitting authority. EPA notes that state and local agencies issue most data-centre air permits.

Connectivity and route diversity

Use the FCC map only as a mass-market availability screen. Ask carriers for serviceability, capacity, demarcations, physical routes, shared infrastructure, construction scope, delivery dates and acceptance results.

Workforce and supplier identity

Allocate site-safety duties between hosts, contractors and staffing agencies. Use SAM.gov only when federal-award status is relevant, and never treat an identifier, registration or directory listing as technical qualification.

Directory path

Search the US market by package and project stage

The counts below reflect current unclaimed editorial records whose published coverage includes the United States. They are not market size, approval, capacity or availability measures. Open a filtered research set, then verify every candidate against the same requirement and evidence schedule.

Evidence matrix

Give every decision a current record and owner

Evidence set

Site evidence

Comparison record

Land control, survey basis, hazards, environmental history, planning and permit route, utility territories, emergency access and dated constraints

Accountable input

Development and site lead

Evidence set

Power and water

Comparison record

Load profile, application status, studies, agreements, network works, water source and discharge basis, backup operating cases and current authority correspondence

Accountable input

Utilities and engineering leads

Evidence set

Connectivity

Comparison record

Carrier serviceability, diverse physical paths, shared points, demarcations, construction scope, optical and service tests, delivery dates and operational escalation

Accountable input

Network and carrier leads

Evidence set

Supplier package

Comparison record

Contracting entity, relevant US delivery evidence, scope boundary, subcontractors, product and labour assumptions, current capacity, schedule, deviations and exclusions

Accountable input

Procurement and package owner

Evidence set

Acceptance

Comparison record

Design reviews, factory and site tests, integrated scenarios, witnesses, pass criteria, defects, retests, training, asset records and operational handover

Accountable input

Commissioning authority

Evidence set

Decision record

Comparison record

Evidence date, owner, open condition, consequence, mitigation, expiry or refresh trigger, decision and approver

Accountable input

Project controls and accountable executive

Offer comparison

Keep scope, evidence and time on one basis

01

Issue one baseline

Give every candidate the same location, duty, interface, programme, evidence, acceptance and commercial basis. Put alternatives into a numbered deviation schedule.
02

Separate status from proof

Record whether each item is supplier-published, independently verified, authority-issued, contractually committed, tested or still assumed. A plausible claim is not a closed condition.
03

Refresh before the gate

Recheck utility, permit, production, labour, subcontractor, logistics and test assumptions at shortlist, award, notice to proceed and handover. Preserve the dated decision record.

Primary references

Official sources used for this guide

The Federal Energy Management Program connects IT conditions, air management, cooling, electrical systems, heat recovery and performance metrics; it describes design guidance, not a project approval.
FEMA brings together location-enabled hazard and resilience tools for screening and planning. Their outputs are a starting point for project-specific studies, not a substitute for them.
The FCC explains that fixed availability is provider-reported mass-market service data collected twice a year. It does not establish enterprise capacity, physical route diversity or a deliverable carrier service.
EPA points data-centre stakeholders to water, air, contaminated-land and environmental-data resources while noting the role of state and local authorities in implementation and permitting.
EPA identifies stationary engines and turbines as potential regulated sources and explains that state and local agencies issue most data-centre air permits under approved programmes.
OSHA says staffing agencies and host employers share responsibility for temporary-worker safety and recommends defining their respective compliance duties in the contract.
SAM.gov separates a Unique Entity ID from the active registration needed to bid directly for federal awards. Neither is a general-purpose technical or delivery qualification.

Sources checked 28 September 2026. Confirm current federal, state, local, Tribal, utility, environmental, safety, contractual and technical requirements with the responsible authorities and specialists for the actual site and scope.