AI infrastructure concentrates compute, power, connectivity and sensitive data in a small number of sites. Every one of them can be reached in more than one way: through the hardware on its way to the rack, through the airspace above it, through the people who hold a badge, through the network, and through the argument over whether it should exist at all.
Guarding, access control, cameras and standard certifications are sold by everyone, and a site needs all of them. Ice Nine covers the layers above that baseline: the hardware supply chain, the airspace, the people with access, the systems inside, and the fight over whether the site gets built at all. Each is priced on its own and assembled for the specific site, because a gap in one is a route into the others. The layers are being built to Israel's standard for critical national infrastructure, the doctrine written for airports, ports and power stations, applied to a data hall.
Ice Nine also works for the capital side of a deal: the lenders and banks financing a site, the insurers underwriting it, and the independent risk consultancies hired to assess a data center operator before any of them commit.
Hardware, from the factory floor to the rack.
Ice Nine traces critical hardware from source through delivery, installation, maintenance and replacement, and treats provenance, custody, firmware and service access as part of the security boundary. Sealed and monitored transport, tamper evidence, and inspection before anything goes through the door. The work recurs on every refresh, decommission and resale, because the boundary moves with the equipment.
Drones, and the rest of the physical perimeter.
Ice Nine studies how a candidate site can be found, watched, reached, disrupted or isolated: physical access, drone exposure, nearby activity, power and fiber dependencies, personnel movement, supplier risk. Detection and interception cover drones up to a defined class. Above that class the work is early warning and an orderly shutdown that protects the data rather than the building. Strategic weapons are outside what any private operator can address, and Ice Nine says so rather than implying coverage it does not have.
The people who can get inside.
Screening at intake, entry mechanisms, identification at the door, compartments inside the hall, and a record of who touched which equipment and when. This is the first question operators ask, and the one where a clean answer is hardest to produce after the fact.
Systems that hold when something gets through.
Networks and operations are designed around segmentation, limited trust and controlled access. Where the mission requires it, systems can run in isolated or air-gapped environments with clear rules for moving data, software and equipment across the boundary.
Tested before handover, and after.
Before launch and at agreed points during operation, authorized teams test physical, cyber, personnel and operating procedures. Every exercise has a defined scope, clear rules and a named owner for each finding.
When something does happen, the team needs decisions that were made in advance. Ice Nine helps define risk levels, local authority, fallback communications, isolation steps, recovery order and the path back to normal operation.
Whether the site gets built at all.
A site that cannot get approved never reaches any of the above. On third-party counts, organized opposition blocked or delayed at least 75 US data center projects worth about $130 billion in the first quarter of 2026, nearly matching the whole of 2025 in three months. The number of active opposition groups doubled to 833 across 49 states, and lawmakers in 14 states filed bills for statewide moratoriums.
Figures from Data Center Watch, first quarter 2026. Third-party estimate.
Most of that opposition is genuine. Communities ask real questions about water, power prices, land and noise, and a project that cannot answer them deserves to stall. Running alongside it is activity built to look local: material seeded from outside the community, timed amplification, and accounts that exist to make a small objection read as a settled consensus. Ice Nine reports coordination indicators, and does not attribute a campaign to anyone.
So Ice Nine treats the information environment around a site the way it treats the fence line. Before a project is announced, it maps who is likely to organize against it, which claims will be made, which of those the project can answer with evidence, and which need a change to the design. Once a project is public, it separates an organized campaign from a neighbor with a fair question, and keeps a dated record of what was said, by whom, and how far it travelled. It does not run public campaigns, place media, or organize supporters. That work belongs to the project's public affairs and legal teams. Ice Nine supplies the assessment, the monitoring and the evidence they work from, creates no accounts, and posts nothing anonymously.
One view of risk, not five vendors.
Ice Nine is embedded in Magn. Security stays connected to site choice, approvals, power, capacity, hardware, partners and daily operations, so the people responsible for a site get one account of what threatens it and what has been done about each part.
Ice Nine operates close to critical infrastructure. Details about its people, methods and active work are shared selectively.
Start with one site. For a focused threat assessment of a planned, contested or operating site, email info@magn.ai.