Design your architecture with your AI.

Your agent reads the diagram, answers questions, and proposes changes you approve.

Open Merid free to start
claude-code · proposal
+ order_status: "refunded"
+ orders.status → order_status
ApplyReject
sofia · review
Why does checkout hit the cache directly?
agent — it doesn't: writes go through the gateway. Edge depends_on · sessions starts there.
Merid editor showing a commerce architecture: storefront, gateway, services, and a live database schema chip

The diagram answers back

Ask your system anything.

nimbus-commerce6 nodes · 5 edges
charges Storefront FRONTEND API Gateway SERVICE Orders Service SOLE CONSUMER Stripe IF DOWN? Orders DB DATABASE Session Cache DATABASE
would be impacted no path to Stripe answered from 5 edges 
you › what breaks if Stripe
goes down?

agent › Only checkout.

Orders Service is Stripe's single
consumer (depends_on · charges) —
new orders can't take payment.

✓ unaffected: browsing, sessions,
reads from the orders DB. Nothing
else touches Stripe.

you › ▋

The answer isn't a guess — it's read off the edges you drew. A diagram in a wiki is a screenshot; this one is a live graph, so "what breaks", "who calls this", and "where do we touch PII" are queries, not archaeology.

MCP · one connection, the whole system

Your agent sees the end-to-end picture.

$ claude mcp add --transport http merid \ https://app.merid.dev/mcp \ --header "Authorization: Bearer <token>" ✓ merid connected · 10 tools Works with Claude Code, Claude Desktop, and any MCP-compatible agent.
you › add a refunds flow to checkout ⚙ get_graph(nimbus-commerce) → 6 services ⚙ get_graph(commerce-schema) → orders, users… ⚙ propose_changes(…) + Refunds Service → Stripe · refunds API + refunds table · FK → orders.id + order_status: "refunded" agent › Proposed — services and schema in one change. Review it in Merid.
1Create a token in Merid 2Connect once from your terminal 3Every project you can open, it can too

An agent in your repo sees one repo. Connected to Merid, it reads the system you actually run — every service, table, and relationship — before it writes a line. That's context no codebase can give it.

Why Merid

What that gets you.

01

Your AI knows your architecture

“What talks to the orders DB?” Ask in plain language and get answers grounded in the diagram — onboarding and incident triage stop depending on whoever drew it.

02

Reviews that don’t wait on you

Reviewers comment on shapes. Your AI replies with context, attaches a fix proposal to the thread, and flags you only when a question needs the author.

03

AI edits arrive like pull requests

Your agent proposes the diagram update — you apply or reject in one click. Nothing lands without you; everything can be reverted.

04

Architecture and database design together

Services on one sheet; tables, foreign keys, and enums on another — linked into the same diagram, reviewed in the same loop.

05

Works with the AI you already use

Claude Code, Claude Desktop, or any MCP-compatible agent connects with one config entry. No export step, no lock-in.

Pricing

Free to start. Pay when it sticks.

Free
$0
  • 3 projects, unlimited sheets
  • Unlimited viewers & commenters
  • Full AI loop — agent access, proposals, reviews
  • Architecture + database schema sheets
Start free
For teams Pro
$12 / editor / month
  • Unlimited projects
  • Everything in Free
  • Viewers & reviewers stay free — always
  • Priority support
Start free, upgrade in app

We charge the people who build diagrams, never the people who review them — share with your whole team without counting seats.

Your architecture changes every sprint. Now the diagram keeps up.

Open Merid