Describe your system in plain English. Get a structured diagram of services, APIs, databases, queues, and data flows — ready for engineering reviews and documentation.
Design your systemFrom a single service to a full microservice architecture — describe the components and let AI map the connections.
Web client, mobile app, API gateway, auth layer, and backend services
Service-to-service calls, inter-service dependencies, and API contracts
Message queues, event buses, consumers, producers, and dead letter queues
Database reads/writes, cache layers, replication, and storage boundaries
Authentication flows, token validation, authorization checks, session handling
Retry logic, circuit breakers, fallback states, and error notification flows
System design prompts work best when you describe components like services, not just steps. Include:
No. AI creates a fast first diagram, but engineers should always review correctness, missing failure modes, security assumptions, and scale constraints. Use the generated diagram as a conversation starter — not the final word.
Developers get the most technical value, but product and operations teams can use the diagram to understand service dependencies, data movement, and system boundaries without reading code.
Not directly — the app generates Mermaid flowchart diagrams which show data flow and dependencies. For ER diagrams specifically, use a dedicated database schema tool. For flow between services and databases (which service reads/writes what), this tool works well.
Export as PNG for Slack, Jira, or Confluence embeds. Export as SVG for Figma and design tools. Copy the Mermaid code to embed in GitHub, GitLab, or Notion. All exports are available from the Export menu in the canvas toolbar.