OPENSOURCE / INFRAMAP
Visualise Your Terraform Infrastructure in Seconds
Inframap is Cycloid’s open-source IaC visualisation tool. Point it at any Terraform or Terragrunt state file and get a clean, human-readable infrastructure map in seconds – without the noise of Terraform’s native graph command.
What is InfraMap?
Inframap is a command-line tool that takes a Terraform state file (or a Terraform working directory) as input and produces an infrastructure diagram as output. The diagram shows what actually exists in the cloud – VPCs, subnets, VMs, databases, load balancers, IAM roles – and how those resources depend on each other.
The tool exists because Terraform’s built-in terraform graph command produces output that is technically accurate but visually unreadable on anything larger than a toy environment. Terraform’s graph shows the internal dependency structure, including provider metadata and state bookkeeping. Engineers looking at it typically say some variant of “I need something cleaner.” Inframap is the cleaner version: a resource-level graph filtered to what humans actually care about.
Supported providers (Q1 2026):
- Amazon Web Services (AWS) – full coverage
- Microsoft Azure – full coverage
- Google Cloud Platform (GCP) – compute, storage, network, IAM
- OpenStack
- Additional providers via the plugin architecture
Inframap is used inside Cycloid’s InfraView module to power the real-time infrastructure visualisation that platform teams see in the IDP. The same engine, exposed as a standalone open-source CLI for teams that want the visualisation without adopting the full platform.
Inframap vs Terraform Graph: Key Differences
The most common question from developers evaluating Inframap: is this different enough from terraform graph to bother with a separate tool? The short answer is yes; the longer answer is in the table below.
CRITERIA
TERRAFORM GRAPH
INFRAMAP
Output readability
Dense, includes internal Terraform bookkeeping (provider, root_module, meta nodes)
Clean, resource-only, filtered to real cloud objects
Provider support
Generic (any provider Terraform supports)
Provider-aware for AWS, Azure, GCP, OpenStack – understands resource types and relationships
Setup required
Built into Terraform CLI
Single binary install (brew, go install, Docker)
Terragrunt support
Manual multi-state assembly
Native (handles Terragrunt state layouts cleanly)
Output formats
DOT (Graphviz)
DOT + direct PNG rendering
IDP integration
None
Native (powers Cycloid InfraView)
Best for
Debugging Terraform module dependencies
Producing shareable, human-readable cloud diagrams
The honest read: terraform graph is fine when you need to debug Terraform module dependencies at the tooling layer. Inframap is what you want when a human needs to look at a picture of the infrastructure and understand it in under 30 seconds.
An open-source alternative to Cycloid’s star feature
InfraView is InfraMap’s big sister and one of our most popular features. Embedded in the Cycloid platform, it builds more advanced maps with the detailed properties of each element on the diagram. It’s a tool with the wow-factor and is a genuine timesaver for devs, DevOps, and system architects the world over.
What's in it for you?
Infrastructure diagrams always up-to-date
Easy to update internal documentation
Save time on creating diagrams by hand
Supported cloud providers
The open-source cloud infra generator
Frequently Asked Questions
What is Inframap?
Inframap is an open-source Infrastructure-as-Code (IaC) visualisation tool developed by Cycloid. It reads Terraform or Terragrunt state files and generates a clean, human-readable infrastructure map showing resources and their dependencies – filtering out the noise that Terraform’s native graph command produces. Inframap supports major cloud providers including AWS, Azure, and GCP. It runs as a CLI tool and outputs maps in PNG or DOT format.
How does Inframap work with Terraform?
Inframap accepts a Terraform state file or a Terraform working directory as input. It parses the state, identifies the provider resources (aws_instance, azurerm_virtual_machine, google_compute_instance, etc.), builds a dependency graph, and prunes out the internal Terraform bookkeeping resources that clutter the native terraform graph output. The result is a diagram showing only the real infrastructure: VPCs, subnets, VMs, databases, load balancers, and their connections. Output is DOT format, easily rendered to PNG or SVG.
Which cloud providers does Inframap support?
Inframap supports the major cloud providers: AWS, Azure, Google Cloud Platform (GCP), OpenStack, and additional providers via the plugin architecture. Coverage is best on AWS and Azure (the two most-used providers in the Cycloid customer base). GCP support covers compute, storage, network, and IAM. For providers not natively supported, Inframap falls back to a generic resource graph that still improves readability over terraform graph.
What is the difference between Inframap and Terraform graph?
Terraform’s native graph command outputs the internal resource dependency graph as Terraform sees it – including provider metadata, module boundaries, and internal state resources. The result is dense and difficult to read on any non-trivial infrastructure. Inframap filters this output to show only the actual cloud resources and their real-world relationships, producing a diagram closer to what a cloud architecture whiteboard would look like. It also handles Terragrunt state and multi-module setups more cleanly.
How do I install and run Inframap?
Install Inframap via Homebrew (brew install cycloidio/tap/inframap), Go install (go install github.com/cycloidio/inframap@latest), or Docker (docker pull cycloidio/inframap). Run it against a Terraform state file with inframap generate terraform.tfstate | dot -Tpng > infra.png or against a Terraform working directory with inframap generate . | dot -Tpng > infra.png. The output is a Graphviz DOT graph that any dot-compatible tool can render.
Like InfraMap?
Cycloid’s InfraView gives you the same visualisation continuously updated across AWS, Azure, GCP, and on-prem – inside the broader IDP.
