# Polylane as your AI SRE

> Polylane is an AI SRE: it learns your system, watches production, investigates every issue with evidence, and writes the fix.

An AI SRE that fixes what it finds. Polylane does an SRE's work: it learns your system, reviews changes, handles incidents, fixes bugs and keeps CI green.

- Learns your system and watches production on its own
- Reviews changes, handles incidents, fixes bugs and keeps CI green
- Shows the evidence behind every conclusion

## How it plays out

### It learns your system before anything breaks

Polylane connects your clouds, repos and observability tools into one context graph, so it knows what depends on what before something goes wrong.

### It reviews changes before it ships

Every pull request is checked against the production it deploys to. If it would break something, Polylane says why before you merge.

### It handles incidents while you sleep

Every alert is checked, repeats are grouped, and real incidents are investigated with the evidence attached.

### It turns bug reports into fixes

Hand it a bug report and it proves the cause before it writes the fix, or passes the work to Devin, Cursor or Factory.

### It keeps CI green when main breaks

When a build fails on main, Polylane finds the commit that broke it and writes the fix.

## Built to be trusted with production.

- **Evidence behind every claim.** Every conclusion links to the query, log line or deploy that supports it, or says what is still unknown.
- **Read-only until you say so.** Accounts connect read-only. Write calls are refused until you turn read-only off for that account.
- **Nothing to tune.** Built-in checks learn what normal looks like for every provider you connect.
- **Not another pager.** It tells you in Slack, email and the console, with the investigation already done.
- **Works with your coding agent.** Polylane writes fixes itself, or hands them to Devin, Cursor or Factory.
- **Sharper every week.** It remembers what it confirms and keeps daily notes, so each issue makes the next one faster.

## Learn more

- [What Is an AI SRE? How It Works and How to Evaluate One](https://polylane.com/learn/incident-response/what-is-an-ai-sre/)
- [Is It Safe to Give an AI SRE Read Access to Production?](https://polylane.com/learn/ai-in-production/is-it-safe-to-give-an-ai-sre-read-access-to-production/)
- [How to correlate incidents with deploys using evidence](https://polylane.com/learn/deployment-safety/how-to-correlate-incidents-with-deploys/)
- [I'm Betting My Company on Proactive Agents](https://polylane.com/blog/proactive-agents/)

## Questions

### What is an AI SRE?

An AI SRE does the operational work of keeping production healthy: it watches your systems, triages alerts, investigates issues and fixes them. Polylane does all four and shows the evidence for each conclusion.

### Does an AI SRE replace my on-call rotation?

It takes the first pass at everything, so people step in only when something needs a decision. Polylane isn't a pager: it tells you by email, Slack and the console, and each issue arrives already investigated.

### Is it safe to give an AI SRE access to production?

Accounts connect read-only, and write calls are refused until you turn read-only off for that account. Code changes go through your normal review.

### How is an AI SRE different from an observability tool?

Observability tools store your telemetry and show it to you. Polylane reads it, decides what matters, finds the cause and writes the fix.

### Does it only diagnose, or does it fix too?

It fixes too. Once the cause is proven, Polylane writes the fix and tests it, ready for your review.

### Do I have to set thresholds?

No. Polylane judges each signal against how that resource normally behaves at that hour on that day, and assumes nothing is wrong until the data says otherwise.

### Will it wake me for a blip?

No. A change has to be big, sustained and heading the wrong way, and repeats fold into one issue.

### What happens to an alert it dismisses?

It's kept with its reasoning, and one click sends it back for investigation. An alert that fires again gets triaged again instead of dismissed twice.

## More use cases

- [Polylane for impact analysis](https://polylane.com/use-cases/impact-analysis) ([markdown](https://polylane.com/use-cases/impact-analysis.md))
- [Polylane for DevOps](https://polylane.com/use-cases/devops) ([markdown](https://polylane.com/use-cases/devops.md))
- [Polylane for Continuous Integration](https://polylane.com/use-cases/continuous-integration) ([markdown](https://polylane.com/use-cases/continuous-integration.md))
- [Polylane for ticket resolution](https://polylane.com/use-cases/ticket-resolution) ([markdown](https://polylane.com/use-cases/ticket-resolution.md))
- [All use cases](https://polylane.com/use-cases) ([markdown](https://polylane.com/use-cases.md))

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