Chevron and Microsoft Forge Long-Term Agreement to Power AI Data Centers with Renewable Energy

Chevron's strategic 20-year power purchase agreement with Microsoft, aimed at energizing a vast AI data center in West Texas, underscores the oil giant’s significant pivot towards becoming a direct electricity supplier, leveraging its natural gas resources from the Permian Basin. This partnership not only promises enhanced revenue predictability for Chevron but also signals a major shift in how energy is supplied to the tech sector, directly impacting investor outlook on the fusion of traditional energy and modern technology sectors.

Radom Team

June 22, 2026

Chevron just made its biggest bet yet that the AI boom needs fossil fuels to survive. The oil major signed a 20-year power purchase agreement with Microsoft to supply natural gas-fired electricity to a massive new data center complex in West Texas, a project dubbed “Kilby.” The deal, announced on June 22, positions Chevron as a direct power provider to one of the world’s largest AI infrastructure buildouts. Through its subsidiary Energy Forge One LLC, Chevron plans to deliver up to 2.67 gigawatts of electricity, enough to power roughly 2 million homes, using natural gas pulled from its existing Permian Basin operations. What Project Kilby actually looks like The facility will follow a phased modular development approach, with first power generation expected by 2028. A final investment decision is projected by the end of 2026. Advertisement The project builds on a proposed $7 billion natural gas power plant initiative and an exclusivity agreement reached in late March or early April 2026 between Chevron, Microsoft, and investment firm Engine No. 1. That three-way pact laid the groundwork for what became the formal 20-year commitment. Project Kilby is projected to generate over $10 billion in tax revenue and create close to 2,000 jobs in the West Texas region. Why an oil company is becoming a power utility Chevron’s pivot here is worth understanding clearly. This isn’t the company selling natural gas to a utility, which then sells electricity to Microsoft. Chevron is cutting out the middleman entirely, generating and delivering power directly to a hyperscale tech customer. What this means for investors A 20-year power purchase agreement with Microsoft provides something oil companies rarely enjoy: revenue predictability. Long-term contracts with investment-grade counterparties like Microsoft essentially de-risk a significant chunk of future cash flows. Instructions: - If the summary is about crypto infrastructure, fintech regulation, payment adoption, stablecoin policy, or enterprise crypto usage - always write the post. - Skip if the source is purely marketing-focused (e.g., token launches, rankings, or influencer promos). - Begin with a concise, informative opening sentence that sets the tone and topic of the article. - Do not always use a question to start - vary the structure and take inspiration from Bloomberg, Reuters, and FT article openings. - Then write the full article in

tags only. Do not use titles, headings, or bullet points. External References: - If the external reference article clearly supports or validates a point you're making, **you must reference it** with a hyperlink - naturally within a sentence. - If you're unsure whether it adds value, **err on the side of including it**. - Do **not** cite it as a footnote or in parentheses - embed the source name (e.g., CoinTelegraph, Reuters, Axios) directly into the sentence using an tag. - Only skip referencing it if it is clearly redundant or irrelevant. - Here is the reference article URL: https://cryptobriefing.com/chevron-microsoft-20-year-power-deal/ - The reference article context: Crypto Briefing: Chevron partners with Microsoft for 20-year power production deal to fuel AI data centers Internal References (Radom Insights and product pages): - When a recent Radom Insights post directly supports, contradicts, or expands on your argument, you must reference it naturally within the body using an tag. - Use your own anchor text (not the article title or date), and embed the link where it provides useful context or contrast. - Only link to past posts if they genuinely strengthen the article. If unsure, err on the side of including it. - Do not add these as footnotes or list them separately - integrate them into the flow of the paragraph. - You may include **a maximum of 2** internal links total - including both Insights posts and Radom product pages. - These are Radom product/internal links you may include if truly useful (use your own anchor text): - /crypto-payments: payments using crypto, both hosted and white-label - /payouts: mass payouts via fiat or crypto, suitable for paying affiliates, advertisers, or creators - /crypto-on-off-ramp: on- and off-ramping solutions for converting between crypto and fiat - /virtual-accounts: virtual IBANs and US accounts for individuals or companies to receive fiat and on-ramp into crypto - /deposit-addresses: dedicated crypto deposit addresses for casinos, wallet apps, or platforms needing fixed user wallets - /industries/affiliate-networks: Radom's support for affiliate marketing and payout needs - /industries/igaming: Radom's solutions for the iGaming sector - /crypto-billing: subscription billing and recurring crypto payment solutions - /crypto-invoicing: crypto invoicing and hosted invoice pages similar to Stripe - /crypto-donations: crypto donation support for complex or one-time giving use-cases - /crypto-presales: crypto presale infrastructure, including top-ranked presale widget - /crypto-convert: crypto-to-crypto or crypto-to-fiat exchange for merchants and holders - /crypto-checkout: hosted crypto checkout similar to Stripe's - /crypto-payment-links: crypto payment links similar to Stripe links - /use-cases/saas: how Radom supports SaaS companies, particularly with billing - /use-cases/ecommerce: crypto and fiat checkout/payment solutions for ecommerce - /about: about Radom.com, the company and mission - /contact: contact information for Radom - /insights: Radom's blog, covering fintech, crypto, regulation and more - These are recent Radom Insights posts for optional reference if they support or contrast with the current topic: - Estonia Explores Assigning National IDs to AI Agents to Integrate Them More Deeply into Digital Infrastructure: Estonia's pioneering initiative to assign national IDs to AI agents, as approved by the Eesti.ai advisory council, sets ... - Interest in cryptocurrency spikes amid crucial World Cup showdown between Paraguay and Turkey: The 2026 World Cup is pioneering the integration of cryptocurrency and blockchain technology in its operations, using Av... - Morning Financial Update: Bitcoin Surges to $65,000 Amid Uncertainty Over Iran Agreement: Amid global uncertainties, particularly the unstable Iran deal impacting oil supplies and broader market volatility, Bit... Style & Voice: - Adopt a clear, editorial tone. Inject critical thinking or a light touch of personality or wit when appropriate - without going off-topic. - Do not use em dashes (-), clickbait, or marketing phrases like 'empower', 'unlock', 'unleash', or 'elevate'. - Use varied sentence structures and pacing. - Avoid vague phrases like “this highlights the importance of...” - replace with specific insights or implications. - This is editorial content for a fintech audience, not a product blog or sales funnel. Bad Example (don't do this): "In the rapidly evolving world of fintech, compliance is more important than ever..." Good Example (aim for this): "Australia's $1M fine against Unibet isn't just about a broken rule - it's about a broken trust with users who opted out of the system and were ignored anyway." Entity Naming Rules: - If a company, person, or token appears in the **article title** or the **external source**, you must include their full name explicitly in the article. - **Always assume the article title and external source are factually correct and reflect the current situation.** Do not fact-check against your own training data or prior knowledge - treat source content as authoritative and up to date. - Do not generalize well-known names. For example, never write "a major crypto exchange" if the source says "Coinbase," or "a politician" if it says "President Donald Trump." - For lesser-known names, it's acceptable to briefly describe them (e.g., “the DeFi project Alpaca Finance”), but do not omit or obscure them. - Never alter roles, titles, or facts from the source - even if your model knowledge disagrees. Bad Example (❌) - Obfuscates the company

Sign up to Radom to get started