Operational Renewable

Apple — Prineville, Oregon Data Center

Prineville, Oregon, United States

Capacity
120MW
Operator
Apple
AI Focus
Inference (Apple Intelligence, iCloud, Siri AI)
Year
2012

Apple’s Prineville, Oregon data center is one of the company’s largest and most important facilities, hosting iCloud infrastructure and increasingly AI inference workloads for Apple Intelligence. Located in the high desert of Central Oregon alongside Meta’s nearby Prineville campus, the facility opened in 2012 and has been expanded multiple times.

Prineville’s location — 160 miles east of Portland at 3,000 feet elevation — provides naturally cool air for much of the year, enabling free cooling for a significant portion of data center operations. Oregon’s hydroelectric-dominated power grid provides low-cost, low-carbon electricity. Apple has powered the Prineville facility entirely through renewable energy since 2014, utilizing direct solar installations and wind power purchase agreements.

The facility hosts Apple’s iCloud services (Photos, Notes, iMessage backups), App Store infrastructure, and increasingly the Private Cloud Compute infrastructure that powers Apple Intelligence — the on-device and cloud AI system launched with iOS 18. Apple designed Apple Intelligence’s privacy architecture specifically for PCE nodes hosted in facilities like Prineville, with verifiable security guarantees that Apple claims even Apple employees cannot access the compute.

Reference Metadata

Country
United States
Region
Oregon
City
Prineville
Status
Operational
Timeline Year
2012
Location Precision
City
Machine-readable record
JSON GeoJSON

Browse This Facility Through The Index

Entry pages are the atomic records in the index. Use the JSON endpoint for programmatic access, then move through the taxonomy links to the broader operator, country, energy, and timeline views that contextualize this facility.

Related Facilities

Nearby slices in the index that share the same operator, geography, build phase, or AI profile. Use these to move laterally through the buildout instead of jumping back to the full directory.

Follow the buildout feed