Architecture Intelligence Platform

Understand any codebase in hours, not weeks.

ScreenTrace indexes your repositories into a live System Map: components, endpoints, services and the stored edges between them, each one traceable to the source line it was read from.

Get started Sign in
  • Built from your real code
  • Every edge links to source
  • GitHub sync, Jira links
  • Hosted or self-hosted
Pilot WorkspaceorderflowSample data
JS

Repositories

REPOSITORIES2
WITH GRAPH1
NODES1,308
EDGES3,412
UNRESOLVED3

  • orderflow acme/orderflow

    main @ 9f1c2a7

    Files 98Nodes 1,308Endpoints 12Unresolved 3Updated 2h

  • orderflow-mobile acme/orderflow-mobile

    main @ 41be0d3

    Files —Nodes —Endpoints —Unresolved —Updated —

Index runs

  • 9f1c2a7mainPublished2h ago · 3m 12s
  • e07b41cmainPublished1d ago · 3m 04s
  • 41be0d3mainRunningorderflow-mobile · started 40s ago

System Map

The published code graph, repository by repository

OverviewCanvas
Readymain @ 9f1c2a7Filter files…

Layers

    Click a layer to hide it · Drag a box to move it

    System Map

    The published code graph, repository by repository

    OverviewCanvas
    Readymain @ 9f1c2a7

      APIs

      Import and explore API definitions — structured documentation for every endpoint

      • POST/orders
        Create an order from the current cartorders
      • GET/orders/{id}
        Read one order with its payment stateorders
      • POST/orders/{id}/retry-payment
        payments
      • GET/health
        Liveness probeops

      POST/orders

      Create an order from the current cart

      Handler

      apps/api/src/orders/orders.controller.ts:27

      Consumers

      apps/web/src/api/orders-client.ts:18

      orderflow · apps/web

      Impact Intelligence

      What a branch or pull request reaches, measured from the graph

      Pull request #412 orderflow

      feature/payment-retry → main

      Requested 14 minutes ago · completed 13 minutes ago

      Medium riskCoverage: partialCompleted

      Branch comparison orderflow

      release/2026.10 → main

      Requested 3 hours ago · completed 3 hours ago

      Low riskCoverage: completeCompleted
      Direct dependents3
      Indirect (possible)7
      Endpoints2
      Tests1

      AI impact analysis has not run yet

      The numbers above show what changed and where it reaches; they do not say why it matters or what you should check. The AI reads only the evidence packet, never the repository.

      Analysis Workspace

      Central hub for product decisions, user flows, and feature reasoning.

      Search analyses...All Categories

      Board

      Work items by state

      Drag cards between columns

      To do 2

      ORD-231

      Retry failed payments

      2 nodes
      ORD-219

      Document /health

      1 endpoint

      In progress 1

      ORD-228

      Add order status endpoint

      3 nodes

      Done 2

      ORD-225

      Index worker handlers

      4 nodes
      ORD-212

      Shared OrderSchema

      5 nodes

      Visual Mapping

      Map your live app to its code

      LoadMapping onClick a region to see the code behind it

      Work Items

      Linked to Jira issues, read-only

      • KeyTitleStateLinked nodes
      • ORD-231Retry failed paymentsTo doPaymentsGateway, Stripe API
      • ORD-228Add order status endpointIn progressOrdersService, OrderRepository, orders
      • ORD-225Index worker handlersDoneOrderConfirmedHandler, SMTP
      • ORD-219Document /healthTo doGET /health

      Trace Console

      Send a request against a discovered endpoint

      Request

      POST

      {
  "cartId": "c_8f21",
  "paymentMethod": "pm_visa"
}

      Response 201 Created · 84 ms

      {
  "id": "ord_3141",
  "status": "confirmed",
  "total": 129.9
}

      Sample dataIllustrative sample repository · or click any item in the console sidebar

      Your whole architecture, one map away

      Connect a repository and ScreenTrace draws the System Map from the code: folders become areas, stored edges become counted lines, and every line can be opened down to the file and row it came from.

      • System Map
      • Source evidence
      • Endpoints
      • Impact Intelligence
      • Work items
      • Board
      • Visual Mapping
      • Trace Console
      • MCP
      • VS Code
      • Chrome capture
      • GitHub
      • Jira
      • Self-hosted
      • Whitelabel
      • Roles

      Also in the box

      • Work items and BoardWork items link to Jira issues, read-only; the Board keeps them moving by state.
      • Visual MappingCapture a screen with the Chrome extension and tie it to the code behind it.
      • Trace ConsoleSend requests against your endpoints from inside the workspace.
      • Agent accessMCP hosts and the VS Code extension authenticate with tokens scoped to read and sync.
      • Roles and permissionsOwner, Admin, Member, Viewer presets plus custom roles; grant only what you hold.
      • Self-hosted and whitelabelOne VM under your domain, your organisation name next to the mark.

      Run it where your code should live

      The same product in the cloud or as a single-VM install under your own domain.

      console.screentrace.app

      Cloud

      • Create a workspace in minutes
      • Connect GitHub repositories
      • Capability-based roles and agent tokens
      • Updates arrive automatically
      Get started
      Your own VM

      Self-hosted

      • One Linux machine with Docker Compose
      • Your domain, your database, your disk
      • Code, analyses and screenshots never leave it
      • Whitelabel workspace name
      Contact us

      Workspaces, custom roles, per-member permissions, GitHub and Jira integrations are part of the product in both deployments.

      Why ScreenTrace

      Architecture is read from code. Not remembered, not drawn.

      Every diagram your team keeps is a memory of the system, and memories drift. ScreenTrace reads the repository and writes down what is actually there.

      Every edge carries the file and line it came from. A claim about your architecture is either backed by source or it is not on the map.

      The AI never guesses from the repository. It reads an evidence packet ScreenTrace assembled, and says only what that evidence supports.

      Get startedSign in

      Frequently asked questions

      What ScreenTrace does with your repositories, and what it never does.

      What is ScreenTrace?

      An Architecture Intelligence Platform. It indexes repositories into a graph of files, symbols, endpoints and the stored edges between them, and presents it as a System Map with node focus, APIs, Impact Intelligence and work items.

      Does ScreenTrace change my code or my Jira?

      No. It reads repositories from GitHub and publishes graph snapshots. Work items link to Jira issues, but ScreenTrace never writes to Jira or to your repository on your behalf.

      Where does my code live?

      On the hosted console, in the ScreenTrace workspace you created. Self-hosted, on a single Linux machine under your domain: code, analyses and screenshots stay in that machine's database and disk.

      How accurate is the map?

      Every edge has a type, a certainty (exact, inferred, possible or dependency) and the source line it was read from. Unresolved references are counted and listed, not hidden.

      What does the AI read?

      Only the evidence packet of an analysis: the dependents, endpoints and tests ScreenTrace found around a diff. It never reads the repository itself.

      What happens when the branch moves on?

      The snapshot is marked as needing a new sync. Run a sync and the map is rebuilt from the current branch.

      How is access controlled?

      Owner, Admin, Member and Viewer presets, custom roles per workspace and per-member extra permissions. A permission can only be granted by someone who holds it.

      How do agents and editors connect?

      With personal access tokens scoped to read and sync, issued from Settings › Agent access. MCP hosts, the VS Code extension and the Chrome capture extension use them.