Rift-code

Rift-code is an architecture diagram tool that turns your GitHub repo into a visual architecture map in seconds. Rift-code maps a GitHub repository into an interactive architecture diagram, with user flows and an Ask Lens feature that answers questions about the code and returns written explanations with visuals.

Rift-code is a code visualization platform that connects to your GitHub repositories and produces an architectural map of the codebase rather than making you trace files by hand. The output is an interactive diagram with layers such as clients, gateway, backend, data and external services. Nodes can be clicked to drill down, and the map updates as a live view of the architecture. The stated goal is to let developers see structure instead of reading it line by line. A second capability is Ask Lens, which accepts natural language questions about the repository and returns written answers paired with visual diagrams. Typical uses named on the site are deep-dive analysis, onboarding new team members and planning features. Rift-code also covers user flows, so the map can show how a request moves through the system, not just how the code is organized. The vendor positions the product around impact analysis before refactors and around helping teams understand how a monorepo fits together. The workflow is GitHub-centric. A user connects an account, scans a repository, and receives the map. The homepage advertises unlimited repository scans at $1.99 per month, with the first scan free. Public sample repositories (openclaw, launchkit, bolt.new, pezzo and excalidraw) can be opened as architecture maps without sign-in or credits, which gives a reliable way to judge output quality before connecting anything. Supported languages and package managers are covered in the FAQ, as are private repository use and access revocation, though those specifics are not listed on the homepage. The product sits in the same general space as code intelligence and dependency graph tools. Its difference is the emphasis on a readable architecture diagram plus question answering, rather than file-level navigation alone. It suits developers joining an unfamiliar codebase, tech leads preparing refactors, and teams that need a shared picture of a system. The team quotes on the homepage come from users citing monorepo comprehension, faster onboarding and fewer production issues during impact analysis. Budget is low relative to most developer tooling, and the plans are monthly.