Map how AI systems connect, work, and evolve
Everyone shows the tools.
AI Arcs shows the wiring.
A screenshot of a tool list tells you nothing. An arc is one connection in a real system — what calls what, what it reads, and why it is there at all.
No account needed to look around.
Same system, five months apart. Watch it grow →
-
See what survives the hype
Launch week tells you what shipped. These maps tell you what people were still running four months later — and what quietly got cut.
-
New uses for tools you already have
Most of the good ideas here are not a new tool. They are someone wiring two things you already run into a loop you had not thought of.
-
Take the whole setup, not a screenshot
Fork any public architecture into your own studio and edit from there. The reasoning on every connection comes with it.
-
Find the people wired like you
Publish a map and you will see who overlaps with your stack — and what they run that you do not.
Three things we mean
by an arc.
The word does triple duty, and so does the product. Each reading is a level you can zoom to.
-
01
A connection
The line between two things, and the reason it exists. Every arc carries its why — not just that the agent reads the ticket history, but that it only does so when a customer is named.
-
02
An architecture
Enough arcs and a shape appears: the lanes a system spans, the loops it runs, the guardrail everything has to pass. The whole map is an arc too — one system, readable at a glance.
-
03
An arc over time
No stack arrives finished. Keep the versions and you get the third arc: the path a system travelled — what got added, what got cut, and what the person learned in between.
Architectures you can
actually read.
Each one is a working system, reconstructed from public documentation and sources. Open any of them — every connection carries the reasoning behind it.
Loading the library…
Start with what
you already use.
Pick a few things. A map draws itself as you go — no diagramming, no forms. That map is worth keeping for a plain reason: you will forget why you wired it this way, and so will everyone you explain it to.
Choose a model, an agent, anything —
the connections appear as you pick.
- Nothing is connected to your systems. You describe your setup; AI Arcs never touches it.
- Private until you say otherwise. Publish a whole map, or none of it.
- No lock-in. Export everything you have made as JSON, whenever you like.
Bring your stack.
Leave with a few ideas.
Start with the tools you already use. Keep it as simple, private, or public as you like.