# Polylane

> Polylane detects production issues and fixes them by opening pull requests.

Nobody should be on-call. Polylane is built by Coreplane Labs in San Francisco, founded by Boris Tane (built Baselime, acquired by Cloudflare; led observability at Cloudflare). Signing up is one command: `curl -fsSL https://polylane.com/setup | bash` installs the CLI, connects the coding agents on the machine, and creates the account. What the script does: https://polylane.com/setup.

## Trusted by the teams you trust

[Depot](https://polylane.com/customers/depot/) · [Supermemory](https://polylane.com/customers/supermemory/) · Unkey · [Basedash](https://polylane.com/customers/basedash/) · [Terminal](https://polylane.com/customers/terminal/) · FLORA · Pocket · [Orchid](https://polylane.com/customers/orchid/)

## What Polylane does

Polylane runs a closed loop over production software, in five steps:

1. **Context**: agents build the context graph live, every resource and dependency across your clouds, observability providers and codebase, so every later step starts from real topology instead of guesses.
2. **Remediation**: agents fix the issue rather than the symptom. Polylane never changes production on its own: the fix is investigated first, written on a branch, and validated, then arrives as a pull request with the full evidence trail; your review and CI still gate the merge.
3. **Review**: agents review every pull request against the production it deploys to, whether an engineer or a coding agent opened it. Polylane walks the graph from the repository to the resources behind it and reads their tier, recent changes and open issues, then leaves one comment, updated in place on every push. A fail has to prove how a line in the diff breaks production, so passing is the default; turn on the blocking check and a fail holds the merge until a later push clears it.
4. **On-call**: agents answer the questions on-call gets, in the thread where they are asked. Who owns this, what changed, is it us: answered with every claim linking back to the query, log line, or change record behind it.
5. **Coding agents**: your coding agent gets the same production context Polylane's own agents use, over one MCP endpoint with browser sign-in and OAuth handled for you: the context graph, telemetry queries, deploys and code search. Reads by default; writes sit behind a default-deny policy, and merging stays human.

At runtime, every incident runs the same named loop: **Signal → Investigate → Fix → Verify**. Signal: An error spike, a failed deploy, a metric drifting from baseline. Anything production emits can start a run. Investigate: One agent writes the causal chain with your real tools: telemetry, deploys, code. Every link keeps its receipt. Fix: Reversible actions run where you allow them. When the root cause is code, the fix arrives as a pull request; your review and CI gate the merge. Verify: Agents watch the signal back to baseline and confirm the fix holds. What they see becomes the next signal.

Polylane works with AWS, Cloudflare, Vercel, Google Cloud, Render, PlanetScale, Railway, Fly.io, Kubernetes, Supabase, Modal, Convex, Trigger.dev, ClickHouse, Turso, Neon, Datadog, Honeycomb, Axiom, Sentry, Better Stack, OpenStatus, Grafana Cloud, Logfire, LangSmith, GitHub, Devin, Cursor, Factory, Conductor, Capy, Slack, incident.io, Linear, Mixpanel, PostHog, Depot, and MCP Server. Every integration is listed at https://polylane.com/integrations/.

## When to use Polylane

- **Detect production issues without threshold tuning.** From raw telemetry to triaged issue. Polylane agents read the actual metric, log, and trace series across AWS, Cloudflare, Vercel, Fly.io, Render, and Kubernetes, and flag regressions against each resource's own baseline.
- **Investigate an incident and prove the cause.** From error spike to root cause. Every claim in a Polylane investigation links back to the query, log line, or change record behind it. Runs are shareable transcripts you can watch and interrupt.
- **Turn an investigation into a reviewed fix.** From pager alert to merged fix. Investigations that end at a line of code end as a pull request with the full evidence trail. Human review and CI still gate the merge.

## For agents

- REST API: `https://api.polylane.com/v1` (OpenAPI spec at https://api.polylane.com/v1/doc, mirrored at https://polylane.com/openapi.json)
- MCP server (OAuth 2.0 or API key): `https://mcp.polylane.com/mcp` (Streamable HTTP, auth walkthrough at https://polylane.com/auth.md)
- Docs MCP server (no auth): `https://docs.polylane.com/mcp` (Streamable HTTP)
- API catalog: https://polylane.com/.well-known/api-catalog · MCP discovery: https://polylane.com/.well-known/mcp
- Full index: https://polylane.com/llms.txt · Docs: https://docs.polylane.com

## Pages

- [Developers](https://polylane.com/developers) ([markdown](https://polylane.com/developers.md))
- [Use cases](https://polylane.com/use-cases) ([markdown](https://polylane.com/use-cases.md))
- [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 as your AI SRE](https://polylane.com/use-cases/ai-sre) ([markdown](https://polylane.com/use-cases/ai-sre.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))
- [Pricing](https://polylane.com/pricing) ([markdown](https://polylane.com/pricing.md))
- [Security](https://polylane.com/security) ([markdown](https://polylane.com/security.md))
- [Blog](https://polylane.com/blog) · [Customers](https://polylane.com/customers)
- [About](https://polylane.com/about) ([markdown](https://polylane.com/about.md)) · [Contact](https://polylane.com/contact) ([markdown](https://polylane.com/contact.md))
- [Careers](https://polylane.com/careers) ([markdown](https://polylane.com/careers.md))
- [Incident hotline](https://polylane.com/incident-hotline) ([markdown](https://polylane.com/incident-hotline.md))

## Trust

- SOC 2 Type II: independently audited security controls.
- ISO 27001:2022: the international standard for information security management.
- End-to-end encryption: AES-256 at rest, TLS 1.2+ in transit.
- Data isolation: fully isolated per organization.
- Trust center: https://trust.polylane.com

## Contact

- X: https://x.com/polylane
- Email: boris@coreplane.ai