Overview
Repolyze automatically generates visual diagrams to help you understand system architecture, data flow between components, and dependency relationships. These diagrams are interactive, exportable, and based on actual code analysis.Architecture Overview
The architecture diagram organizes components into layers:Component Layers
Frontend
Frontend
Client-side components, UI frameworks, and presentation layer:
- React/Vue/Angular components
- Page components and routing
- UI libraries and design systems
- Client-side state management
Middleware
Middleware
Request processing, authentication, and intermediate layers:
- API gateways
- Authentication/authorization
- Rate limiting and caching
- Request transformation
Backend
Backend
Server-side application logic and API endpoints:
- REST/GraphQL APIs
- Business logic
- Controllers and services
- Application servers
Service
Service
Microservices and background workers:
- Background jobs
- Message queues
- Scheduled tasks
- Service workers
Database
Database
Data persistence and storage layers:
- SQL databases (PostgreSQL, MySQL)
- NoSQL stores (MongoDB, Redis)
- Object storage (S3)
- Cache layers
External
External
Third-party services and integrations:
- Payment processors (Stripe)
- Email services (SendGrid)
- Cloud providers (AWS, Vercel)
- Analytics services
Component Cards
Each component displays:- Name - Component identifier
- Description - What the component does
- Technologies - Frameworks and libraries used (up to 3 shown)
- Layer indicator - Visual grouping by architectural layer
Data Flow Diagram
Visualize how data moves through your system with two view modes:Visual View
A structured grid showing:- Sources - Where data originates (user input, APIs, databases)
- Processes - How data is transformed (validation, computation, aggregation)
- Storage - Where data is persisted (databases, caches, files)
- Outputs - Where data is sent (APIs, UI, external services)
Diagram View
An interactive Mermaid flowchart that shows:- Nodes - Data flow components with type icons
- Edges - Directional arrows showing data movement
- Labels - Data type or transformation description
- Automatic layout - Clean, organized visualization
The diagram is dynamically generated and adapts to your system’s complexity.
Diagram Export Options
PNG Export
Download diagrams as high-resolution images:- Click the PNG button in the diagram toolbar
- Image is rendered at 2x scale for clarity
- Auto-downloads as
data-flow-[timestamp].png - Includes theme-appropriate background
PNG exports preserve the current theme (light/dark mode).
Code Export
Copy the Mermaid diagram code:- Click the Code button
- Mermaid syntax is copied to clipboard
- Paste into:
- README.md files
- Documentation sites
- Mermaid Live Editor
- GitHub markdown
Fullscreen View
Expand diagrams for detailed inspection:- Click the maximize icon
- View in large modal window
- All export options available
- Close with ESC key or close button
Dependency Graph
Understand how components depend on each other:Node Types
- Core modules - Main application components
- Shared utilities - Reusable helpers and functions
- External packages - Third-party dependencies
- Configuration - Config files and environment setup
Edge Types
- Direct dependencies - Solid lines for explicit imports
- Indirect dependencies - Dashed lines for transitive deps
- Labeled edges - Show import type or usage context
Interactive Features
Theme Support
All diagrams automatically adapt to your theme:- Light mode - Clean white backgrounds, dark text
- Dark mode - Dark backgrounds, light text
- Color consistency - Matches your site’s primary colors
Empty States
When diagram data isn’t available:- Clear messaging explaining why
- Icon indicating the missing diagram type
- Graceful fallback (no errors)
- Repository too small (< 10 files)
- No detectable architecture patterns
- Unsupported language/framework
- Analysis still in progress
Best Practices
Export for Documentation
Copy Mermaid code and include it in your project’s README or docs.
Share with Team
Download PNG diagrams to share in Slack, presentations, or wikis.
Track Changes
Re-analyze after refactoring to see architectural improvements.
Onboard Developers
Use diagrams to help new team members understand the codebase.
Next Steps
Health Scoring
Review quality metrics for your repository
Export & Share
Learn all the ways to share your analysis