Under every system, there is a drawing.Sinopia finds it.
Code, data, pipelines, jobs and infrastructure in a single living map. Connect it to your coding agent, and it queries the map on its own before it touches anything. It runs inside your company: your code stays yours.
Watch your agent read the map.
No voiceover, just music: the real product, filmed while it works. The tool calls and the answers are the ones the Rossi Distribuzione map actually gave.
One line in the terminal. Your agent sees the map.
Connect Sinopia to your coding agent like any MCP connector. From then on it has 37 tools to read the map: find a node, trace where a piece of data comes from, measure the impact of a change, open the file at the right line. It calls them on its own, when it needs them.
- I
You ask a question, like you would a colleague.
- II
Your agent queries the map, on its own.
- III
And it answers with the file and the line.
The questions you used to ask whoever was there.
Three questions from the demo, asked to the Rossi Distribuzione map. Scroll: the product's own map view answers.
What breaks.
“If I change the order total, what breaks?”
The pigment seeps into the plaster one step at a time: each ring is one hop from the field that changes. On the right, the count by system and by category.
Where the data comes from.
“The nightly balance job: who uses what it produces?”
The chalk line runs from the mainframe's JCL job to the website checkout: the export, the nightly pipeline, the warehouse, the credit service.
The plan, piece by piece.
“I want the customer’s balance and credit on the order page: write me the plan.”
The agent wrote the plan by walking the map, and pinned it to the wall: what changes, where, and what stays untouched. Like the cartoon a fresco is painted from.
An agent is only as good as the context it gets.
Coding agents read the code in front of them. The data, the pipelines, the nightly jobs and the mainframe, they don't.
The person who knew it is retiring
Years of logic in a single head.
There is a migration to do
First you need to know what it touches, down to the last job.
A new head of IT just arrived
They need to understand what they inherited, without reading everything.
Your agents get it wrong
Code that compiles, and a broken pipeline they couldn't see.
Any system, inside the map.
Rossi Distribuzione is a fictional company made of real systems: an e-commerce site, an ERP, a mainframe, and the glue that holds them together. This is how they become one map.
Code, data, jobs, infrastructure.
COBOL and JCL from the mainframe, the ERP's XML, the website's Go, SQL and dbt, Airflow, Terraform, Kubernetes. A read-only copy, and nothing else.
Every piece finds its place.
Deterministic code extracts the structure. For Rossi: 12,870 nodes in 8 systems, and 33 bridges between them.
Every node says where it comes from.
File and line, always. The model only writes the explanations, the map updates itself every night, and when it isn't sure it refuses instead of writing.
Your code stays in your box.
The map engine runs at your place, one database per company. The gateway runs at ours: it recognizes the person and lets the answers through, without keeping them. Any agent, via MCP.
The real map, yours to explore.
Below, Sinopia's map view runs on the Rossi Distribuzione map, with the answers from a real session. Step into a system, open the questions, click a node: this is the product, not an animation. The interface speaks English; the company it maps speaks Italian.
The preview holds 420 of the 12,870 nodes, with the real answers of the map. The live demo has everything, and answers in real time. Best explored on a computer.
Sinopia.
The sinopia is the red drawing painters traced on the plaster, under the fresco. When the fresco comes away, it is still there.
So it is with a company's software: screens change, systems pile up in layers, but underneath there is a drawing. Sinopia finds it.