OpenAI's official Terraform provider: manage projects, limits as code
Version 1.0 lands in the Terraform Registry — rate limits, spend alerts, service accounts and roles become reviewable HCL. The catch: it needs an org Admin key.
Copy markdown
First-party, not a community fork
OpenAI published the provider as v1.0.0 and documented it in an official guide, retiring the patchwork of community forks builders had been stringing together. It's the sanctioned way to manage your API Platform org as infrastructure-as-code.
What you can now put in HCL
It covers projects, users and group memberships, service accounts, roles, rate limits, spend alerts, and certificates — the full org-admin surface. Guardrails that used to be dashboard click-ops are now diffable and reviewable in a PR.
The gotcha: it needs an Admin key
Auth runs through an organization Admin API key set via OPENAI_ADMIN_KEY; ordinary API keys can't touch these admin endpoints. You'll also need Terraform 1.0 or newer installed locally.
Why multi-project teams care
Spin up a new project with its rate limits and spend caps in one `terraform apply`, then tear it down just as cleanly — no more manual dashboard setup per environment. It pairs with the hard spend limits OpenAI shipped on July 22.