Meets your stack
where it already lives.
Connect the git provider you already use, wire rescans into your CI, hand the map to your AI agents through an MCP server and a VS Code extension, and gate access behind your own identity stack. Impact fits the tools you have instead of asking you to adopt new ones.
Source control
Six providers for scanning and PR automation.
Full read access for scanning plus pull request automation on the majors — and clone-only scanning for public forges.
GitHub
Full scanning plus PR automation. Connect via OAuth or install the GitHub App for push-triggered rescans.
GitLab
Scan any project and open merge requests. Works with gitlab.com and self-managed instances.
Bitbucket
Repository scanning and pull request automation on Bitbucket Cloud.
Azure Repos
Connect Azure DevOps repositories for scanning and coordinated pull requests.
AWS CodeCommit
Scan CodeCommit repositories and drive pull requests inside your AWS account.
SourceForge
Scanning plus pull request automation for projects hosted on SourceForge.
Public forges — clone-only
Codeberg
Clone-only. Point us at a public Codeberg repo and we scan it.
Gitea
Clone-only scanning for any reachable Gitea-hosted repository.
sr.ht
Clone-only. Public SourceHut repositories can be scanned on demand.
Automation & CI
Rescans on every push. PRs opened for you.
Push webhooks
Every project gets its own webhook secret. On each push we auto-rescan, so the map and the scores never drift from what shipped.
GitHub App
Install the app once and rescans fire automatically on push — no per-repo token juggling and no manual re-runs.
Coordinated PR automation
When a change spans several files or repos, Impact opens draft pull requests on the connected provider for you to review and merge.
For your AI agents
The codebase map, handed to your tools.
Impact’s understanding of your code — call graphs, blast radius, contract drift, risk — is available to the agents and editors you already work in.
MCP server
A Model Context Protocol server at /api/v1/mcp exposing 11 agent tools — blast_radius, who_calls, contract_drift, file_context, plan_change, simulate_change, review_change, risk, health_forecast, context and ask — for Claude Code, Cursor, or any MCP client.
VS Code extension
Blast radius, contract drift, risk, and file context surfaced inline in your editor as you make the change — before you ever open a PR.
Access & identity
Sign in your way. Automate with keys.
SSO / SAML
SAML single sign-on for account access, so your team signs in through the identity provider you already run.
Multi-factor auth
MFA on account sign-in adds a second factor for every user protecting your organization’s data.
API + API keys
Programmatic access to the platform with x-api-key or Bearer authentication — script scans, pull scores, and wire Impact into your own tooling.
Observability
Fuse production traffic into the map.
An OTel-style runtime telemetry ingest endpoint lets you feed real production traffic into Impact, so the dependency map reflects what actually runs — not just what the static analysis can see.
Connect your first repo.
Bring the provider you already use and have a full scan in under a minute. Wire up the webhooks, agents, and identity pieces whenever you’re ready.