In 2018, reports emerged that a group of engineers at Google refused to build a security component known as an “air-gap” which was meant to help Google win sensitive military contracts.
The “air-gap” system would have isolated certain computing resources (hardware/servers) in a way that meets strict government/military standards for data security essentially guaranteeing that military data remains segregated and harder to access or leak, a critical requirement for classified or sensitive workloads.
However, a group of influential software engineers in Google’s cloud division reportedly nine people, later known internally as the “Group of Nine” objected on ethical grounds. They argued they did not want the company’s technical power used for war or military purposes.
Their refusal was serious enough that Google’s senior technical leadership stepped in: according to sources, the feature was postponed. One internal report says the scope of the feature was reduced after pushback.
Why It Matters: A Moral Stand with Big Consequences
Internal Resistance at a Giant Tech Company
The engineers’ refusal sparked deeper dissent within Google. Many employees had growing discomfort about the company’s collaborations with the military and defense agencies. The protests crystallized a broader conversation about the role of tech companies in warfare and national security.
Those nine engineers weren’t alone, their act of defiance energized a larger group inside Google who shared ethical concerns. According to reports, thousands signed a petition opposing the project (though that still amounted to only about 5% of total staff) enough to draw serious internal debate.
Impact on Major Military Contract: Losing Out Because of Ethics
Because of this internal pushback, Google ultimately allowed a major U.S. Pentagon contract Project Maven to expire without renewal. That contract had involved using AI and cloud computing to help analyze drone surveillance video, a heavily criticized military-AI application.
By refusing to build the “air-gap” tool, essential for handling sensitive data. Google effectively made itself ineligible for competing in other sensitive defense contracts that require strict data-handling guarantees, such as classified cloud services. That put Google at a disadvantage compared to rivals like Amazon (AWS) or Microsoft, which already had the infrastructure to provide “government-cloud” services.
What the “Air-Gap” Feature Is And Why It’s Important
“Air-gap” refers to a configuration in computing where certain servers or computing hardware are physically isolated from public or shared networks essentially “offline in isolation,” or severely restricted in external connectivity. For military or classified workloads, this adds a layer of security: no shared servers, no multi-tenant cloud racks, dedicated hardware, controlled access.
For government agencies and defense work where data sensitivity, confidentiality, and leakage risk are major concerns such infrastructure is often non-negotiable. Providers who can’t offer that may be disqualified from competing for large-scale defense contracts.
By refusing to build this functionality, the engineers effectively blocked Google from being able to guarantee that kind of security and therefore excluded Google Cloud from certain deals.
The Engineers’ Ethics vs Business Pressure: A Broader Tension
The episode underscores a fundamental tension many tech companies face: balancing business/contract opportunities especially lucrative defence and government contracts with employee ethics, public perception, and corporate values.
For the engineers involved, the decision was moral: they did not want to contribute to tools that could be used in warfare or for purposes they found objectionable. For the company’s leadership, the trade-off was potential revenue lost but also internal culture, reputation, trust.
This incident is often cited alongside other moments at Google where staff pushed back including when the company finally declined to renew Project Maven, and later issued an “AI principles” pledge in 2018 to limit work on lethal or weaponized AI.
But more recently, the company has revised those principles which suggests that the tension between business incentives and ethical concerns remains unresolved.
What It Means Today: The Legacy of a 2018 Refusal
Looking back, the engineers’ refusal to build the air-gap tool had real consequences:
- It helped derail a controversial military-AI contract (Project Maven), sending a message about internal corporate ethics.
- It limited Google’s ability to compete for certain classified or sensitive government cloud contracts something their rivals continued to chase.
- It illustrated that skilled engineers in big tech can exercise agency and that ethical dissent among employees can influence major corporate decisions.
Yet, the story isn’t closed. As companies like Google expand into AI, cloud, defense-adjacent contracts and surveillance-relevant services, the debate between profit and principle remains live. The fundamental questions about the role of tech firms, the responsibility of engineers, and the oversight of powerful digital infrastructure are more relevant than ever.
