Put your production graph to work.
Your agents can write code. Do they know the system?
Code is only part of the picture. Xerg gives agents and engineers shared context about the systems it connects to, so they can investigate dependencies, review proposed changes and spend less time piecing the same knowledge together.
The graph starts with your code and accounts.
No catalog to build, no YAML to maintain, nothing to install.
Connect GitHub.
Xerg reads your config files, import lines and variable names to connect apps, cloud resources and services in a graph you can explore and question.
Add account evidence.
Connect AWS, Vercel, Stripe and 16 more. Add account resources and details your code may not reveal. Xerg only reads.
Share the context.
Invite your engineers, and anyone else as a free viewer. Give Claude Code or Cursor the same graph to query over MCP.
Production knowledge your whole team can use.
Investigate, review and get up to speed.
Plan changes with context
Trace recorded dependencies and source references before a key rotation or vendor switch, then review what needs attention.
Give agents shared context
Claude Code, Cursor and other agents can query Xerg over MCP to investigate dependencies. Engineers can inspect the same evidence when reviewing proposed changes.
$claude mcp add --transport http xerg https://mcp.xerg.ai✓ xerg connected · 10 toolsyou › rotate the Stripe keyagent → where_used("STRIPE_SECRET_KEY")api · billing-worker · stripe webhookagent › I found 3 references to review.
Get to the cause faster
Inspect dependencies, recorded code owners and changes between saved graphs. Xerg keeps a copy of the graph for each day it’s saved, for 180 days.
Support security reviews
Build your system and vendor list for SOC 2 and security questionnaires from repository and account evidence. Security and compliance join free.
Find what nobody wrote down
Review account resources with no reference found in scanned code, alongside available 30-day spend for AWS, Azure, OpenAI and Anthropic.
Get new people up to speed
New engineers, agents and engineering leaders can explore the same graph, trace dependencies and find the relevant code.
Agents read the graph. People make the call.
Your agents are teammates now, so Xerg treats them that way. Every agent key is made by a person on your team, and each member’s agents come with their seat.
Read.
Agents can query the graph and its evidence with 9 tools that never execute external changes: impact, where_used, owners, what_changed and more. Keys allow 600 calls an hour and expire after 90 days.
Act, with approval.
Agents open the pull request or the ticket. A person on your team approves it.
Govern.
Decide, and audit, what each agent can touch and spend.
Read-only by design. Free to start.
Free for one person and their agents. Then $20 per member a month, billed annually, with each member’s agents included. Viewers are always free, you pay only for active members, and no card is needed to start.
See pricing →Xerg only reads, with the narrowest access each service offers. It never changes anything in your accounts.
No source code or scanned secret values kept. Only variable names, and the service, file and line where something was found.
Know what you connect. Review what Xerg reads, stores and shares before connecting your accounts. Read the security docs →
Before you connect GitHub.
What is Xerg?
Xerg connects your repositories, cloud resources and services in a shared production graph. Engineers explore it visually, while coding agents query it through MCP. Both can inspect the evidence to understand dependencies and plan changes.
How does Xerg find what we run?
It reads config files, like package manifests, Terraform, deploy configs, CI workflows and example env files, and scans source files for import lines and API hostnames. Connect an account like AWS, Vercel or Stripe to add resources and account details beyond repository discovery.
Does Xerg read our secrets or our code?
The scanner skips real .env files and keeps variable names, never their values. It scans up to 300 source files per repo for imports and API hostnames, and keeps only the service, file and line, never the code. Separately enabled documentation sources retain only the cataloged Markdown, with revision citations. Account connection tokens are stored encrypted.
Can Xerg, or our agents, change anything through it?
Xerg’s connectors and MCP tools never execute external changes. An operator can separately configure a trusted gateway that requires scoped verification before its host runs a fixed command. Installing MCP alone does not enforce that gateway.
How do coding agents use Xerg?
Add Xerg’s MCP server to Claude Code, Cursor or any MCP client with a workspace key. Your agent gets 10 tools to inspect dependencies, retrieve cited documentation, read production evidence and request scoped verification. The tools never execute external changes.
Do agents cost extra?
A member’s agents don’t: they come with the member’s seat, and lookups are never charged per call. An agent with no person behind it, like a CI job, gets its own agent seat, $10 a month billed annually.
How is Xerg different from Backstage or Port?
Xerg starts with a graph from selected repositories and connected accounts, including recorded references to outside services. Engineers and agents query that evidence. Compare coverage, setup effort and the questions each product answers on your own stack.
How much does Xerg cost?
Free for one person and their agents. Team is $20 per member a month billed annually, with each member’s agents included. Viewers are always free.
Is the graph guaranteed to show all of production?
No. Production context records selected sources, serving deployments, observation times and coverage gaps. Optional checks compare selected journeys with docs and bot answers, or inspect runtime and integration evidence. They require configured sources and runners; unconnected systems and unchecked behavior remain unknown.
Does Xerg support GitLab or Bitbucket?
Yes. Hosted scans support GitHub, Bitbucket Cloud and GitLab.com. Self-managed GitLab and Bitbucket Server are not supported.
Put your production graph to work.
Connect GitHub and give your team shared context. Xerg only reads.
Sign up with GitHub Or try it on any public repo, no sign-up →