Skip to main content
Xerg is a live map of everything your team runs: your repos and the apps in them, your cloud resources, and the outside services in between, like Stripe, Sentry or OpenAI.
A Xerg map: repos as areas, apps inside them, and the outside services they use around themA Xerg map: repos as areas, apps inside them, and the outside services they use around them

​
How it works

  1. Connect GitHub. Xerg reads your config files (package manifests, deploy configs, Terraform, CI workflows, example env files) and scans your source files for imports and API hostnames. It maps every repo, app and outside service it finds.
  2. Confirm what’s live. Connect AWS, Vercel, Stripe and more to see what each account actually runs, including what your code never mentions.
  3. Ask, share, plug in your agents. Ask “what breaks if Stripe goes down?”, invite your team (viewers are free), and give Claude Code or Cursor the same map over MCP.
Xerg only reads. It never changes your code or your accounts. It downloads config files, example env files and up to 300 source files per repo (source files can be turned off in setup), and keeps only what it finds in them: the service, the file and the line. It never keeps code or env values, only variable names.

Quickstart

Sign up with GitHub and see your map.

What Xerg reads

The files it reads, and what it keeps.

Connect a service

Confirm what’s live. Xerg only reads.

Coding agents

Give Claude Code, Cursor and other agents the map.