Code to Diagram

Rekhic enables developers to upload project source files or directories and automatically detect their architectural components, backing databases, and service boundaries.

The Workflow

text
         Source Code Files / Manifests
                      │
                      ▼
            Local Browser Analysis
   (Client-side AST & Heuristic Parsers)
                      │
                      ▼
            Architecture Detection
  (Technologies, Services, DBs & APIs Detected)
                      │
                      ▼
             Architecture Preview
                      │
                      ▼
                 Rekhic Canvas

Local Processing Guarantee

Privacy Notice: All source code uploaded or pasted into Rekhic is analyzed locally in your browser runtime.

Your source code is never uploaded to, transmitted across, or stored on any Rekhic backend servers. Parsing takes place client-side using JavaScript AST analysis and regex pattern matchers.

Supported Manifests and Frameworks

Rekhic's local analysis engine recognizes common package manifests and structural conventions across multiple ecosystems:

Ecosystem	Manifests Inspected	What Rekhic Detects
Node.js / TypeScript	`package.json`, imports	Next.js, Express, NestJS, Prisma, Mongoose, TypeORM
Java / Spring	`pom.xml`, `build.gradle`	Spring Boot, JPA, Hibernate, Kafka, PostgreSQL, MySQL
Python	`requirements.txt`, `pyproject.toml`	FastAPI, Django, Flask, SQLAlchemy, Celery, Redis
Containers & Infra	`docker-compose.yml`, `Dockerfile`	Services, networks, database containers, ports
Go	`go.mod`	Gin, Echo, GORM, database drivers

In addition to manifest files, Rekhic inspects file system paths (e.g. controllers/, routes/, models/, services/, schemas/) to infer application layers and data entities.

Limitations & Best Practices

To set clear engineering expectations:

Heuristic, Not Omniscient: Rekhic uses heuristic pattern matching. It does not compile your code, execute binaries, or construct full type-checker symbol graphs.
Dynamic Invocations: Dynamic runtime dependency injection or reflection across distributed microservices cannot be completely inferred from static source files.
Review Before Treating as Authoritative: Generated architecture diagrams provide an initial structural scaffold designed to save you hours of manual box-drawing. Engineers should always review, refine, and verify generated topologies before treating them as production truth.

Next: Learn how to visualize public repositories in GitHub Repository to Diagram.

README to Diagram

GitHub Repository to Diagram