Skip to main content
No. Xerg downloads example env files and keeps only the variable names, never the values, and it never downloads real .env files. Keys you paste to connect a service are encrypted and only used to read that account. See Security and data.
It scans it. Xerg downloads up to 300 source files per repo, none over 100 KB, and scans them for imports and API hostnames, to find services called with no package or env variable. It keeps only the service, the file and the line, never the code. Owners and admins can turn source reading off in setup. See What Xerg reads.
No. The GitHub App, every connector, Ask and the MCP tools only read.
Xerg found it in your code but hasn’t seen its account. Connect the service and it’s confirmed, with what the account actually runs.
Xerg finds services from packages, env variable names, config files and API hosts it recognizes. An env variable that looks like a service’s key but isn’t one Xerg knows shows as unrecognized (dotted and faded). A service your code never mentions shows up when you connect the account it runs in, or with Connect another service… in settings.
Every repo the Xerg GitHub App can see. Admins and owners change the list with choose repos in the left rail. See GitHub.
Only the people in your workspace. Viewers are free and see everything on the map; members can also ask and use coding agents. See Teams and roles.
No. Viewers are always free. Billing isn’t live yet, so every workspace is free for now; once it is, you’ll only pay for members active in the last 28 days. See Plans.
Yes. On the home page, type any public repo as owner/repo, or open one of the examples.
Uninstall the Xerg App in your GitHub organization’s settings, and revoke any keys you made for connectors in each vendor’s settings. To delete the workspace and everything in it, email hello@xerg.ai from an owner’s address.