Voice-first architecture canvas
Talk your architecture into existence.
Describe a system out loud. TalkGraph draws it as you speak, checks it against real architecture rules, and stress-tests it before anyone writes a line of Terraform.
No sign-up. Works with a mic, a keyboard, or a mouse.
Listening
- spoken scenarios pass the benchmark
- 24/24
- spoken scenarios pass the benchmark
- components in the typed catalog
- 42
- components in the typed catalog
- general tools, strict JSON schemas
- 9
- general tools, strict JSON schemas
- components the agent can invent
- 0
- components the agent can invent
How it works
From a sentence to a stack you can defend.
Every spoken edit compiles to typed commands, applied as one atomic transaction. What you see is exactly what gets exported.
You say it
AssemblyAI's Voice Agent hears you over one WebSocket, with keyterms drawn from the component catalog so Kafka, pgvector, and your own service names come through right. Interrupt it any time.
It's checked before it's drawn
The agent can only act through typed tools against an allowlisted catalog. Illegal links, like a browser talking straight to Postgres, are refused out loud with a one-tap fix.
It's stress-tested
A live linter flags single points of failure, missing caches and queues, and plaintext links. Say “simulate 10x traffic” or “kill the database”, then “fix it”.
It ships
Export a Terraform skeleton, a Mermaid diagram, or an architecture decision record, all generated from the same typed graph you see on screen.
Guardrails
It pushes back like a senior engineer would.
Most diagram tools draw whatever you say. TalkGraph knows a queue can’t write to a database on its own, that replication only runs between the same engine, and that a client should never hold database credentials. When it infers something for you, it says why, and one tap undoes it.
“Connect the web app straight to Postgres.”
Clients shouldn't reach a database directly. That skips auth and turns your schema into a public API. Want me to put a service in between?
“Put a queue between the API and the database.”
Done. A queue can't write to Postgres by itself, so I added a worker to consume it.
“Kill the database.”
Orders is down with it. Nothing else in the path has a replica.
Who it’s for
Built for the conversations where systems get designed.
Design reviews
Sketch the proposal live while the room talks, and leave with an ADR instead of a whiteboard photo.
Solutions engineers
Draw the customer's architecture on the call, in their words, and send the diagram before the call ends.
Incident postmortems
Rebuild what failed, kill the component that went down, and show which fix would have held.
Interview prep
Practice system design out loud against a partner that pushes back when a design won't scale.