Choose where to save
Save explicitly in this browser or choose private Cloud storage for access on other devices. A local save is not a cloud backup.
- 01API GatewayAWS API Gateway
- 02Orders LambdaAWS Lambda
- 03Orders tableAmazon DynamoDB
- 04Order eventsAmazon EventBridge
aal system-design "0.2"
dictionary "0.2.0"
design Example "From an order request to a saved event" {
element Gateway "API Gateway" { type aws.amazon_api_gateway }
element Orders "Orders Lambda" { type aws.lambda }
element Data "Orders table" { type aws.amazon_dynamodb }
element Events "Order events" { type aws.amazon_eventbridge }
relation Flow1 Gateway -> Orders request_response "Place order"
relation Flow2 Orders -> Data write "Save order" Matching AAL
Illustrative product preview · AAL and canvas element Orders "Orders Lambda" { type aws.lambda }Three ways to see the system
The right view for the conversation.
Explore structure, connected systems, and interactions over time. Each capability is an independent project with its own model and language. Acefy Architecture Language (AAL) is readable diagram source that stays synchronized with the canvas.
System Design
Applications. Data. Events. Infrastructure.
- 01API GatewayAWS API Gateway
- 02Orders LambdaAWS Lambda
- 03Orders tableAmazon DynamoDB
- 04Order eventsAmazon EventBridge
From an order request to a saved event
API Gateway invokes Lambda, which stores the order in DynamoDB and publishes an event to EventBridge.
Get started with System Design →Matching AAL excerpt
aal system-design "0.2"
dictionary "0.2.0"
design Example "From an order request to a saved event" {
element Gateway "API Gateway" { type aws.amazon_api_gateway }
element Orders "Orders Lambda" { type aws.lambda }
element Data "Orders table" { type aws.amazon_dynamodb }
element Events "Order events" { type aws.amazon_eventbridge }
relation Flow1 Gateway -> Orders request_response "Place order"
relation Flow2 Orders -> Data write "Save order"
relation Flow3 Orders -> Events publish "Order created"
}C4 Architecture
Software structure. Context. Containers. Components.
- 01API GatewayAWS API Gateway
- 02Orders LambdaAWS Lambda
- 03Orders tableAmazon DynamoDB
Make software responsibilities visible
Explain who uses your systems, how applications fit together, and what each component is responsible for.
Get started with C4 →Matching AAL excerpt
architecture Commerce {
system Store "Online store" {
container Gateway "API Gateway"
container Orders "Orders Lambda"
container Data "Orders table"
}
Gateway -> Orders "Place order"
Orders -> Data "Save order"
}Sequence Diagram
Make the order of interactions clear. Start with one overview and open deeper details where they help explain the flow.
Explore Sequence diagrams →Architecture canvas ↔ AAL
Change the design. See the source agree.
Review the boundaries. Refine a responsibility. Rename an element. Your visual edits and readable AAL stay aligned, so the architecture stays yours to shape.
Explore visual authoring →- 01API GatewayAWS API Gateway
- 02Orders LambdaAWS Lambda
- 03Orders tableAmazon DynamoDB
- 04Order eventsAmazon EventBridge
Matching AAL 01 / 01
element Orders "Orders Lambda" { type aws.lambda }Prepared interaction · canvas and source update together
Start with something concrete
Real patterns. Room for your ideas.
01 / AWS ORDER PROCESSING
From request to order event
Trace API Gateway, Lambda, DynamoDB, and EventBridge in one connected design.
02 / GCP DATA PROCESSINGFrom event to insight
Follow Pub/Sub, Cloud Run, and BigQuery in a compact processing flow.
03 / SOFTWARE STRUCTUREExplain the order platform
Use a C4 view to show the responsibilities behind the AWS order flow.
From your browser to your next review
Keep your work useful beyond the canvas.
Bring the design into the room
Use automatic layout to organize your diagram, then Present to focus your discussion on the architecture.
Take your architecture with you
Export SVG or PNG for documents and presentations. Export a project file to preserve editable source and saved layout.
A few useful details
Before you start.
Understand diagram types, AI drafting, and how your projects are saved.
Read the documentationWhich project type should I choose?
Use C4 for software structure, System Design for connected systems, and Sequence for interactions over time. Each project type has its own AAL language and synchronized visual designer.
What is AAL?
Acefy Architecture Language is readable source for your diagrams. C4, System Design, and Sequence each have a dedicated AAL language. You can write source or edit visually, with both kept in sync within each project.
Do I need an account, and where is my work saved?
Start designing C4, System Design, and Sequence diagrams without signing up. Save explicitly: Local means this browser. Accounts add AI Guided Draft, the full palette, and up to 20 private cloud diagrams total across all three types. A local save is not a cloud backup. Export a project file for a portable copy; local and cloud clones remain independent.
How do the diagram types complement each other?
C4 explains responsibilities and structure. System Design maps connected elements and boundaries. Sequence explains the order of interactions, with deeper detail where needed. They remain independent projects.
Does System Design deploy my resources?
System Design models your platform and its interactions. It does not provision resources, discover a live environment, or verify running infrastructure.
Can I create an architecture draft with AI?
Yes. Sign in, open a C4, System Design, or Sequence project, and choose AI Guided Draft. Describe your architecture and optionally attach or paste one JPG or PNG. A validated draft replaces the current diagram and AAL; you can undo it and save explicitly. Review the design before relying on it. You can also use our downloadable references with your own external AI assistant.
Your next architecture conversation starts here
Make your architecture easier to explain.
Start without signing up. Choose C4, System Design, or Sequence and build your first useful diagram. Accounts add AI Guided Draft and cloud persistence.