Terraform Registry website, registry.terraform.io, Terraform providers, modules, policy libraries, HashiCorp Developer, HCP Terraform, namespaces, infrastructure as code, publishing, and WHOIS domain data

Terraform Registry

Terraform Registry is the official public registry website for discovering and publishing Terraform providers, modules, and policy libraries used in infrastructure-as-code workflows.

Core purpose

Terraform Registry helps users find Terraform providers, reusable modules, and policy libraries, and gives publishers a path to distribute public registry artifacts.

Official domain

registry.terraform.io is the official Terraform Registry website for browsing and installing public Terraform ecosystem artifacts.

Domain created

November 3, 2013

The Terraform logo used as the brand image for the Terraform Registry website page.View official Terraform logo asset

What Terraform Registry is

Terraform Registry official site is the public website where Terraform users search for providers, modules, and policy libraries. HashiCorp's Terraform documentation describes publishing to the public registry for providers, modules, and policies, with namespaces and account workflows used to organize published artifacts. The registry is part catalog and part distribution point. A user may browse package-style pages in the browser, but Terraform itself can read module sources and provider requirements from configuration files during infrastructure planning and deployment workflows.

Providers and modules

Providers connect Terraform to platforms, APIs, and services such as clouds, identity systems, monitoring tools, and databases. Modules package reusable Terraform configuration so teams can standardize common infrastructure patterns. The registry gives both artifact types stable pages with names, versions, documentation, and installation examples.

Namespaces and publishing

Terraform Registry uses namespaces to organize published providers and modules. Publishers can connect accounts and manage public artifacts, while HCP Terraform users can coordinate registry publishing through organization workflows. That structure helps users identify who maintains an artifact before adopting it.

Documentation on package pages

Registry pages usually do more than list downloads. They can show version histories, requirements, usage examples, provider documentation, module inputs and outputs, source links, and commands or configuration snippets. This makes the website a reference surface as well as a discovery tool.

Public and private registry patterns

The public Terraform Registry is useful for open ecosystem artifacts. Teams that need internal reuse can also work with private registry patterns or reference repositories directly. The split lets open-source modules and providers stay discoverable while private infrastructure patterns remain controlled inside an organization.

Who uses Terraform Registry

Terraform Registry is used by infrastructure engineers, platform teams, cloud architects, DevOps teams, security teams, open-source maintainers, and vendors that publish Terraform providers or modules. Some users only copy module source strings, while others rely on the registry as a daily reference for provider resources and module interfaces.

Why it matters

Terraform Registry matters because infrastructure as code depends on reusable, versioned building blocks. A shared registry reduces the amount of custom glue every team has to write, helps users find maintained integrations, and gives publishers a standard place to document and distribute Terraform artifacts.

WHOIS domain data

Data pulled: May 24, 2026View current WHOIS record

Domain: terraform.io
IP address: 76.76.21.21
Registrar: CSC Corporate Domains, Inc.
WHOIS server: www.whois.corporatedomains.com
Referral URL: http://www.cscglobal.com
Created: November 3, 2013
Updated: October 24, 2025
Expires: November 3, 2026
Nameservers: ns-297.awsdns-37.com (205.251.193.41); ns-702.awsdns-23.net (205.251.194.190); ns-1228.awsdns-25.org (205.251.196.204); ns-1672.awsdns-17.co.uk (205.251.198.136)
Domain status: serverDeleteProhibited; clientTransferProhibited; serverTransferProhibited; serverUpdateProhibited
Contact privacy: Registrant name and contact details are redacted; registrant organization is listed as International Business Machines Corporation, and admin and technical contact details are redacted.

Key concepts

ProviderA Terraform plugin that exposes resources and data sources for an external service or platform.
ModuleA reusable group of Terraform configuration files that can be called from another configuration.
NamespaceThe registry identity that groups published providers, modules, or policy libraries.
Version constraintA Terraform configuration rule that controls which provider or module versions can be used.

Common workflows

Search the registry for a provider and copy required provider configuration into a Terraform project.
Evaluate modules by reading usage examples, inputs, outputs, source links, and version history.
Publish public providers, modules, or policies through documented registry workflows.
Use registry documentation during code review when deciding whether a Terraform artifact is maintained and suitable.

Common misconceptions

Terraform Registry is not Terraform itself; it is the website and registry surface for ecosystem artifacts used by Terraform.
A module appearing in the registry does not guarantee it matches a team's security, compliance, or reliability needs.
Public registry modules are not the only reuse option; organizations can also use private registries or direct source references.

Open questions

How should users evaluate trust, maintenance, and security signals for infrastructure modules and providers?
How will private registry workflows evolve as platform teams standardize internal infrastructure patterns?
How much validation should registries apply to published infrastructure artifacts before users adopt them?