BluSky AI modular data center in Nephi
Also called: BluSky AI Nephi
BluSky AI plans a small (4 MW) modular data center on leased land in Nephi. The deal is not final.
What happens next?
🗓️ No meeting or deadline known yet.
Zoning here is usually decided by the City Council of Nephi City.
Where things stand: Proposed Non-binding letter of intent to lease land, signed September 2025.
❓ 1 open question about it: see below.
Last checked Oct 8, 2026.
🕒 Latest update (Sept 23, 2025): BluSky AI announced a non-binding deal to lease about 16,000 sq ft for a 4 MW modular data center.
What we know
- 📍 Where1358 N 200 W, Nephi (Juab County parcels XA3A-0030-4 and XA3A-0040-2), Nephi, Juab County
- 🏢 CompanyBluSky AI Inc.
- ⚡ Power it needs4 megawatts (about as much as 3,200 homes)
❓ Still unanswered
Nobody has answered these in public yet. Can you help find out?
- Was the lease signed and has the city approved the site? 🙋 I'll find out ·
🔎 What we checked
- Oct 8, 2026: We checked the site location: BluSky AI's filing names the address 1358 N 200 W in Nephi and two county parcels. We placed the pin on the smaller parcel, where the leased pad is.
What happened so far
- Sept 23, 2025BluSky AI announced a non-binding deal to lease about 16,000 sq ft for a 4 MW modular data center.
Local votes and rules
📜 Data center rules
Nephi's city council created a new Industrial 4 (ID4) zone just for data centers and their power plants (Ordinance 12-02-2025). Data centers must use air cooling or closed-loop cooling, not open evaporative cooling. Power plants must bring their own water rights. The zone sets lot size, setbacks, height and dark-sky lighting rules.
Drag the slider to compare the land before and now.
Where this comes from
- BluSky AI looks to lease land in Utah for 4MW data center site · DatacenterDynamics · Sept 2025
- BluSky AI press release (Exhibit 99.1) · SEC EDGAR · Sept 23, 2025
- Juab County parcel XA3A-0030-4 (statewide parcel layer) · Utah Geospatial Resource Center (statewide parcels) · Oct 8, 2026
See something wrong? Tell us and we'll fix it.