Public Alpha

Know your codebase
before you prompt.

Start from existing READMEs across repos. Generate one architecture graph for the whole project.

Read docs
session: local // graph //
stable
1# Multi-Repo Project Architecture
2
3```devgraph-service
4# story placeholder:
5# title: Cleft Care Research Platform
6# repos:
7# - github.com/ameyalambat128/cleftcare
8# - github.com/ameyalambat128/cleftcare-dashboard
9# - github.com/ameyalambat128/cleftcare-api
10# - github.com/ameyalambat128/cleftcare-ohm-api
11name: mobile-app
12type: react-native
13repo: github.com/acme/mobile-app
14depends:
15 - backend-api
16 - inference-api
17links:
18 web: github.com/acme/web-dashboard
19 api: github.com/acme/backend-api
20 inference: github.com/acme/inference-api
21dataflow:
22 - record audio in app
23 - upload samples via backend-api
24 - run analysis via inference-api
25```
26
27$ devgraph build docs/architecture.md
28
29> Found services across 3 repositories
30> Wrote .devgraph/graph.json
31> Wrote .devgraph/summary.md and .devgraph/system.mmd
1: input+2: build3: outputs

What DevGraph knows right now.

DevGraph turns architecture notes into a deterministic graph with outputs for humans and AI workflows.

  • Service boundaries and cross-repo dependencies
  • API routes and environment variables
  • Generated artifacts for onboarding and automation
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

How it works in practice.

Annotate key services in existing READMEs, run one command, and use outputs in docs, Studio, and agent workflows.

  • Add devgraph blocks in Markdown docs
  • Run 'devgraph build docs/architecture.md'
  • Use outputs in .devgraph and open Studio
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 and context graphs.

DevGraph gives you the architecture layer now. Context graph workflows extend it with decision history and operational provenance.

  • 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}

Connectable sources.

Connect the sources developers already use and unify them into one graph that is easier to navigate and query.

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

Map your repo in minutes, not meetings.

Start with the docs you already have. Build once. Share architecture context with your team and every agent session.

Get startedView on GitHub