One graph. Every repo.

DevGraph

Markdown-first architecture context for humans and AI.

Turn the READMEs and architecture notes you already maintain into graph.json, summary.md, Mermaid diagrams, Studio views, and agent-ready context with one command.

Read docsView on GitHub
Markdown blocks

Annotate services in docs

Build outputs

graph.json, summary.md, Mermaid

Agent context

Stable context across repos

Product Proof

Write blocks, run one command, ship context.

Stable
devgraph build
1# docs/architecture.md
2
3```devgraph-service
4name: payments-api
5type: backend
6repo: github.com/acme/payments-api
7depends:
8 - postgres
9 - auth-api
10links:
11 studio: /docs/introduction
12```
13
14$ devgraph build docs/architecture.md
15
16> Found 14 devgraph blocks in 6 files
17> Wrote .devgraph/graph.json
18> Wrote .devgraph/summary.md
19> Wrote .devgraph/system.mmd

Inputs

Existing Markdown, service blocks, and architecture notes across repos.

Outputs

Shareable docs, graph data, Mermaid diagrams, and Studio-ready context.

Real Product Captures

See DevGraph in the terminal and in Studio.

The homepage now shows the product instead of generic context language: build output from the CLI and a graph view from Studio on the same DevGraph brand surface.

CLI Capture

Build graph.json, summary.md, and Mermaid from Markdown blocks

DevGraph CLI build capture showing graph outputs written to .devgraph

Studio Capture

Inspect services, dependencies, and generated graph context visually

DevGraph Studio capture showing services and dependencies in a graph view

Turn Markdown into an architecture graph.

DevGraph scans devgraph blocks in the docs you already keep and builds a deterministic graph for engineers, onboarding, and AI workflows.

  • Track service boundaries and cross-repo dependencies
  • Capture APIs, environment variables, and ownership context
  • Generate graph outputs that stay close to the codebase
See generated outputs
summary.md (preview)
1# Project Summary
2
3| Service | Repo | Depends On |
4| --- | --- | --- |
5| mobile-app | mobile-app | backend-api, inference-api |
6| web-dashboard | web-dashboard | backend-api |
7| backend-api | backend-api | postgres, s3 |
8| inference-api | inference-api | model-runtime |
9
10Generated files:
11- .devgraph/graph.json
12- .devgraph/summary.md
13- .devgraph/system.mmd
14- .devgraph/agents/*.md

Build outputs your team and agents can both use.

Run one command and get a stack of durable artifacts for docs, reviews, diagrams, and agent sessions across the whole repo.

  • Write devgraph blocks next to the system docs they describe
  • Run 'devgraph build docs/architecture.md' to refresh context
  • Open Studio or ship the generated files directly into your workflows
See the build workflow
terminal
1$ devgraph build docs/architecture.md
2
3> Found 18 devgraph blocks in 6 files.
4> Building graph...
5> services: 14
6> dependencies: 32
7> Wrote .devgraph/graph.json
8> Wrote .devgraph/summary.md
9> Wrote .devgraph/system.mmd
10> Wrote .devgraph/agents/mobile-app.md
11
12✨ Done in 0.4s.

DevGraph is the architecture layer you trust first.

Start with deterministic structure and relationships now. Layer in decision history, incidents, and provenance as your context graph practice matures.

  • Today: Structure, relationships, and dependencies
  • Next: Decisions, incidents, and provenance
  • Build trustworthy context in layers
Read context graph direction
graph.json (context-ready preview)
1{
2 "nodes": [
3 {
4 "id": "mobile-app",
5 "type": "service",
6 "metadata": {
7 "framework": "react-native",
8 "repo": "github.com/acme/mobile-app"
9 },
10 "relationships": [
11 { "target": "backend-api", "type": "depends_on" },
12 { "target": "inference-api", "type": "depends_on" }
13 ],
14 "context": {
15 "adrs": [],
16 "incidents": [],
17 "provenance": "planned"
18 }
19 }
20 ]
21}

Connect the sources around your graph.

DevGraph starts with Markdown-first architecture context and can expand outward into the systems your team already uses.

See integration roadmap
001

Git & CODEOWNERS

Link repositories, ownership boundaries, and file-level context across services.

Read source mapping
002

Packages & API Specs

Track package manifests, OpenAPI contracts, and dependency edges in one place.

Read dependency docs
003

CI/CD & Infra

Connect pipelines and infra definitions from Terraform and Kubernetes manifests.

Read pipeline docs
004

Observability & ADRs

Bring in traces, errors, runbooks, and ADRs to enrich architecture context.

Read context docs

DevGraph makes your architecture legible before the next prompt.

Start from Markdown. Build one graph. Share the same architecture context with your team, your docs, and every AI session that touches the repo.

Read docsView on GitHub