Skip to main content
Xerg helps your team answer questions like “Which apps reference Stripe?” and “Where has this release been observed?” It maps selected repositories, the services found in them and resources reported by connected accounts. Each answer depends on which sources you have connected and when they were checked.
A Xerg graph: repos as areas, apps inside them, and the outside services they use around themA Xerg graph: repos as areas, apps inside them, and the outside services they use around them

​
How it works

  1. Start with a repository. Set up a workspace, scan a repo, then open a service on the graph to see the file that led Xerg to it. You can do this in your browser without installing a CLI or connecting a cloud account.
  2. Check the evidence. An account connection can show a resource your code never mentions. To check which revision a domain serves, configure a production source. A code reference or an account listing alone cannot answer that question.
  3. Follow a change. When change recording is enabled, open Changes to compare the intended release with the observations received. See which environments still need checking. Ask about recorded dependencies in the app or give a coding agent access over MCP.
Inventory connections read your accounts. Repository scans keep findings and references. If you separately enable a documentation catalog, Xerg also stores the Markdown you select. See Security and data.

Quickstart

Sign up with GitHub and see your graph.

What Xerg reads

The files it reads, and what it keeps.

Connect a service

See which resources the account reports.

Coding agents

Give Claude Code, Cursor and other agents the graph.