Planned colocation and server hosting

Your hardware. Our campus.

Develop your next deployment with SmartTec in Mead, Oklahoma. Buildings A and C provide 5,035 gross sq ft for data-center development. Each customer allocation requires confirmed power, a complete cooling design and commissioning.

SMARTTEC / SPATIAL CONCEPT3D EXPLORER

Start with the equipment you want to place: rack dimensions, weight, power draw and cooling requirements.

Step inside the concept.

AI hardware concept · Not installed inventory or an OEM configuration drawing.

Choose a topic, or open the 3D model.

Illustrative compute hall, not an installed or available facility. Customer allocation and cooling design require a separate review.

Data-center buildings
5,035 sq ft Buildings A and C, gross area
Utility
OG&E 3,000 A at 208 V, three-phase
Carrier option
100 Gbps asymmetrical option Under review; scope and price unconfirmed
Current stage
Development Fit-out and commissioning ahead
SmartTec colocation packet: Your infrastructure. A place to grow. Preview the packet

Your deployment guide / 14-page PDF

Plan your next rack with clarity.

Explore proposed service options, an indicative rate card, a worked monthly budget and published regional pricing comparisons. See how power, liquid cooling, connectivity and deployment responsibilities fit together.

September 2026 · Budgetary proposal. Rates and availability require engineering review, utility confirmation and a signed service order. Market packages differ in inclusions.

Bring your servers or plan a hosted deployment.

Customer-owned hardware

Colocation

Keep ownership of your servers and software stack. We assess the space, power, cooling and connectivity needed for your equipment in Buildings A and C.

Share rack dimensions, equipment weight, IT load and cooling requirements so we can develop an appropriate deployment proposal.

Planned SmartTec-owned hardware

Server hosting

Discuss hosting on servers SmartTec would procure, own and operate. We will agree configuration, access, customer and operator responsibilities, software management and support for the deployment.

For GPU workloads, the proposed 64-GPU B300 fleet would support shared inference and dedicated single-tenant GPU servers. Equipment purchase, allocation, commissioning and customer terms remain ahead.

Compare planned compute services →

Space, power and cooling planned together.

Buildings A and C are designated for data-center development. Building B supports batteries, utilities and storage, and is excluded from the 5,035 sq ft data-center area.

Launch is planned on OG&E grid power. Management reports shared 3,000 A at 208 V, three-phase distribution from Building C; customer IT allocations follow engineering review and commissioning. Solar and BESS are a separate later investment.

Explore the approved campus study. Published model 14 September management target · v6.1.1 cost basis retains an air-cooled, one-building financial baseline. The approved campus experience illustrates a proposed direct-liquid design across Buildings A and C; it requires updated equipment quotes, engineering and repricing before it is included financially. Each colocation proposal needs its own equipment, airflow, power and cooling review; customer allocations are separately scoped.

Development milestones

Construction
24 September 2026 targetUDGOK contractor.
Electrical commissioning
8 October 2026 targetManagement target.
Fiber delivery
8 October–5 November 2026 target windowManagement target; carrier delivery and acceptance required.

Customer availability follows equipment and facility acceptance. These milestones do not represent live capacity.

Match connectivity to the deployment.

The owner reports the Dobson handoff in Building B; the external route remains unverified. A fiber service option is under review. The management delivery estimate was 4–8 weeks from 10 September 2026 and requires carrier confirmation. The reported 100 Gbps asymmetrical option is not an ordered, commissioned or included service commitment.

Committed bandwidth, upstream and downstream rates, circuit type, order status, installation, IP arrangements, egress and service levels await carrier confirmation. Internet service is distinct from the internal GPU fabric and server network interfaces. A financial-model internet allowance does not purchase a stated circuit speed or establish its carrier terms. We will confirm the Phase 1 external bandwidth and support scope against the actual service order.

We review tenant traffic patterns and resilience requirements with the proposed service. Multiple interfaces, circuits or an internal fabric rating do not establish end-to-end internet throughput or route diversity.

A clear path to your deployment.

  1. Share the requirements. Hardware, IT load, cooling, network, target date and any compliance requirements.
  2. Review the fit. We assess the equipment and campus design, and coordinate a site visit where useful.
  3. Agree the proposal. The offer defines the allocation, commercial terms, access, support and service commitments before equipment is deployed.

Colocation terms are developed per proposal. Submitting an inquiry starts the review and does not reserve capacity.