{"slug": "openai-national-community-compact-no-ndas-with-officials-full-power-costs", "title": "OpenAI National Community Compact: No NDAs With Officials, Full Power Costs", "summary": "OpenAI published a National Community Compact and a Compute Campus Policy Blueprint on November 5, 2026, committing that every future compute campus it owns and operates will pay the full cost of the electricity and infrastructure it uses, publish site-level water and electricity use, avoid non-disclosure agreements with public officials except for narrow security, trade-secret and competitively sensitive information, and report expected jobs annually. The compact is a voluntary company commitment, not law; the accompanying blueprint asks governments to turn those practices into rules for all data center builders. The move follows OpenAI's January 20, 2026 Stargate Community post and lands three days after its Grid Protectors Program, and it addresses regulators' stranded-cost concern by promising financial assurances before major spending begins, though OpenAI did not specify the form those assurances take.", "body_md": "OpenAI published a [National Community Compact and a Compute Campus Policy Blueprint](https://openai.com/index/setting-new-standard-responsible-ai-infrastructure?ref=explainx) on November 5, 2026. The compact says that every future compute campus OpenAI owns and operates will pay its own way on power, report its water and electricity use in public, avoid non-disclosure agreements with public officials, and publish the jobs it expects to create. The blueprint then asks governments to turn those habits into rules for everyone.\n\nThis is a policy move, not a product launch. It lands three days after the [Grid Protectors Program](https://explainx.ai/blog/openai-grid-protectors-program-1000-mw-flexible-demand-georgia-effingham-2026) and during a bruising season for data center builders. The core question for readers is simple: how much of this is new, how much can you hold OpenAI to, and what does it say about where AI infrastructure politics is heading?\n\n## TL;DR: what OpenAI committed to\n\n| Question | Answer, per OpenAI's November 5 post | \n|---|---|\n| What was published? | A National Community Compact (company commitments) and a Compute Campus Policy Blueprint (proposals for lawmakers) | \n| Who is covered? | Future campuses that OpenAI owns and operates, each with its own local compact | \n| Who pays for power? | OpenAI says it pays the full cost of the electricity it uses and the infrastructure that serves it, with financial assurances before major spending | \n| Water? | A water plan per campus, closed-loop or low-water cooling prioritised, site-level water and electricity use published | \n| Noise? | Construction plans and independent noise studies published before operations and annually after | \n| NDAs? | None with public officials, except narrow protections for security information, trade secrets, or proprietary or competitively sensitive information | \n| Jobs? | Expected jobs published, annual reports on hiring and apprenticeships, work with unions and training providers | \n| Is it law? | No. It is a voluntary company commitment. The blueprint asks policymakers to make rules | \n\n## What does the National Community Compact say?\n\nOpenAI frames the compact as the next step after its January announcement. In that earlier [Stargate Community post](https://openai.com/index/stargate-community?ref=explainx), dated January 20, 2026, OpenAI said every Stargate site would get its own tailored plan and that it would \"pay our own way on energy\" so its operations would not raise local electricity prices. It named examples in Wisconsin, Michigan and Texas where partners underwrite power infrastructure.\n\nThe new compact turns that into a common checklist. According to OpenAI, each local compact will reflect local priorities but include the same set of commitments. OpenAI also promises to engage residents early enough that their input shapes project plans, to give residents a local point of contact for the life of the campus, and to report publicly each year on how it is doing.\n\nWater use droplet over a data center cooling block, illustrating OpenAI's published water and electricity commitments\n\n### Power and infrastructure\n\nThe most concrete line is about money. OpenAI says it will pay the full cost of the electricity it uses and of the infrastructure needed to serve it. It also says it will provide financial assurances before major spending begins, so that other customers are protected if a project is delayed, reduced or canceled.\n\nThat last clause matters. The common fear from regulators is stranded cost: a utility builds a plant or line for a giant customer, the customer walks away, and ordinary ratepayers inherit the bill. A promise of upfront assurances addresses that scenario directly, though the post does not say what form the assurances take (a deposit, a parent guarantee, or a minimum-bill contract).\n\n### Water, noise and public data\n\nOpenAI promises a water plan for each campus, and says it will prioritise closed-loop or low-water cooling. It will publish site-level water and electricity use. It will publish construction plans and independent noise studies before operations begin, and again each year after.\n\nPublishing site-level numbers is a change from the usual practice, where utilities and companies treat per-site consumption as commercially sensitive. If OpenAI follows through, journalists and local officials get a baseline for checking claims. Our earlier explainer on [data center water and electricity](https://explainx.ai/blog/data-center-real-environmental-impact-water-electricity-2026) shows how hard those numbers are to verify today.\n\n### NDAs with public officials\n\nThe compact says OpenAI \"will not use\" NDAs with public officials. It then allows \"narrow protections\" covering legitimate security information, trade secrets, or proprietary or competitively sensitive information.\n\nThose carve-outs are wide in practice. \"Competitively sensitive\" can cover site selection, power pricing and tax terms, which are exactly what residents complain about learning late. The test will be the text of each local compact and whether officials can discuss a project with residents before a vote.\n\nThis follows other companies. We covered [Amazon dropping NDAs with governments](https://explainx.ai/blog/amazon-drops-data-center-ndas-built-together-1-billion-moratoriums-2026) in October and [Google ending NDA requirements for local officials](https://explainx.ai/blog/google-stops-data-center-nda-local-officials-the-information-raskin-microsoft-amazon-2026) shortly after. OpenAI's version is the third big-company move on this point in a month, and it comes with the same kind of exceptions.\n\n### Local jobs and community investment\n\nOpenAI says it will publish the jobs it expects to create, work with unions and training providers, and report annually on hiring and apprenticeships. It also promises sustained investment in priorities that residents help choose.\n\nThe post gives two examples. In Effingham County, Georgia, residents helped shape a $4.8 million grant to provide free school meals for all 14,000 students in the county. In Pike County, Ohio, families named childcare as a priority, which led to a joint $6 million commitment from OpenAI and SB Energy. Both figures come from OpenAI's own post; I did not find independent confirmation of the amounts.\n\nAn academy building with rows of badges, representing local workforce training in OpenAI's compute campus jobs commitments\n\n## What is in the Compute Campus Policy Blueprint?\n\nThe blueprint is the second half of the announcement. OpenAI says voluntary commitments are \"an important starting point\" but that \"new policy is required to establish trust and confidence\" among communities, elected officials and companies. The blueprint is addressed to federal, state and local lawmakers. According to OpenAI's post, it proposes:\n\n- **Who pays for power.** State utility commissions should require large electricity customers to cover the costs they add to the grid and protect other customers if a project falls through.\n- **Flexible connection.** Utilities should make it easier for campuses to connect if they can safely cut demand when power is scarce. OpenAI points to its Georgia Power agreement, which lets the utility reduce power to its Effingham County campus by up to 1,000 megawatts in high-demand periods.\n- **Federal help.** Congress can speed up transmission upgrades and restore and expand tax incentives for clean electricity.\n- **Public reporting.** Water, energy, noise and hiring data, and narrow limits on when developers can require public officials to sign NDAs.\n- **Transparent incentives.** When states or local governments offer tax incentives, the terms should be public, with measurable commitments and a way to recover benefits if a developer falls short.\n- **Local supply chains.** Developers share purchasing plans early so local suppliers can compete, and employers, building trades unions and community colleges use hiring forecasts to train residents.\n\nMuch of this overlaps with bills already moving. Our post on a [Senate permitting bill that would make data centers pay transmission costs](https://explainx.ai/blog/baaja-senate-permitting-bill-data-centers-pay-transmission-costs-20-mw-50-billion-claim-checked-2026) covers one federal version of the \"pay what you add\" idea.\n\n## What is actually new compared with January?\n\nJanuary was a principle with examples. November is a template. The differences, based on the two OpenAI posts:\n\n| Item | January 20 Stargate Community | November 5 Compact | \n|---|---|---|\n| Scope | Stargate sites | Future campuses OpenAI owns and operates | \n| Power costs | Pay our own way, tailored per region | Pay full cost of electricity and infrastructure, plus financial assurances before major spending | \n| Water | Prioritise closed-loop or low-water cooling | Water plan per campus, published site-level water and electricity use | \n| Noise | Not a headline item | Independent noise studies published before and after operations | \n| NDAs | Not addressed in the post | None with public officials, narrow exceptions | \n| Jobs | OpenAI Academies, workforce partners | Published job forecasts, annual hiring and apprenticeship reports | \n| Accountability | Not specified | Annual public report, local point of contact | \n| Policy asks | None | Compute Campus Policy Blueprint | \n\nThe two genuinely new items are the NDA language and the annual public reporting. Those are the parts residents and journalists can check.\n\n## Why now? The politics around the announcement\n\nThe timing is not subtle. Data centers became a campaign issue this autumn, and we mapped the pushback in [our data center backlash map](https://explainx.ai/blog/ai-data-center-backlash-map-2026) and in [our midterm races post](https://explainx.ai/blog/data-center-backlash-midterms-texas-pennsylvania-ohio-michigan-races-moratorium-2026). A Bloomberg report, as summarised in a Techmeme headline, says OpenAI pledged to change how it handles data center deals after Democrats' midterm wins. I could not open the Bloomberg article, so I am not relying on its details. The OpenAI post itself does not mention the election or any party.\n\nEarlier reporting that OpenAI planned a post-midterm policy push and a rename of data centers to \"compute campuses\" is covered in our [post on the AI compute campus rebrand](https://explainx.ai/blog/openai-ai-compute-campuses-data-center-rebrand-post-midterm-pr-what-is-reported-2026). The November 5 post uses \"compute campus\" throughout, which fits that report, although OpenAI has not said the rename is a strategy. OpenAI has also shown it will lobby on this topic directly: see its [letter to the Texas governor on a data center pause](https://explainx.ai/blog/openai-letter-texas-governor-abbott-data-center-pause-2026).\n\n## What is confirmed and what is not\n\n**Confirmed by OpenAI's own post:** the compact and blueprint exist and were published November 5, 2026; the list of commitments above; the Georgia Power 1,000 MW reduction clause; the Effingham $4.8 million and Pike County $6 million community figures.\n\n**Not confirmed or not stated:**\n\n- No timeline or list of which future campuses get a compact first. The post says \"future\" campuses only.\n- No definition of \"financial assurances\" or what counts as \"competitively sensitive\".\n- No independent audit. Reports are OpenAI's own, published annually.\n- No mention of partner-built sites such as those run with Oracle or Microsoft, which carry much of OpenAI's capacity. The January post named partners; the compact covers sites OpenAI owns and operates.\n- No claim that the election drove the change. That link comes from press framing, not from OpenAI.\n\n## What this means for people who build with AI\n\nFor most developers, nothing changes in an API call. The practical effects are indirect.\n\n- **Cost and capacity.** If utilities and states adopt rules that make large loads pay for grid upgrades and accept curtailment, the cost of AI compute may rise, and some capacity may arrive later. OpenAI is betting that clear rules unlock permits faster than fighting each town.\n- **Reliability.** A campus that agrees to cut up to 1,000 MW at peak implies that inference or training jobs may shift in time. OpenAI has not said how this affects API latency or availability.\n- **Local-first signals.** If you build or host AI workloads, expect questions from customers about where compute sits and what it consumes. Published site-level water and electricity data could become a procurement input.\n\nIf you work on a data center project or advise a town, the compact is a usable checklist: ask for a water plan, an independent noise study, a public jobs forecast, financial assurances, and the exact NDA language before a vote.\n\n## How to hold the commitments to account\n\nThe words are only as good as the follow-up. A few concrete checks:\n\n1. Look for the first local compact text. A signed local document is more useful than a national blog post.\n2. Compare the first annual report with the compact line by line: water, electricity, noise, hiring.\n3. Watch whether state utility commissions adopt \"pay what you add\" tariffs, since that is what makes the pledge enforceable.\n4. Check whether officials in affected towns report being free to discuss terms in public.\n5. Track whether competitors match the commitments. Amazon and Google moved on NDAs first.\n\n## Bottom line\n\nOpenAI's November 5 compact is a more specific version of a promise it first made in January. The specifics worth tracking are the NDA language, published site-level data and annual reports. It is voluntary, it covers only campuses OpenAI owns and operates, and its broadest wording sits in the exceptions. The blueprint is the more consequential half: if states write these rules into law, every builder follows them, not only the companies that volunteered.\n\n*Details come from OpenAI's posts dated November 5, 2026 and January 20, 2026, and may change as local compacts are published. Accurate as of the publication date.*", "url": "https://wpnews.pro/news/openai-national-community-compact-no-ndas-with-officials-full-power-costs", "canonical_source": "https://explainx.ai/blog/openai-national-community-compact-compute-campus-policy-blueprint-no-ndas-pay-own-way-2026?utm_source=rss&utm_medium=feed&utm_campaign=blog", "published_at": "2026-11-05 00:00:00+00:00", "updated_at": "2026-11-05 11:52:18.075563+00:00", "lang": "en", "topics": ["ai-policy", "ai-infrastructure"], "entities": ["OpenAI", "National Community Compact", "Compute Campus Policy Blueprint", "Stargate", "Grid Protectors Program"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/openai-national-community-compact-no-ndas-with-officials-full-power-costs", "markdown": "https://wpnews.pro/news/openai-national-community-compact-no-ndas-with-officials-full-power-costs.md", "text": "https://wpnews.pro/news/openai-national-community-compact-no-ndas-with-officials-full-power-costs.txt", "jsonld": "https://wpnews.pro/news/openai-national-community-compact-no-ndas-with-officials-full-power-costs.jsonld"}}