I built this while working as an AWS Solutions Architect. I kept seeing the same problem - DevOps teams would hand over architecture diagrams that were months out of date, or worse, just wrong compared to what was actually deployed.
They were maintaining diagrams manually in draw.io, updating them whenever infrastructure changed. Which meant they were perpetually out of date. That's not a good use of anyone's time.
When I explored what auto diagramming tools were out there, they either needed access to state files or cloud accounts (not always possible in security-conscious environments), or produced basic dependency graphs rather than proper diagrams with VPC and subnet groupings.
Terravision reads your Terraform HCL directly, runs entirely client-side with no credentials required, and can slot into a CI/CD pipeline so your docs update themselves after every deployment.
Feedback welcome - what would make this more useful?
neogeno•2h ago
They were maintaining diagrams manually in draw.io, updating them whenever infrastructure changed. Which meant they were perpetually out of date. That's not a good use of anyone's time.
When I explored what auto diagramming tools were out there, they either needed access to state files or cloud accounts (not always possible in security-conscious environments), or produced basic dependency graphs rather than proper diagrams with VPC and subnet groupings.
Terravision reads your Terraform HCL directly, runs entirely client-side with no credentials required, and can slot into a CI/CD pipeline so your docs update themselves after every deployment.
Feedback welcome - what would make this more useful?