Buckeye Technology Park
FJI qualification held or pending: the full four-document gate, including project-specific government evidence, has not yet been accepted. Qualification evidence and decisions →
Project status: Developer lists owned land in development; operating capacity unestablished. Capacity scope: 1,800 MW developer-listed capacity; energized IT load unverified. How we verify evidence.
← Back to project index- Location
- Arizona / Buckeye
- Readiness
- Proposed / development
- Status
- Developer lists owned land in development; operating capacity unestablished
- Confirmed companies
- Tract; future tenants and equipment suppliers unconfirmed
- Next milestone
- Executed customer commitments, dated utility delivery and financed construction phases.
- Reviewed
- October 6, 2026
Expanded analysis · Original disclosures linked below · CAD and USD preserved as labeled · Company statements attributed; interpretations labeled.
The one-minute investment takeaway
Buckeye is a land-and-infrastructure development opportunity at an early economic stage. The most valuable next evidence is a binding customer commitment paired with deliverable power. Acreage creates room to build, but it does not tell investors when revenue begins or which listed company benefits. The developer, future campus owner and computing customer may be different parties.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Developer lists owned land in development; operating capacity unestablished Readiness source →
What the sources establish
- Operator / company disclosure Current listing. Tract lists 2,019 acres, 1,800 MW of capacity and an owned-and-in-development status. It describes 22 parcels and by-right data-center use. These are developer specifications, not confirmation of energized IT capacity. Primary source →
- Operator / company disclosure Historical scope. The August 28, 2024 acquisition announcement described 2,069 acres, potential for up to 40 data centers and utility planning that could support 1.8 GW. The reviewed sources do not explain the acreage difference. Potential full build-out is distinct from financed construction. Primary source →
Who receives the money?
Our analysis of disclosed roles. Revenue routes are business-model interpretations, not estimates of booked project revenue.
| Company / exposure | Economic role | What investors need to establish |
|---|---|---|
| Tract / private | Acquires and develops land and infrastructure. | Land sales, development fees or lease economics depend on transaction terms that are not established here. |
| Future campus tenants | Would fund or use individual developments. | No reviewed source establishes a named hyperscaler commitment; Microsoft, Amazon and Alphabet are comparison context only. |
| Power and equipment suppliers | Would enable serviced land and computing operations. | Proximity to Palo Verde does not establish a power contract. No project-specific supplier orders are verified. |
How financially meaningful is it? Analyst interpretation
Our analysis: value is created by converting land into usable, contracted infrastructure. The central diligence bridge runs from zoning to utility delivery, then customer financing, construction and billing. The 1,800 MW headline cannot be multiplied by a generic construction cost and called committed spending. Investors also need to know which counterparty pays for substations, roads and water infrastructure, and whether the developer retains ownership or sells parcels.
Development cash return = net land or lease proceeds + earned development fees − land basis − infrastructure and carrying costs − financing costs. A retained campus requires a separate recurring-rent model; no specific transaction structure is assumed.
Hypothetical illustration: USD 100 million of debt carried at an assumed 8% costs USD 8 million annually before other expenses. A two-year delay adds USD 16 million of simple interest if the balance and rate stay constant. These are assumed values, not Tract debt terms.
Milestones that would change the assessment
| Milestone | Evidence to watch |
|---|---|
| Customer commitment | Identify a named counterparty, binding scope and cancellation conditions; a prospective customer is an earlier stage. |
| Utility delivery | Seek executed service arrangements, phased delivery dates and cost allocation rather than proximity or total development capacity. |
| Financed construction | Track funded phases, permits and physical handovers; separate serviced land from a commissioned computing campus. |
What could break the investment case?
Our analysis: Infrastructure delivery can lag customer requirements, and financing costs accrue before revenue. Tenant concentration can weaken bargaining power. Water, cooling and community constraints require project-specific evidence; neither adequate supply nor a shortage is inferred here.
What would change our view?
Our analysis: Our confidence would rise with executed tenant agreements, financed phases and dated utility commitments. It would fall if infrastructure spending proceeds without contractual demand or if delivery obligations require costs that expected proceeds cannot cover.
What remains unknown Not established in this review
Tenant identity, financing terms, infrastructure budget, water and cooling plans, current energized capacity, completion dates and public-company project earnings remain unestablished.
Project research for information, not a buy recommendation. Financial illustrations use assumptions, not disclosed site results or management guidance.
Arizona government record check
Reviewed October 7, 2026 · Reported city agreement; primary agreement verification unresolved
Independent local reporting describes Buckeye’s August 6, 2024 council action replacing the Cipriani residential development agreement with a technology corridor associated with Tract. The executed city agreement, its adopted ordinance and infrastructure reimbursement conditions were not retrieved in this review; those terms are therefore not certified here. The developer’s 1,800 MW figure remains a development envelope. No matched project-specific utility decision or service agreement was retrieved establishing committed delivery dates, and no air-permit match was established for future tenant facilities.
Independent account of council action · Buckeye council record archive — follow-up source · Tract campus listing · Maricopa County air-record portals
Targeted record screen; air permits, building completion and project-specific power service remain unverified in this review. Readiness is based on the separately cited project evidence.
Company investor information & quarterly statements
Corporate-disclosure certification held: Tract: held; Research packet retains a corporate disclosure hold.
Tract
Land/infrastructuredeveloper; futuretenantsunconfirmed
Disclosure verification held: Official investor and quarterly document coverage remains incomplete.
Private participant: Private/unlisted participant: no public quarterly financialstatements reviewed. No invented quarterlies or indirectparent exposure. Current ownership/private-status documentation remains tobeverified.
Corporate disclosures provide company-wide context. They do not establish this project’s revenue, spending, profit, ownership share or operating capacity. Disclosure verification records →