TerraVision

Turn Terraform code into professional cloud architecture diagrams that stay in sync with your infrastructure — automatic, secure, living documents

📖 Full documentation site →

Watch a 4-Minute Intro

What is TerraVision?

TerraVision automatically converts your Terraform code into professional-grade cloud architecture diagrams using the official AWS, GCP, and Azure icon sets. Your diagrams stay in sync with your infrastructure — no more outdated Visio, draw.io or Lucidchart files.

Why TerraVision?

✅ Always up-to-date — diagrams generated directly from your Terraform code
✅ 100% client-side — no cloud access required, runs locally, your code never leaves your machine
✅ CI/CD ready — automate diagram updates on every PR merge
✅ Free & open source — no expensive diagramming tool licenses
✅ Multi-cloud — AWS (full), GCP, and Azure (core services)
✅ Interactive HTML output — clickable nodes, pan/zoom, search, animated data flow
✅ Editable draw.io export — open in draw.io, Lucidchart, or any mxGraph editor
✅ Optional AI annotations — labels, titles, and flow sequences from Ollama (local) or AWS Bedrock
✅ Terragrunt compatible — auto-detects single- and multi-module Terragrunt projects
✅ MCP server — let AI agents generate diagrams from your Terraform, see the guide

Supported Cloud Providers

Provider	Status	Resources
AWS	✅ Full support	200+ services
Google Cloud	🔄 Partial support	Core services
Azure	🔄 Partial support	Core services

Quick Start

Install

pipx install terravision   # or: pip install terravision if in a virtual env

You also need Python 3.10+, Terraform 1.x, Graphviz, and Git. See the Installation Guide for platform-specific instructions, Docker, and Nix.

Generate your first diagram

git clone https://github.com/patrickchugh/terravision.git
cd terravision

# EKS cluster example
terravision draw --source tests/fixtures/aws_terraform/eks_automode --show

# Azure VM scale set
terravision draw --source tests/fixtures/azure_terraform/test_vm_vmss --show

# From a public Git repo (note the // for subfolder)
terravision draw --source https://github.com/patrickchugh/terraform-examples.git//aws/wordpress_fargate --show

That's it — your diagram is saved as architecture.png and opens automatically.

Generate an interactive HTML diagram

terravision visualise --source ./path-to-your-terraform --show

Click any resource to see its Terraform metadata, search resources, pan/zoom, and watch animated data flow on edges. The HTML is a single self-contained file that works fully offline.

Try the Interactive Demos

Click any of these to see the interactive HTML output TerraVision produces:

🟧 AWS demo — Wordpress on ECS Fargate with CloudFront, RDS, EFS
🟦 Azure demo — VM scale set with load balancer and VNet
🟩 GCP demo — Core GCP networking and compute

Basic Usage

Generate a diagram

# From a local directory
terravision draw --source ./path-to-your-terraform

# From a Git repository
terravision draw --source https://github.com/user/repo.git

# Custom format and filename
terravision draw --source ./path-to-your-terraform --format svg --outfile my-architecture

# Editable draw.io file
terravision draw --source ./path-to-your-terraform --format drawio --outfile my-architecture

Use a pre-generated Terraform plan (no cloud credentials needed)

# Step 1: in your Terraform environment
terraform plan -out=tfplan.bin
terraform show -json tfplan.bin > plan.json
terraform graph > graph.dot

# Step 2: diagram generation, no Terraform or cloud access required
terravision draw --planfile plan.json --graphfile graph.dot --source ./path-to-your-terraform

AI-powered annotations (optional)

terravision draw --source ./path-to-your-terraform --ai-annotate ollama   # local LLM (no data leaves your machine)
terravision draw --source ./path-to-your-terraform --ai-annotate bedrock  # AWS Bedrock via boto3 (uses your AWS credentials)
terravision draw --source ./path-to-your-terraform --ai-annotate restapi  # any OpenAI-compatible endpoint (OpenAI, LiteLLM, vLLM, ...)

Only metadata and the summary graph are sent to the LLM — never your .tf source. The bedrock backend authenticates via the standard AWS credential chain (no infrastructure to deploy); restapi is configured via TV_RESTAPI_URL, TV_RESTAPI_KEY, and TV_RESTAPI_MODEL. See the Annotations Guide and AI-Powered Annotations for the full configuration.

Simplified view

