Understand Terraform repos at a glance.

terraform graph generates a raw DOT representation of Terraform's dependency graph and requires Terraform CLI. Other visualization tools typically require a state file to generate a graph. tfwizard instead parses the source files directly, so you can explore a repository without initializing Terraform, downloading providers, or having access to its state. It also provides an interactive UI with module hierarchy, resource search, filtering, and blast-radius analysis

Primarily engineers who write or review Terraform — when onboarding onto an unfamiliar codebase, planning a risky change, or explaining infrastructure to others. Also useful during incidents for quickly mapping blast radius.

AWS, GCP, and Azure resources are classified into categories (compute, networking, storage, IAM, AI, and so on). Any other Terraform provider parses and graphs correctly — resources just won't carry category metadata.

When uploading files manually, your .tf files are stored in your own browser's local storage and sent to the server for parsing. The server holds only the parsed result in memory — no raw file bytes — and that in-memory state can be lost if the server scales down between requests.

When loading from GitHub, the server fetches the repository directly. Raw file content never reaches your browser's storage at all, so the only thing stored locally is the rendered graph.

In both cases, attribute values matching common sensitive patterns — password, secret, token, api_key, and similar — are replaced with [redacted] in the graph. This matters most for the GitHub path; for manual uploads your browser already holds the original files.

No. Just open the URL, paste a GitHub link or upload .tf files directly. Nothing to install or configure.