KIO MER1: Yucatán coverage needs service reliability and pricing discipline
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: Existing operator-listed modular facility; current occupancy undisclosed. Capacity scope: IT MW undisclosed; compact modular enterprise / regional facility. How we verify evidence.
← Back to project indexCompare this project → · Track its catalysts → · Evidence guide →
- Location
- Mérida, Yucatán, Mexico — representative locality pin
- Readiness
- Existing facility / readiness unverified
- Status
- Existing operator-listed modular facility; current occupancy undisclosed
- Confirmed companies
- KIO Data Centers
- Next milestone
- Accepted local demand, measured efficiency and net recurring service margin
- 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
Our analysis: Yucatán coverage needs service reliability and pricing discipline. MER1 adds southeastern Mexico with a compact enterprise facility. Its Tier II-characteristics description and single service drop should remain visible in the analysis.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Existing operator-listed modular facility; current occupancy undisclosed Readiness source →
What the sources establish
- Facility role. KIO describes KIO MER1 as a carrier-neutral modular facility with 89 square meters technical space for enterprise and regional workloads. It uses Tier II-characteristics wording. Primary source →
- Technical boundaries. Eight ATOM rooms; six 109 kVA UPS units; two 500 kW generators; single 13.2 kV service drop. Operator design PUE is 2.1; this is not measured annual PUE or verified IT capacity. 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 |
|---|---|---|
| KIO Data Centers | Private colocation and infrastructure operator | Net local service contribution after support, power, maintenance and renewal. |
| Enterprise customers and carriers | Potential recurring service and connection counterparties | Actual signed contracts and route resilience; identities undisclosed. |
| Infrastructure suppliers | Potential equipment and maintenance receipts | Named awarded procurement before public-market attribution. |
How financially meaningful is it?
Our analysis: A modular enterprise site can support local services without frontier-model training hardware. Its economic opportunity lies in accepted recurring service, customer continuity and connectivity rather than a campus-scale GPU narrative. KIO’s Tier II-characteristics language does not establish the same certification or service envelope as every other KIO facility. Backup generators, redundancy within the building and a single medium-voltage service drop need separate reliability assessment. The reported design PUE suggests material facility overhead under its design assumptions, but it cannot be used as measured annual performance. Regional weather, fuel logistics and network-route redundancy require site-specific engineering diligence; none is assigned a quantified loss probability here. Local customer contracts must cover support, maintenance and energy while allowing for replacements. A broad KIO platform brand does not eliminate local demand concentration or technical limits.
Facility yield equals accepted rent plus net service contribution minus operating, maintenance and financing costs, relative to all allocated delivery capital.
Hypothetical illustration: 50 kW steady IT load at an assumed 2.0 PUE uses 876 MWh annually. A USD 10/MWh electricity-price change adds USD 8,760 annual cost. These are illustrative operating assumptions, not the site’s accepted load, measured PUE or tariff.
Milestones that would change the assessment
| Milestone | Evidence to watch |
|---|---|
| Scope and capital | Reconcile campus and portfolio figures, accepted versus potential capacity, and property versus equipment funding. |
| Electrical and cooling acceptance | Billable capacity, density upgrade costs and lease renewal economics. Equipment delivery, construction completion and commissioning are separate steps. |
| Commercial productivity | Useful workloads or billable customer capacity, with operating costs and renewal obligations included. |
| Counterparty attribution | Named binding service and procurement terms before estimating participant earnings. |
What could break the investment case?
Our analysis: A single service drop, compact footprint and expensive support can limit customer suitability. Design efficiency is not measured efficiency, and Tier-characteristics wording should not be upgraded to independent certification.
What would change our view?
Our analysis: Dated acceptance, improved useful output and competitive net resource costs would strengthen our assessment. Underutilized capacity, expensive upgrades without customer support, or rising renewal costs ahead of economic benefits would weaken it. We would update this profile using campus-specific operating and contractual evidence. A larger corporate investment headline, a grant program or a design capability alone would not establish a stronger return.
What remains unknown
Current accepted IT MW, facility load, billable occupancy or workload utilization, site-attributable earnings, tariff details, phase capital, supplier contract values and measured performance remain unestablished unless explicitly stated above. Operator specifications are not independently measured outcomes. The pin represents the locality rather than a verified server hall. Broad portfolio AI demand is not proof of a dedicated AI deployment here.
Project research for information, not a buy recommendation. Financial illustrations use assumptions, not disclosed site results or management guidance.
Company investor information & quarterly statements
KIO principal operator is private; public quarterly statements unavailable. No named major publicly traded AI tenant established by matched MER1 evidence.
Corporate disclosures provide company-wide context. They do not establish this project’s revenue, spending, profit, ownership share or operating capacity. Disclosure verification records →