Read the processing flow on the architecture diagram
Architecture diagrams drawn in IceShore carry your use cases, so you can read the processing flow.
No walkthrough meeting needed
You can follow the flow one use case at a time, so nobody needs a meeting to explain how to read the diagram.
Processing order
Starting from the user who triggers the flow, each system resource is numbered in processing order.
Expected traffic
Traffic for each resource (rps, etc.) is totaled automatically, so you can spot resources under heavy load and resources that are rarely used.
People aren’t the only ones who can read it
An architecture diagram drawn in IceShore is a hybrid: a diagram people can read, and code AI can read.
Hand that diagram to your AI, and it answers all kinds of questions with the same understanding you have.
"deliverySync": {
"title": { "en": "Send delivery schedule" },
"trigger": {
"type": "timedAction",
"description": { "en": "EventBridge hourly schedule" },
"end": [{ "$ref": "template.yaml#/resources/DeliverySyncFunction" }],
"endpointTitle": { "en": "Delivery schedule sync" }
},
"traffics": {
"syncToTable": {
"source": { "$ref": "#/useCases/deliverySync/trigger" },
"end": [{ "$ref": "template.yaml#/resources/OrderTable" }],
"endpointTitle": { "en": "Order table" }
},
"syncToPartner": {
"source": { "$ref": "#/useCases/deliverySync/trigger" },
"end": [{ "$ref": "#/actors/deliveryPartner" }],
"endpointTitle": { "en": "Delivery company API" }
}
}
},
"dailySalesReport": {
"title": { "en": "Previous day's sales summary (for HQ)" },
"trigger": {
"type": "timedAction",
"description": { "en": "EventBridge schedule at midnight every night (JST). cron(0 15 * * ? *) (UTC)" },
"end": [{ "$ref": "template.yaml#/resources/DailySalesReportFunction" }],
"endpointTitle": { "en": "Sales summary batch" }
},
"traffics": {
"reportToTable": {
"source": { "$ref": "#/useCases/dailySalesReport/trigger" },
"end": [{ "$ref": "template.yaml#/resources/OrderTable" }],
"endpointTitle": { "en": "Order table" }
},
"reportToBucket": {
"source": { "$ref": "#/useCases/dailySalesReport/trigger" },
"end": [{ "$ref": "template.yaml#/resources/SalesReportBucket" }],
"endpointTitle": { "en": "Sales report (S3)" }
}
}
}Public samples
Architecture diagrams built from public infrastructure code. You can open them without signing up.
Agent chatbot with Strands Agents and Amazon Bedrock AgentCore
Open diagram→Serverlesspresso: coffee ordering system for event venues
Open diagram→Order service of a serverless e-commerce platform
Open diagram→Routing events to an SQS queue with EventBridge rules
Open diagram→Three-tier Todo web app (Cloud Run + Memorystore + Cloud SQL)
Open diagram→HTTP API on Azure Functions (Consumption plan)
Open diagram→
Why trace the processing flow on an architecture diagram?
A familiar format
Developers already know how to read architecture diagrams.
IceShore adds use cases to a document you already use.
Clearer understanding for people
You understand the system faster than by reading piles of AI-generated documents.
Better understanding for AI
An AI whose context is flooded with documents makes worse decisions.
Giving it compact architecture data steers it toward an accurate understanding of the system.
What you can do with IceShore
Your AI gets better at system maintenance.
FAQ
Does it cost anything?
Free for one person, with no time limit. Teams pay per seat per month (Team $19, Business $39, excl. tax). Team and Business come with a 14-day free trial.
Who writes the processing order?
Your AI writes it after reading the code and infrastructure-as-code files. If the diagram looks wrong, you can ask your AI to fix it.
You can also edit the processing flow directly in IceShore’s editor.
Don’t many use cases make the diagram hard to read?
Select one use case and the resources it doesn’t touch fade out, so you see only that flow.
Can I try it without signing up?
Public samples open without signing up. You can also ask your AI questions about the samples.
Bind your AI-grown systems, with AI.
Start maintaining your systems with IceShore today.