Skip to main content
Architecture Explorer analyzes your codebase and generates an interactive visualization of its structure - modules, dependencies, handler call graphs, and more. It runs inside your workspace and serves a web-based UI you can access from your browser.

​
What It Does

Architecture Explorer scans your project files, builds a dependency graph, and renders it as an interactive web application. You can explore:
  • Module structure - how files and directories relate to each other
  • Dependency graphs - which modules import or depend on others
  • Handler call graphs - trace the flow from HTTP handlers through business logic
  • Code metrics - file sizes, complexity indicators, and module boundaries

​
Supported Languages

Architecture Explorer scans up to 5 projects at a maximum directory depth of 25. For monorepos, it discovers and analyzes each project (crate or package) independently.

​
Availability by Image

Architecture Explorer is not pre-installed on any image, so you need to install it first.
Use the dev template if you want a richer development environment for working alongside Architecture Explorer. See Images & Templates for details.

​
Installation

Install Architecture Explorer before launching it.

​
Start the installation

The install runs asynchronously and prints a job id you can poll.
See Install Tool for the full response schema.

​
Poll for installation status

Installation takes 1-3 minutes depending on the workspace image. Poll with the job id from rig tools install until the status is installed.
See Installation Status for the response schema.

​
Installation complete

Once installed, Architecture Explorer is ready to launch.

​
Launching Architecture Explorer

After installation, launch the tool.
See Launch Tool for the response schema.

​
Accessing the Visualization

Once launched, Architecture Explorer serves a Vite development server on port 5174 inside the workspace. It’s accessible at:
Open this URL in your browser to interact with the visualization.
The arch- prefixed subdomain is created automatically when you launch Architecture Explorer. You don’t need to create an app route manually.

​
What you’ll see

The visualization includes:
  • Project overview - list of all detected projects with their type (Rust crate, Node.js package)
  • Dependency graph - interactive node graph showing how modules connect
  • File tree - expandable tree view of the analyzed directory structure
  • Call graph - for Rust projects, trace handler functions through layers of business logic
  • Search - find specific modules, functions, or files across all analyzed projects

​
Stopping Architecture Explorer

When you’re done, stop the tool to free up resources.
See Stop Tool for details.

​
Complete Example: Analyze a Rust Project

This walkthrough clones a Rust project into a workspace and visualizes its architecture. 1. Create a workspace with the dev image rig workspace spawn creates the workspace from the dev template, boots it, and waits until it’s ready:
2. Clone your project SSH into the workspace and clone the repository you want to analyze:
3. Launch Architecture Explorer
Then open https://arch-<workspace-id>.rigbox.dev in your browser. 4. Explore the visualization Open https://arch-<workspace-id>.rigbox.dev in your browser. Architecture Explorer will scan the cloned project, detect Cargo.toml, and build the dependency and call graphs. 5. Stop when done

​
Tips

For a richer development environment, use the dev template. Install Architecture Explorer once and launch it whenever you need it.
Architecture Explorer works best with well-structured projects that have clear module boundaries. Flat file structures with hundreds of files in one directory produce less useful visualizations.
Architecture Explorer consumes CPU and RAM while running. If your workspace has limited resources (e.g., 512 MB RAM), consider stopping other services before launching.

​
Next Steps