The Architecture Studio (Architecture in the console menu) is generated fresh on every view — nothing is pre-rendered, cached, or versioned. Open it and you're always looking at your org's current schema, not a snapshot from whenever someone last remembered to regenerate it.
The pages
| Page | What it shows |
|---|---|
| Overview | What your app is made of, in one page, with an executive summary you can write. |
| App Architecture | How the app fits together, left to right: the API, what it calls, and the glyphs, events, connectors and AI providers those reach. |
| Infrastructure Diagram | The AWS resources behind the app, and which of your assets use each one. Follow the numbers to trace a request. |
| App Flows | How the app works from the outside in — who does what, on which asset, on which AWS resource. |
| Data Model | Your entities, how they relate, and what every field means. |
| API Reference | Every endpoint your app exposes, with its fields and descriptions — and the OpenAPI document to download. |
| Integrations & AI | What your logic reaches outside the app: connectors and AI providers. |
| Runtime Resources | The AWS building blocks every asset runs on, and why each one is there. |
| Environments | Test and Prod side by side: what is the same, what differs and what is ready to promote. |
| Export | Preview the architecture document page by page, then download it as a PDF. |
| Review queue | Descriptions the AI wrote. Accept them, edit them, or reject them. |
See how it works: request journeys
On the Infrastructure Diagram, the See how it works bar lists common use cases: an API request and how it is counted, a WebSocket chat, a Logic Block run (straight away or in the background), an inbound webhook, a record change that triggers automations, an account email, search syncing, a Glyph and a crew run. Pick one and a dot travels the diagram step by step, with a caption for each step. You can pause, step forwards and back, change the speed, turn on Narration (a recorded voice that reads each step), and switch on Show what happens when it fails to see the failure paths too.
The walkthroughs are written by hand, but they are checked against the generated diagram, so they can only describe connections that really exist. If a part a walkthrough passes through has changed since it was last reviewed, it is marked as possibly out of date.
Exporting a PDF
Open Export, choose the sections you want (executive summary, infrastructure diagram, app flows, data dictionary, API reference, resource inventory, asset descriptions), and the page preview on screen is the document you will download. Choose whether AI-written drafts are included and which page style to use.
The OpenAPI / Swagger reference
The API Reference page shows a real OpenAPI 3.1 specification, generated live from your entity and logic block definitions with no stored file to fall out of sync, and lets you download it for Swagger UI, Postman or any API tool. A separate public-only spec is limited to no-login routes (useful for a partner integration that only needs your public endpoints).
Always current by construction
Because the OpenAPI spec is generated from the same live catalog your API actually runs on, there's nothing to remember to update — change an entity's fields and the spec reflects it on the next request.