The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
In an April 2019 interview ahead of Google Cloud Next, then-CEO Thomas Kurian argued that Google Cloud could compete with AWS by improving enterprise sales, making open-source software easier to buy and operate, and partnering with developers rather than undermining them. On military work, he pointed to Google’s published AI principles: they barred AI designed for weapons while allowing some government and military uses.
Those remarks capture an early strategy, not today’s cloud-market picture. Google Cloud’s current pitch is much more centered on AI, security and data platforms. The interview remains useful for understanding how Kurian framed Google’s enterprise ambitions—and where his statements were executive claims rather than independently verified facts.
The 2019 challenge: turn technical strengths into enterprise business
GeekWire published its interview with Kurian on April 9, 2019, shortly before Google Cloud Next 2019, which the event coverage expected to draw more than 30,000 attendees. Kurian had recently succeeded Diane Greene as Google Cloud CEO after spending 22 years at Oracle. The immediate challenge was to persuade large organizations that Google could deliver not just capable infrastructure, but the sales, contracting and support expected from an enterprise supplier.
Free tools Windows power users keep installed
One-click scans. No signup required.
The competitive context was stark. The interview cited AWS revenue of $25.7 billion for 2018. At that point Alphabet did not report Google Cloud revenue as a clean standalone figure in the way readers might expect; the article described cloud results alongside businesses including G Suite and Chromebooks. These are historical details from 2019, not current revenue comparisons or market-share measures. Read the original GeekWire interview.
#1 Best Overall
Kurian’s thesis was that Google had strong technology but needed to improve how it took that technology to market. He described priorities that included expanding sales, specializing teams by industry and technical area, and making contracting easier. The distinction matters: a cloud platform can be technically capable and still lose deals if procurement, support, migration help or account coverage falls short.
Why Google partnered with open-source companies
Kurian described customers asking for three things: a managed version of an open-source technology, enterprise-grade support, and the ability to use existing Google Cloud credits to pay for it. Google’s arrangements with Redis Labs, MongoDB and Elastic were intended to answer that demand. The proposition was a service integrated with Google Cloud’s console, billing and sales channels, with Google taking on infrastructure operations and the software company participating in the commercial relationship.
This was more than a general statement of support for open source. It was an ecosystem and distribution strategy: customers could avoid running database infrastructure themselves, vendors could reach enterprise buyers through Google, and Google could make its cloud more useful without building every product in-house. Kurian argued that companies doing the hard work of creating and maintaining popular software deserved to be rewarded.
The context was a growing dispute over cloud providers offering hosted versions of open-source products. Some software companies had changed licenses in response to concerns that cloud platforms could monetize their work without sustaining the companies behind it. Kurian’s argument was not that cloud providers should never host open-source software. It was that the creators and maintainers should have a viable business model and a fair commercial relationship.
Managed open source can still mean cloud dependence
For a buyer, “open source” and “portable” are not synonyms. Source code may be available under an open-source license while a managed deployment depends on a provider’s control plane, identity and access management, networking, monitoring, backup tools, billing and proprietary integrations. A customer may be able to move the data but still face substantial work to recreate the service and its operating procedures elsewhere.
Google’s later open-cloud messaging emphasizes choice, hybrid deployment and multi-cloud approaches. That can coexist with a commercial incentive to make managed services deeply integrated with Google Cloud. The practical question is not simply whether a product is open source, but which parts of a production system can be moved without major redesign.
Before selecting a managed database or search service, check the software’s license and governance, the service’s supported features and versions, export formats, API compatibility, backup and restore process, regional availability, and who provides first-line support. Ask whether the cloud provider supports the upstream project or only its own hosted service. Model egress and migration costs, and document an exit plan while the system is still being designed. Cloud credits and marketplace procurement can make an initial purchase easier, but they do not answer the portability question.
For some workloads, a vendor-managed service such as MongoDB Atlas, Elastic Cloud or Redis Cloud may be preferable if upstream-vendor support or multi-cloud availability is the priority. A cloud-native service may fit better when a single console, billing relationship and integrated operations matter most. Neither route is automatically more open or less expensive.
Kurian’s answer to AWS: improve execution
Kurian did not set out a market-share target in the interview. He emphasized organizational changes: grow the sales and go-to-market teams, add industry and technical specialization, and simplify the process of contracting with Google. He also said Google could bring a wider portfolio—including cloud and other Google capabilities—to enterprise transformation conversations.
He cited large-company adoption across fields such as media, retail, utilities, financial services, manufacturing and health care, and characterized customer loyalty and churn favorably. Those are Kurian’s statements in an interview, not independently audited measures presented there. The same care applies to his broader claim that Google’s weakness was go-to-market execution rather than technology. It explains his strategy; it does not by itself prove that Google had closed the competitive gap.
For cloud buyers, the sales argument has practical consequences. Contract terms, billing clarity, escalation paths, service-level commitments, regional availability, migration assistance and compliance documentation can determine whether a technically attractive platform is workable. A sound comparison with AWS or Azure should account for an organization’s existing agreements and staff skills, data location and egress, identity systems, database compatibility, support needs, specialized services, and government authorization requirements—not just feature lists.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsKurian’s Oracle experience was relevant to this effort. He had spent 22 years there before joining Google, but resisted a simple story of opposing corporate cultures. He said engineers shared many traits across companies, while Google differed in how it brought technology to market and worked with customers. His approach implied a blend: bring enterprise-sales discipline to Google’s infrastructure and engineering strengths without dismissing developer preferences or open-source communities.
What Kurian said about government and military work
Asked about military customers, Kurian said Google worked with “a number of agencies around the world” and referred to the company’s public AI principles. He did not name agencies, contracts, systems or contract values in this interview. His answer was a policy position, not evidence that Google was supplying a particular military capability.
Google’s published AI principles said the company would not develop AI for weapons or other technologies whose principal purpose or implementation was to cause or directly facilitate injury. The same principles allowed government and military work in areas including cybersecurity, training, recruitment, veterans’ health care, and search and rescue. That is a distinction between categories of use, not a claim that every project in an allowed category is automatically appropriate or compliant.
“Working with the military” can describe very different things, from administrative cloud hosting or health-care services to cybersecurity, logistics, intelligence, surveillance or weapons-related systems. The interview does not establish which specific work Google performed. Nor does a broad published principle settle questions about how a particular system is used or how policy limits are enforced. Claims about a specific contract should be grounded in the relevant agency record or company announcement, not inferred from Kurian’s general remarks.
Recommended Free Tools
Google’s current public-sector materials advertise government and defense offerings, including a stated U.S. Department of Defense Impact Level 5 provisional authorization. That is a company claim about a compliance and hosting capability; eligibility depends on the relevant service and scope. It is not evidence that Google develops weapons or that every defense use is permitted. See Google Cloud’s public-sector materials.
Best Value
Then and now: Google Cloud’s strategy has shifted
| In 2019 | In 2026 |
|---|---|
| The visible priorities were enterprise sales, procurement, Kubernetes, hybrid cloud and partnerships around managed open-source databases. | Google Cloud’s official messaging emphasizes Gemini, AI infrastructure and TPUs, data platforms, security, and agent-based applications. |
| The competitive story focused on AWS’s scale and Google’s need to improve enterprise execution. | Google highlights AI adoption and growth, including a claim that nearly 75% of its Cloud customers use its AI products. |
| The military discussion centered on the public debate over Google’s AI principles and defense work. | Google’s public-sector pitch includes government compliance claims; its security strategy also features the completed Wiz acquisition and agentic security products. |
Google’s Cloud Next 2026 materials identify Kurian as Google Cloud CEO and describe the company’s current AI and platform priorities. Google has also said Cloud revenue grew 82% year over year in the second quarter of 2026, and it reports its own AI-adoption figures. These are company statements; they do not independently establish Google Cloud’s current market rank or prove that the 2019 strategy succeeded. See also Alphabet’s Q2 2026 results commentary and Google’s announcement on completing the Wiz acquisition.
The change in emphasis is instructive. In 2019, Google was making the case that enterprise execution and ecosystem partnerships could make its cloud competitive. By 2026, it presented AI, security and data as major reasons to buy. The former explains the strategy Kurian articulated; the latter is a snapshot of Google’s current positioning, not proof that every customer should choose Google over AWS or Microsoft Azure.
A practical way to evaluate the pitch
If you are choosing Google Cloud for an open-source workload, compare the same architecture across providers and include more than compute prices. Fix the region, uptime target, data volume, traffic pattern, support tier and commitment term, then use the providers’ calculators: Google Cloud, AWS and Azure. No provider is universally cheapest; networking, storage, support, discounts and workload design change the answer.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Confirm what you are buying: identify the license, service operator, supported version, feature limits and upstream support relationship.
- Test the exit: export a representative dataset, restore it elsewhere if feasible, and estimate migration time, downtime and egress charges.
- Check operational fit: review IAM, encryption and key management, observability, backups, regional availability and compliance evidence.
- Assess procurement and support: compare contract terms, billing, escalation routes, marketplace options and committed-use discounts.
- Match the platform to your constraints: weigh current skills, existing cloud agreements, data gravity, AI needs and any hybrid or multi-cloud requirement.
Google advertises $300 in credits for new customers, subject to its current offer terms, but credits are an onboarding incentive rather than a cost comparison. Check Google Cloud’s current offer and pricing details before making a decision.
The significance of the interview
Kurian’s 2019 argument was that Google Cloud had to become easier for enterprises to buy, easier for developers to use, and more constructive toward the companies behind open-source software. He also said government and military relationships could fit within published AI boundaries. The interview documents how Google’s new cloud chief framed those problems at the time; it is not a final verdict on Google’s competitive standing, the success of its partnerships or the compliance of any particular military project.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
