# Polylane Context graph

> Polylane's context graph joins every cloud resource and repository across providers, with blast radius and tiers. It is the same graph its agents reason over.

See how every service connects across all your clouds. Polylane links everything in AWS, Cloudflare, Vercel and the rest to the code that deploys it, so anyone can see what calls what and what breaks if it fails.

- **Ask what calls a database and get the answer from your infrastructure.** What calls this database? Which repository deploys that worker? Ask in plain English and get the answer from your real infrastructure.
- **Know what breaks before you change a resource.** Pick any resource and see everything that depends on it, across every cloud.
- **Critical resources are checked every 30 minutes.** Polylane works out what everything else depends on, checks it more often, and tells you why. Change anything you disagree with.
- **Your coding agent can check dependencies before it changes code.** Through the MCP server, the CLI or the API, your agent can check what a service connects to before it changes the code.

## Questions

### What do I need to connect?

Your cloud accounts and your repositories. Polylane builds the graph from them and keeps it current.

### Can my coding agent use it?

Yes, through the MCP server, the CLI or the API.

### Which clouds does it cover?

AWS, Google Cloud, Cloudflare, Vercel, Kubernetes and more. The integrations page lists every one.

### Does Polylane need write access to build the graph?

No. The graph is built from read-only access to your accounts and repositories.

## More of the product

- [Swarms](https://polylane.com/product/swarms) ([markdown](https://polylane.com/product/swarms.md)): Many agents on one problem, sharing one board.
- [Investigations](https://polylane.com/product/investigations) ([markdown](https://polylane.com/product/investigations.md)): From an issue to a proven root cause.
- [Knowledge Base](https://polylane.com/product/knowledge-base) ([markdown](https://polylane.com/product/knowledge-base.md)): Everything Polylane learns about your production, written down.
- [Autofix](https://polylane.com/product/autofix) ([markdown](https://polylane.com/product/autofix.md)): Reviewed fixes, opened in your repository.
- [Impact assessments](https://polylane.com/product/impact-assessments) ([markdown](https://polylane.com/product/impact-assessments.md)): Checks each pull request against production.
- [Anomaly detection](https://polylane.com/product/anomaly-detection) ([markdown](https://polylane.com/product/anomaly-detection.md)): Finds problems nobody set an alert for.
- [Advisories](https://polylane.com/product/advisories) ([markdown](https://polylane.com/product/advisories.md)): Misconfigurations, found and fixed per resource.
- [Escalations](https://polylane.com/product/escalations) ([markdown](https://polylane.com/product/escalations.md)): One clear ask when a person is needed.
- [Console](https://polylane.com/product/console) ([markdown](https://polylane.com/product/console.md)): The web app: graph, threads, issues.
- [Slack](https://polylane.com/product/slack) ([markdown](https://polylane.com/product/slack.md)): Ask about production where you already talk.
- [GitHub](https://polylane.com/product/github) ([markdown](https://polylane.com/product/github.md)): Mention @polylane on any pull request.
- [MCP and plugins](https://polylane.com/product/mcp) ([markdown](https://polylane.com/product/mcp.md)): Production context for Claude Code, Cursor and Codex.
- [CLI](https://polylane.com/product/cli) ([markdown](https://polylane.com/product/cli.md)): Polylane from your terminal.
- [API](https://polylane.com/product/api) ([markdown](https://polylane.com/product/api.md)): Everything in the console, over REST.

Get started with one command: `curl -fsSL https://polylane.com/setup | bash` installs the CLI, connects your coding agents, and creates the account.