terravision draw --source ./path-to-your-terraform --simplified

Strips VPCs, subnets, and networking plumbing. Great for executive presentations.

Common options

terravision --help shows full help text details.

Option	Description	Example
`--source`	Terraform directory or Git URL	`./path-to-your-terraform`
`--format`	Output format: `png`, `svg`, `pdf`, `drawio`, and more	`svg`
`--outfile`	Output filename	`my-architecture`
`--workspace`	Terraform workspace	`production`
`--varfile`	Variable file (repeatable)	`prod.tfvars`
`--planfile`	Pre-generated plan JSON	`plan.json`
`--graphfile`	Pre-generated graph DOT	`graph.dot`
`--ai-annotate`	AI annotation backend	`ollama`, `bedrock`, `restapi`
`--simplified`	High-level view (no networking)	(flag)
`--show`	Open after generation	(flag)

Documentation

The complete documentation lives at patrickchugh.github.io/terravision.

For users:

For contributors:

FAQ

Common questions — cloud credentials, LLM data privacy, offline use, Terragrunt, output formats, and more — are answered in the FAQ on the documentation site.

Contributing

Contributions are very welcome. See CONTRIBUTING.md for development setup, coding standards, and the PR process.

Support

Issues: GitHub Issues
Discussions: GitHub Discussions
Documentation: patrickchugh.github.io/terravision

License

See LICENSE.

Acknowledgments

Graphviz — diagram rendering
Terraform — infrastructure parsing
Terragrunt — multi-module orchestration
Cloud provider icons from official AWS, GCP, and Azure icon sets

Release files for terravision 0.47.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for terravision 0.47.0
File	Size	Uploaded
terravision-0.47.0.tar.gz	21.3 MB	Sep 4, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for terravision 0.47.0
File	Interpreter	ABI	Platform	Reset
terravision-0.47.0-py3-none-any.whl 22.1 MB Sep 4, 2026	Python 3	none	any	Details

Total release size: 43.3 MB

Release files / terravision-0.47.0.tar.gz

Download URL	terravision-0.47.0.tar.gz
Size	21.3 MB
Tags	Source
SHA-256 checksum How to use checksums	`e17b4906f67e3612f086beddb16350d7cd5deca3cbdd1f1cbbf4f5f1af428641`
BLAKE2b-256 checksum How to use checksums	`3b74de5af3dde5fa03ce074d83e217d29926e9312c80c1528670b9f3d9df977b`
Upload date	Sep 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/patrickchugh/terravision
Publishing commit: github.com/patrickchugh/terravision/tree/f5236dc5c8a4e2ee7b77d6f198c406da2ecef0b6

Workflow

Publishing configuration: github.com/patrickchugh/terravision/blob/f5236dc5c8a4e2ee7b77d6f198c406da2ecef0b6/.github/workflows/publish-to-pypi.yml
Publishing logs: github.com/patrickchugh/terravision/actions/runs/33881716131/attempts/1

Artifact

Subject: terravision-0.47.0.tar.gz
SHA-256 checksum: e17b4906f67e3612f086beddb16350d7cd5deca3cbdd1f1cbbf4f5f1af428641 Verifying attestations

Release files / terravision-0.47.0-py3-none-any.whl

Download URL	terravision-0.47.0-py3-none-any.whl
Size	22.1 MB
Tags	Python 3
SHA-256 checksum How to use checksums	`36f90553aacb86959cf81076c0d4867c291ee1ee220ea6f7d05628678cf6b7bd`
BLAKE2b-256 checksum How to use checksums	`576e338f2683e1c0c471521bc1c1ebdf4ba37352f96399efd340770e76039195`
Upload date	Sep 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/patrickchugh/terravision
Publishing commit: github.com/patrickchugh/terravision/tree/f5236dc5c8a4e2ee7b77d6f198c406da2ecef0b6

Workflow

Publishing configuration: github.com/patrickchugh/terravision/blob/f5236dc5c8a4e2ee7b77d6f198c406da2ecef0b6/.github/workflows/publish-to-pypi.yml
Publishing logs: github.com/patrickchugh/terravision/actions/runs/33881716131/attempts/1

Artifact

Subject: terravision-0.47.0-py3-none-any.whl
SHA-256 checksum: 36f90553aacb86959cf81076c0d4867c291ee1ee220ea6f7d05628678cf6b7bd Verifying attestations