All Tools View Categories About Contact Privacy

Terraform Provider Registry Explorer

Search a built-in catalog of Terraform providers and parse registry source paths.

Runs entirely in your browser - nothing is uploaded and no live connection is made to the Terraform Registry.
Note: this is a static catalog browser with no live connection. Results come from a bundled sample list, not the live registry.
0
providers matched
Your provider search results will appear here.

About Terraform Provider Registry Explorer

The Provider Registry Explorer is a client-side reference tool for Terraform providers. It searches a built-in catalog of popular providers and can parse a registry source path into its namespace, name and system components. No live Registry connection is made: the catalog is a curated sample bundled into the page, and source parsing happens locally, so your queries never leave the browser. This is handy when you need to recall a provider source string, check which namespace publishes a provider, or teach someone how the registry.terraform.io addressing scheme works without opening a browser tab to the live site. Because everything is static and local, the tool works offline and is safe to use on locked-down networks. Pair it with the provider block and providers.tf generators to move from a catalog lookup to working configuration in a couple of steps. The catalog focuses on the providers teams actually reach for, which keeps results relevant rather than overwhelming. When you parse a source path, the tool also explains each component so the addressing model becomes intuitive: the namespace is usually the publishing organization, the name is the provider, and the system is almost always terraform. This mirrors how the public registry and private registries structure their addresses, so what you learn here transfers directly to real configuration. You can also use the explorer to double-check that a provider you plan to depend on exists in the expected namespace before you add it to a required_providers block, which avoids a failed terraform init later. The tool is deliberately read-only and presents no buttons that would mutate your configuration, so it is safe to keep open alongside an editor while you work. Many engineers keep it as a quick reference when writing modules that span several cloud providers and want the correct source strings without context switching to a web browser.

Features

  • Static catalog - a curated list of common providers with versions and summaries.
  • Keyword search - filter by name, namespace, category or summary text.
  • Category filter - narrow the catalog to Cloud, Container, Security and more.
  • Source parser - split registry paths into namespace, name and system.
  • Required providers snippet - generate a ready terraform.required_providers block.
  • Live count - a stats chip shows how many providers matched.
  • Copy, Download, Print - export the results list.
  • No live connection - fully local, private and offline friendly.
  • Namespace awareness - see who publishes each provider at a glance.
  • Version visibility - current versions are shown for quick compatibility checks.
  • Summary preview - each entry includes a short description of what it manages.

How to Use

  1. Open the tool and locate the search panel on the left side of the page.
  2. Type a keyword such as aws, google or docker to filter the catalog.
  3. Pick a category from the filter dropdown to narrow results further.
  4. Paste a source path like registry.terraform.io/hashicorp/aws if you want it parsed instead.
  5. Click Search catalog or simply type, since results update as you go.
  6. Load a sample to prefill a search for aws providers.
  7. Review the results in the right pane, including the matched count.
  8. Export by copying, downloading or printing the results list.
  9. Combine filters - use a keyword together with a category for precise results.
  10. Copy the snippet - when parsing a source, copy the generated required_providers block into your module.

Examples

Example 1 - keyword search - typing aws lists the AWS provider plus any other provider whose summary mentions aws, with a matched count of the results shown above the list.

Example 2 - source parse - pasting hashicorp/aws returns the namespace hashicorp, name aws and system terraform, along with a required_providers snippet you can paste straight into a configuration.

Example 3 - category filter - selecting the Container category with an empty keyword lists every container provider in the sample, which is a fast way to browse a focused subset of the catalog without typing a query.

Benefits

  • Local - no registry call and no network needed.
  • Educational - learn the source addressing layout quickly.
  • Fast - instant filtering as you type.
  • Portable - copy or download the results anywhere.
  • Offline - works on restricted networks safely.
  • Confidence - verify provider names before depending on them.
  • Consistency - standardized source strings across your whole team.
  • Focused - a curated set keeps lookups fast and relevant.

Frequently Asked Questions

Does this connect to the live Terraform Registry?
No. A built-in catalog is searched and registry source paths are parsed locally. There is no live connection and nothing is uploaded.
What can I search?
Type a keyword (e.g. aws, google, docker) to filter the bundled provider catalog by namespace, name, category or summary.
Can I paste a registry source?
Yes. Paste a path like registry.terraform.io/hashicorp/aws or hashicorp/aws and it will be split into namespace, name and system.
Why is there no live connection?
Browsers cannot reach the registry directly without a backend, so this is a client-side reference and parser only.
Is the catalog complete?
No. It is a curated sample of popular providers, not the full registry.
Can I copy or download the results?
Yes. Copy the visible list, download it as a text file, or print it.