REST and gRPC endpoints
Method, path, params, responses and streaming modes are first-class cards on your canvas.
Architecture docs
that stay alive
Define each service, database and API once, then use it in every diagram. When you change it, every doc that uses it changes, and you can see what depends on it.
No credit card required
Dispatch Service
ReplacesWhiteboard photosStale Lucid and Miro boardsWikis nobody updatesDiagrams drawn by hand
Your diagrams lie within a week
Whiteboard photos, stale boards, and wikis nobody updates. The cost is real: slow onboarding, bad decisions, and tribal knowledge locked in a few heads.
Not just boxes and arrows
Use elements that describe your system, from an API response to a database relationship.
ERDs and sequence diagrams
Model tables with typed columns, keys and crow's-foot cardinality, then lay out the calls between services step by step, on the same canvas.
Cloud architecture
Group real AWS services into accounts, regions, VPCs and subnets to show where your system runs.
Treat your architecture docs like code
References and embeds
Reference a service or a whole document instead of copying it. Embeds render the source live, so one change shows up everywhere it is used.
An IDE for your architecture
Open every document you need side by side in tabs, jump to any doc with Ctrl+O, and follow a reference straight into the doc it points to.
Work across architecture docs
Let your agent read and update your docs
Example conversation
Add a refunds service that reads from the bookings database
- Checked the Dispatch Service doc
- Bookings DB is used by 3 docs
- Drew Refunds Service, linked to Bookings DB
Keep diagrams and code in the same workflow
Living diagrams
Draw services, API endpoints and database tables on the same canvas. Edit their details without redrawing the diagram.
Learn moreSmart references
Reference one object across your docs. Open a database to see its direct and downstream dependencies.
Learn moreYAML and Git
Edit diagrams as YAML, keep the YAML in Git, and review changes in a pull request.
Learn morePR drift check
Map code paths to architecture docs in .archdocs.yml. Run the GitHub Action to flag pull requests that change code without updating its docs.
Learn moreReal-time collaboration
Edit a document together, leave comments, and review earlier versions.
Learn moreWhy I built ArchDocs
I built ArchDocs so a service can be defined once and used in every document that needs it.
Aylon, founder of ArchDocs
Read my noteFrequently asked questions
Is it free?
Yes. ArchDocs has a Free plan. Paid plans add higher limits and features for larger teams.
See pricing and plan limitsWhere is my data stored?
Architecture documents are stored in PostgreSQL. The API runs on DigitalOcean, and the web apps run on Cloudflare Workers.
Can I export?
You can download diagrams as SVG, PNG or PDF. You can also copy a diagram as YAML from the editor.
How is this different from Lucid, IcePanel or Structurizr?
ArchDocs lets you define a service, database or API once, reference it across documents, and see what depends on it. Diagrams also have YAML you can review in Git. If you only need a standalone sketch, try the free editor before setting up a workspace.
Does it work with my AI tools?
Yes, if your client supports remote MCP servers with OAuth. Connect to https://api.archdocs.io/mcp and sign in through your browser. The agent can read and update your architecture docs.
Read the MCP setup guideStart documenting in five minutes
Create a free account and start documenting your architecture.
No credit card required