Open source alternative to CodeDashboard and Eraser.io
Last verified
Visualize any GitHub repository as an interactive architecture diagram. MIT licensed, powered by AI, with Mermaid export and private repo support.
GitDiagram produces an architecture overview of a repository in one browser visit, no local checkout needed. Engineers starting a new job or picking up an inherited project can see how the major components connect before writing a single line of code.
Skip if the codebase is private and your organization restricts sharing tokens with external services. Also skip if the repository is very small (under 20 files); a directory listing is faster.
Before a planning session or architecture review, paste the repository URL and get a component diagram without pulling up the code. The diagram exports as PNG for use in slides or design documents.
Skip if you need an editable, collaborative architecture diagram with custom shapes and annotation layers. Eraser.io or Miro are better fits for that workflow.
Click any node in the generated diagram to jump directly to the relevant file on GitHub. When evaluating a project to contribute to, this provides faster orientation than navigating the repository tree manually.
Skip if the project already includes a well-maintained architecture diagram in its documentation; reading the existing diagram will be faster.
Diagram any public GitHub repository to quickly assess what a dependency or third-party library actually contains. The architecture view shows how a library is internally structured before committing to using it.
Skip if your security or compliance workflow requires air-gapped tools. GitDiagram sends repository content to an external AI API.
Understanding an unfamiliar codebase takes hours. A large repository may span hundreds of files across nested directories, and the README typically describes the project's purpose rather than mapping how its components interact. Engineers onboarding to a new team, reviewing a pull request touching many files, or contributing to an open source project for the first time often spend their first hours reading directory trees and tracing imports.
Architecture diagrams, when they exist at all, go stale quickly. Teams document how a system works at launch, then stop updating as features are added. By the time a new contributor arrives, the diagram shows an older version of the system and the code tells a different story. There is no lightweight path to an accurate, current picture of how a repository is structured without actually reading through it.
Feeds the repository tree, README, and bounded source excerpts to a language model that returns a system-level graph with groups, nodes, edges, and shapes. Generates a structural overview rather than a folder tree, so the diagram shows how components relate rather than where files live.
Every node in the generated diagram links to the real file or directory on GitHub. Click a component to open its source in a new tab. Links are validated against the actual repository before the diagram renders, so every link points to something that exists.
The diagram generates progressively rather than waiting for the full result. A short architecture overview streams first, followed by the graph nodes and edges as they are produced. Successful diagrams are cached by repository, so repeat visits load the saved artifact without triggering another model call.
Provide a fine-grained GitHub personal access token in the browser header. The token is sent only with the relevant same-origin API request and is never embedded in public diagram links. Private diagrams are stored in a separate R2 namespace derived with a server-side secret.
Copy the raw Mermaid source to paste into any editor that supports Mermaid diagrams, or download the rendered diagram as a PNG image. Exporting the Mermaid source lets you version-control the diagram or edit individual nodes and edges manually.
The default managed cloud version uses OpenAI for generation. Self-hosted deployments can configure OpenRouter as the AI provider instead, which opens access to a wider range of models without requiring a direct OpenAI account. User-supplied API keys retain standard service tier.
Both tools help engineering teams work with architecture diagrams, but they serve different workflows. GitDiagram generates diagrams automatically from a GitHub repository; Eraser.io is a collaborative diagramming editor where engineers author and maintain diagrams manually alongside technical documentation.
| Feature | GitDiagram | Eraser.io |
|---|---|---|
| License | MIT | Proprietary |
| Self-hosting | Docker (disaster recovery path) | No |
| Diagram authoring | AI-generated from repo | Manual with shapes and connectors |
| Private repo support | Yes, via GitHub token | Not applicable |
| Export formats | Mermaid source, PNG | SVG, PNG, PDF |
| Pricing | Free (public repos, hosted) | Paid plans |
| Collaboration | Not built in | Core feature |
| Source path validation | Yes, against actual repo | N/A |
GitDiagram is the better choice when the goal is a fast, disposable architecture overview of an existing repository with no setup time. It takes a URL and returns a diagram in seconds, making it useful for onboarding, quick code reviews, and exploring unfamiliar dependencies. Because the diagram is generated automatically, it reflects the current state of the repository on the next generation without any manual upkeep.
Eraser.io is the better choice when a team needs persistent, collaborative architecture documentation with custom layouts, multiple diagram types, and the ability to annotate and edit individual elements. Its diagramming canvas lets teams build canonical architecture documents that they refine over time, which is a workflow GitDiagram does not support. Teams maintaining living architecture documents with multiple contributors are better served by Eraser.io's collaborative workspace.
Local development setup uses Bun with Cloudflare R2, Upstash Redis, and an AI provider configured in the environment file.
```bash
git clone https://github.com/ahmedkhaleel2004/gitdiagram.git
cd gitdiagram
bun install
cp .env.example .env
bun run dev
```Public repository diagrams on the hosted version at gitdiagram.com are free. The source code is MIT licensed, so running your own instance is also free, though you supply your own API keys for Cloudflare R2, Upstash Redis, and an AI provider. Heavy usage on the hosted version may be subject to rate limits.
Yes. Select Private Repos in the header and provide a fine-grained GitHub personal access token with read access to the target repository. The token is sent only with the relevant same-origin API request and is never stored in the diagram URL or public diagram links.
Yes. The repository includes a Dockerfile and Railway configuration. Self-hosting requires a Cloudflare R2 bucket for diagram storage, Upstash Redis for rate limiting, and an OpenAI or OpenRouter API key. The README describes the Docker path as a disaster recovery recipe; expect to configure multiple services before the full stack runs.
The managed cloud version uses GPT-5.6 Luna at medium reasoning by default. Self-hosted deployments can configure OpenRouter to use a different model. Users can also supply their own OpenAI API key, which uses standard service tier and their configured model.
Diagrams can be exported as raw Mermaid source or downloaded as a PNG image. The Mermaid source can be pasted into any tool that renders Mermaid diagrams, including GitHub markdown files, Notion, and popular diagramming editors.
Alternative to
CodeDashboard
Review code changes as architecture maps, not line diffs
Alternative to
Eraser.io
Local-first AI diagramming tool for developers and builders
Alternative to
Lovable
Local, open-source AI app builder with your own API keys
Alternative to
Dust
Open source AI workspace with sandboxed apps and Gatekeeper security
Typed errors, DI, and concurrency for TypeScript
Alternative to
AWS Amplify
Open source Apple SDK for Firebase auth, data, push and crashes
Featured
Alternative toClaude Managed Agents
Open-source agent deployment API. Self-host or use Omnara Cloud.
Alternative to
Superhuman
AI email assistant that drafts replies and clears your inbox
Alternative to
Grok Bot
AI teammates you own: your keys, your model, your machine.
The projects we add and every new guide. Free, unsubscribe any time.
Claude Code to 
OpenCode
Jira to 
Windshift
Notion to 
AppFlowy
Slack to 
Mattermost
Linear to 
GitLab
Wispr Flow to 
Handy
CapCut to 
Concat
Grok Bot to 
rakazo
Superhuman to 
Inbox Zero
Airtable to 
AITable
Muse to 
OpenClaw
GitHub Copilot to 
Cline
Datadog to 
Netdata
Microsoft Teams to 
Rocket.Chat
Pinecone to 
Qdrant
Zapier to 
n8n
Devin AI to 
OpenHands
Firebase to 
Supabase
1Password to 
KeePassXCConfluence to 
Docmost
Contentful to 
Strapi
Adobe Premiere Pro to 
Shotcut
ChatGPT to 
AnythingLLM
LangSmith to 
Langfuse
