OpenDiagramWhich GitHub repositories can I import?
The current import flow supports public repositories. Connect GitHub, then choose from the repositories available in the picker or enter an owner/repository name.
Architecture from existing code
Turn a GitHub repository into an architecture workspace.
Move beyond folder trees and scattered README files. Import a public repository, identify its main parts, and review the result as a connected system.
Import a repositorySource
GitHub repo
src / services
package.json
infra / …
Mapping system…
Your mascot does the mapping
You review · they assemble
Output
Live diagram
API
Auth
DB
Queue
Repository import flow
Trace the system without reconstructing it by hand.
1
Connect GitHub
Authorize GitHub for repository access. OpenDiagram currently lists public repositories available to your account.
2
Choose the codebase
Search by owner and repository name, then select the project whose architecture you want to understand.
3
Open the workspace
OpenDiagram reads repository structure, detects services and dependencies, and prepares a project for generated diagrams and documentation.
A map to question—not a claim that the code explains itself.
Repositories reveal structure, but architecture also lives in runtime behavior, operational constraints, external services, and decisions that may never appear in source files.
Use the generated workspace to find those gaps. Correct the draft, add missing context, and keep the system view useful as the code changes.
Explore editable diagram features →Repository-import questions
Does OpenDiagram change my repository?
No. Repository import reads project context to prepare an OpenDiagram workspace. It does not commit changes or write files back to GitHub.
What should engineers review after import?
Check detected service boundaries, dependencies, runtime relationships, external systems, and anything inferred from conventions rather than explicit configuration.