Google has reportedly signed an agreement allowing the US Department of Defense to use its AI models for classified work, despite an open letter from hundreds of employees urging the company to stay away from military uses that they say could become dangerous or impossible to oversee.
The deal, reported earlier Tuesday by The Information, allows the Pentagon to use Google’s AI tools for “any lawful government purpose,” including sensitive military applications. Google joins OpenAI and xAI, which have also struck similar classified AI agreements with the Pentagon.
The reported agreement includes language stating that Google’s AI system is not intended for domestic mass surveillance or for autonomous weapons without appropriate human oversight. But it also says Google doesn’t have the right to control or veto lawful government operational decisions, according to reports. Google will also help adjust safety settings and filters at the government’s request.
A Google spokesperson told CNET in an emailed statement that the company remains committed to the position that AI shouldn’t be used for domestic mass surveillance or autonomous weapons without human oversight, and said providing API access to commercial models under standard practices is a “responsible approach” to supporting national security.
The Pentagon declined to comment to CNET.
The deal lands in the middle of an internal backlash. In an open letter addressed to CEO Sundar Pichai, more than 600 Google employees asked the company to “refuse to make our AI systems available for classified workloads.” The employees wrote that because they work close to the technology, they have a responsibility to highlight and prevent its “most unethical and dangerous uses.
“We want to see AI benefit humanity, not to see it being used in inhumane or extremely harmful ways,” the letter says. The employees said their concerns include lethal autonomous weapons and mass surveillance, but extend beyond those examples because classified work could happen without employees’ knowledge or ability to stop it.
The company’s posture toward military and national-security AI has shifted since then.
Last year, Google removed a previous language from its AI principles that said it would not pursue technologies likely to cause overall harm, weapons, certain surveillance technologies or systems that violate widely accepted human rights and international law principles.
In a February blog post updating Google’s AI principles, Google DeepMind CEO Demis Hassabis and senior vice president James Manyika wrote that “democracies should lead in AI development” and that companies and governments should work together to build AI that “protects people, promotes global growth and supports national security.”
For Google workers opposed to the deal, the concern is not just that AI could be used by the military, but that classified deployment removes the usual visibility around how a model is being used.
“I feel incredibly ashamed,” Andreas Kirsch, a Google DeepMind researcher, wrote in a public post on X reacting to the reported deal.
The open letter from Google employees ends with a direct appeal to Google’s CEO: “Today, we call on you, Sundar, to act according to the values on which this company was built, and refuse classified workloads.”
A functioning structure and informational flux that gathers businesses, finance, and technological operations alongside each other to drive up the businesses through cloud transformation.
It promotes data-powered decision-making in due time and results in financial responsibility. The collaboration of finance, operations, and business teams makes it possible to achieve it.
FinOps is a field that integrates principles of financial management with cloud engineering and operations to give organizations an analysis of their cloud expenditure. It also allows them to make well-versed decisions on the allocation of their cloud budget and costs. Its goal is to increase the revenue or the business value with the help of the cloud. It also helps organizations control their cloud expenditure while still maintaining the performance level, dependability, and security required to assist their business operations.
Principles of Cloud FinOps
Accountability
With a set of pre-defined KPIs and benchmarks, the teams responsible for value realization reporting and costing amendment can be held accountable. This makes decision-making a process with standards.
Business Value Realization
Decisions taken from the perspective of business make Cloud FinOps successful.
Flexibility
Encourage constant budget allocation, IT spending, and forecasting to push ahead with agile budgeting and planning procedures in the IT industry.
Clarity of Costs
All organizational levels have access to instantaneous cost and billing data.
Partnerships
For cloud finance management, collaborate with departments like IT, finance, app development, and architecture.
Fluctuating nature of the cloud
Accept the pay-as-you-go aspect of cloud and gain from providing dynamic customer service to meet their ever-changing requirements.
Five Key Elements that Make Cloud FinOps
1. Accountability and Facilitation
This element centers on setting up centralized, multi-functional teams that include engineering, finance, operations, architecture, and app developers, while also setting up governance and benchmarks for cloud expenditure.
2. Planning and Predictions
For cloud planning and predictions to be effective, an organization must allocate resources, benchmark efficacy, and gain a deeper understanding of the cost drivers.
3. Cost Optimization
This element, which is an ongoing, repetitive process that focuses on identifying key cost-optimization drivers, offers a consistent methodology to manage cloud consumption in the most economical way.
4. Measurement & Awareness
This key element focuses on building a key set of KPIs and business-value metrics to calculate the transformation’s success. Customers frequently begin with a set of cost-optimization metrics before switching to unit economics or business value metrics, like cost per transaction or cost per customer served.
5. Tools and Accelerators
To sum up, using the right tools and accelerators is crucial for efficiently managing and monitoring cloud spending. It comprises:
Using Google Cloud cost-management tools to examine cost and billing data in real time
Creating a reporting dashboard for tracking values and managing cloud spending
Putting automation scripts into place to create budget alerts and account guardrails
Benefits That Cloud FinOps Offer
Business Value Realization
Initial focus on cloud migration often leaves the business goal of infrastructure in the rear. Proper cooperation between various departments makes FinOps effective and a success. This allows the reconsideration of business values while lifting cloud management to new heights.
Better Decision Making
Making decisions to make business better than today is the whole point here. Using the insights from cloud data and financial analytics, the FinOps team is able to make informed decisions regarding the business’s cloud computing commodities. This also makes them focus on the business goals.
Art of Predictions and Cloud Reporting
FinOps teams analyze cloud spend and set standards for future cloud costs using analytics, reporting, and forecasting cloud FinOps tools. They can create budgets fittingly and evade unplanned surplus costs thanks to the jacked-up cost visibility.
Accountability for Clear Cloud Use
By providing clarity into resource ownership and cloud spending, FinOps promotes accountability while leveling the time and effort needed for research and change implementation.
Challenges That FinOps Come With
Before Cloud FinOps begins to show results, you must surpass many predicaments. These may include issues with organizational processes, technical implementation, or how the teams as a whole perceive the changes.
Governance
Incorporating new methods, tools, and challenges requires all the things to be in place and well-governed. The processes to be incorporated ought to adhere to existing laws, rules, and compliance standards. It can be challenging to describe these approaches, create policies, and implement them.
Technical Glitches
There might be considerable technical glitches in putting the suggested modifications into practice, from planning effective cost data collection and processing to putting per-instance optimizations, element migration, and access management into practice.
All of the alterations should certainly be based on practicality, as well as administering the right balance between cost-effectiveness and effort, while taking into account the gross solution’s business value.
Cultural Alterations
As the FinOps framework requires processes to be established at every level of an organization, an actual cultural transformation must take place for FinOps methodologies to be implemented successfully. This entails setting up a culture of financial responsibility and accountability while maintaining the requirements of the company and the objectives of the other players in mind.
It could be challenging to bring in this culture, as it needs not only the establishment of appropriate processes but also a shift in the team’s mentalities. So, it is a task!
From Chaos of Cloud to Clarity: An Imperative for Businesses
Cloud FinOps is the way of the future for businesses, but excessive cloud spending can undermine the very advantages that companies are trying to achieve. Cloud FinOps management transforms from a standalone finance function into a vital business capability with FinOps.
Businesses that adopt Cloud FinOps not only reduce cloud expenses but also acquire the flexibility to change course more quickly, the assurance to make more intelligent investments, and the transparency to match IT with business value.
The ability to forecast precisely, budget dynamically, and optimize continuously is not a luxury in a world where cloud usage is only increasing; rather, it is a competitive necessity.
1. What is another name for FinOps? Answer: FinOps is the blend of “Finance” and “DevOps”. It shows the collaboration between business and engineering groups. It is also known by terms like Cloud Financial Management and Cloud Financial Optimization.
2. When did FinOps start? Answer: It began in 2019 as an open community comprising individuals and organizations where knowledge of cloud financial management could be shared.
3. What is the future of FinOps? Answer: FinOps’s future depends on comprehensive innovation and teamwork. FinOps and ITAM combination will be essential as cloud infrastructure develops to trim the financial waste, promote sustainability, and improve AI-powered optimization.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
