Criticalsecurity
Admin routes bypass the gateway
The backend serves /admin directly, so requests reach it on a path that never passes the gateway's auth check.
FixRoute all admin traffic through the gateway, or enforce auth at the service.
Everything it does on the canvas.
A real diagramming surface that your assistant controls. It lays out your system into tiers, flags risk in place, and writes it all up.
It draws into real tiers, not a pile of boxes.
As components arrive, each one drops into the tier it belongs to and the layout re-routes around it. Drag anything and the connections keep up. The diagram stays readable even when the system is not simple.
ClientClient
FrontendFrontendCDN
Gateway & AuthGatewayAuth
BackendBackendService
AI / LLMLLMAI AgentVector DB
DataDatabaseCacheQueueStorage
ExternalExternal
Risk is marked in place, by severity.
Findings do not live in a separate report tab. They sit on the component they affect, sorted by severity, each with the reason and a concrete fix. Five categories, five severity levels, one consistent scale.
Highbottleneck
Every profile read hits Postgres
There is no cache between the backend and the database on the hottest read path, so each request is a synchronous query.
FixPut the Redis cache in front of the profile reads.
Mediumscalability
One database, no replica
Reads and writes share a single Postgres instance with nothing to fall back to.
FixAdd a read replica before traffic grows another order of magnitude.
InfoLowMediumHighCritical
architecture.md
Download report
It writes the whole thing up.
Ask for a report and you get a full Markdown document: the components and how they connect, every finding with its reasoning, and a phased scaling plan that says what to fix now, next, and later. It is plain text, so it drops straight into your repo, a pull request, or a ticket.
Color is the data, never the decoration.
Fifteen component types, each with a fixed hue and icon, so type is never carried by color alone. Connection load and finding severity have their own scales. Nothing on the canvas is colored just to look good.
ClientFrontendGatewayBackendServiceLLMAI AgentVector DBDatabaseCacheQueueStorageCDNAuthExternal
See your own system drawn this way.
Connect your assistant, describe what you built, and watch the tiers, findings, and report fill in. Or click through a real one first.