Software Architecture Viewer & Advisor — bRRAIn Docs

Connect any GitHub repos, get a living architecture map and AI-driven advisor for your codebase.

Software Architecture Viewer & Advisor

Connect your code repositories and get a living architecture map plus an AI advisor that reasons over the actual code.

What it does

  • Live architecture map — modules, services, packages, dependencies, owners, hot zones.
  • Cross-repo navigation — even when your codebase spans dozens of repos.
  • Code-aware Handler — ask "where do we encrypt user data?" or "which services touch the billing table?" and get answers grounded in the code.
  • Drift alerts — flags when reality diverges from declared architecture.
  • Dependency hygiene — outdated packages, vulnerable dependencies, license-compatibility issues.

Use cases

  • Onboarding new engineers ("show me the auth flow").
  • Architecture review preparation.
  • Pre-refactor impact assessment.
  • Continuous documentation of a codebase that's outgrown its docs.
  • Vulnerability response ("which of our services are affected by CVE-XXX?").

Installing

Per-organization subscription. Pricing tiers depend on number of repos and total LOC indexed.

After install:

  • A code-graph view mounts in your Console.
  • The first-time wizard guides you through connecting your first code host (GitHub, GitLab, Bitbucket, Azure DevOps, self-hosted Git).
  • A first scan runs in the background; you can navigate the partial graph as it builds.

Connecting repos

For GitHub:

  1. Install our GitHub App on your organization (or on specific repos).
  2. Pick which repos to index.
  3. Pick which branches (default: every default branch + active feature branches).

For other hosts the connection flow is similar — we use OAuth where supported and personal access tokens otherwise.

Indexing is incremental and tracks every push.

Architecture map

The map renders:

  • Repos as outer containers.
  • Services / modules / packages as nodes.
  • Dependencies as edges (typed: import, HTTP, message-bus, etc.).
  • Owners as overlay layers.
  • Hot zones (high-change-frequency files, recent incidents).

Filter, search, expand, collapse. Save curated views for re-use.

Code-aware Handler

Ask the Handler questions in plain English:

  • "Where do we encrypt user data?"
  • "Which services depend on the user-profile table?"
  • "Who's the most-recent author of the order-processing service?"
  • "What was the design intent for the legacy routing/v1 package?"

Answers cite the relevant files and line ranges. Click through to your code host.

Drift alerts

If the code starts to drift from declared architecture (a new dependency edge appears that wasn't in the architecture decision record, a service gets owners outside the declared team), an alert fires.

Drift detection is configurable — strict for compliance-bound projects, lenient for greenfield exploration.

Dependency hygiene

Continuous scan against:

  • Outdated packages (semver upgrade availability).
  • Known CVEs (NVD plus our own enrichment).
  • License compatibility (your declared license policy vs. actual dependency licenses).
  • Abandoned dependencies.

Findings surface as a sortable / filterable list with one-click "open issue / open PR" affordances.

Full-text search across every indexed repo, with semantic boosting:

  • Symbol search.
  • Path-and-line search.
  • Natural-language search via the Handler.

Search respects the access scopes of your code-host integration; you only see what your access permits.

Scopes required

  • Read and write in the extensions/code-architecture zone.
  • Read access to the code-host integrations you wire up.
  • LLM access via the per-organization Handler.

Where to next