1. [Home](https://www.g2.com/)
2. ...
3. [Diagramming Software](https://www.g2.com/categories/diagramming)
4. [IceShore Discussions](https://www.g2.com/products/iceshore/discuss)

[
 ![IceShore](https://images.g2crowd.com/uploads/product/image/large_detail/large_detail_d337709ff9edd9b1c2912091ebe188cb/iceshore.svg "IceShore")
](/products/iceshore/reviews)

# IceShore Discussions

Your AI reads your Terraform and other infrastructure code over MCP, maps your system architecture in IceShore, and records who uses each part for which business process. Then it can answer system maintenance questions like "Who is affected if we shut down this API?" with the business processes and number of people involved. - Build AWS architecture diagrams from code, automatically. The AI you already use generates architecture diagrams from Terraform, CloudFormation and more. - Diagrams show more than system resources. On top of the resources in your infrastructure-as-code files, IceShore draws what the system does for the business: its use cases. - Select a use case in IceShore and the related users and resources are highlighted, so you can follow the processing flow step by step. - The AI you already use reads and organizes your code. IceShore never calls an AI to build diagrams or make decisions. - Values that look like access keys or passwords are masked before saving, wherever they can be detected. - Diagram data is written in ADL (Architecture Description Language). The spec is public. - From the same architecture, IceShore draws one diagram in Japanese and another in English.

## Be the first to start the conversation

Get answers from real professionals in the G2 community.