A new standard for database design.
Drawn by you. Driven by your agent.
Three views of one schema, a layout that re-packs itself, and MongoDB documents drawn as documents. Your agent drives the same canvas over MCP — and the arrangement you made survives every edit it makes.
You design a schema in three passes. So it has three views.
Every other tool draws one diagram and leaves you to squint past the columns you are not thinking about. This one draws the amount you need right now, and re-packs the layout every time you switch — so nothing overlaps and nothing needs tidying by hand.
Then it gets messy. One key fixes it.
Half an hour into a design the cards are wherever you dropped them and the edges cross twice on the way. Press the button — or Tidy on the canvas — and the whole thing re-columns itself.
Columns by dependency, not by name.
Each model lands in a column equal to the longest foreign-key path reaching it, so what a thing depends on is always to its left.
Cycles do not break it.
A self-reference has no depth and a loop has no beginning, so the edge closing one is ignored. A schema with a `parent_id` lays out like any other.
It lands on the grid.
Positions snap to the dots you can see, so a tidied layout is one you keep dragging from rather than one that jumps when you touch it.
A document is not a table with a JSON column.
Nesting is how a document database models the world — MongoDB and DynamoDB keep the shape inside the record, not in a join. Most ERD tools let you name a field `JSONB` and leave you there, so that shape stays your problem and the diagram is a lie by omission. Scroll, and watch this one draw the document instead.
Point at one thing. The rest steps back.
A schema past twenty models is mostly noise to whatever you are currently thinking about. Focus is the answer to that: everything one hop from what you are pointing at stays lit, everything else dims. Pick a target and watch the canvas.
One table is touching everything. Hide its relations.
In this ride-hailing schema `user` is an endpoint of 7 of the 8 relations — riders, drivers, referrals and both sides of every rating all point back at it. Nothing is wrong with the model; it is just drowning out the structure you were trying to read.
See what changed, on the diagram itself.
Schema history usually means a wall of migration files and a guess about what they did to the shape of things. Name a save point, pick any two, and the canvas draws the answer.
You, your team, and your agent. One canvas, live.
An MCP server and a skill ship with it. Your agent’s edits arrive through the same path a teammate’s do — so what it changes appears on everyone’s canvas as it happens, and your arrangement survives all of it.
The canvas is already open.
Just draw — or tell your agent to. No account, no card.
-- signing up takes 0 seconds. there isn't one.