BetaEditorial Listing

Polylane

Coreplane Labs · Polylane: AI On-Call Agent That Investigates Incidents and Opens Fix Pull Requests

Open Polylane

Polylane is an AI on-call agent that connects to your code, cloud accounts, and observability tools, detects production issues without alert thresholds, investigates them with cited evidence, and opens a pull request when the cause is a code defect. It suits small and mid-sized engineering teams on GitHub or GitLab running on AWS, Google Cloud, Cloudflare, Vercel, Fly.io, Railway, Supabase, or Kubernetes who want fewer pages and faster fixes.

PricingFreemium
Setupmedium
Runs onWeb · API
APIYes
Open sourceNo
DocsYes
CategoryCoding
DevOpsSREIncident ResponseRoot Cause AnalysisObservabilityAutofixPull RequestsPull Request ReviewCode ReviewSlackMCPGitHub

Best for

Startup and mid-sized engineering teams on GitHub or GitLab running production on AWS, Google Cloud, Cloudflare, Vercel, Fly.io, Railway, Supabase, or Kubernetes, who want an agent to watch telemetry, investigate incidents, and propose fixes as pull requests without a dedicated SRE team

Not ideal for

Teams whose code lives on Bitbucket, workloads mainly on DigitalOcean, organizations that route incidents through PagerDuty or Opsgenie or work in Microsoft Teams, and teams that must self-host or keep all data inside their own cloud without an Enterprise contract

Who it's for

Engineering, platform, and on-call teams at startups and growing companies that run production on modern cloud platforms and use GitHub

Capabilities

  • Live context graph of resources, dependencies, and repositories across connected clouds, with change records and resource tiers ranked by how much depends on each resource
  • Threshold-free issue detection that compares metrics, logs, and traces with each resource's own baselines, watches saved queries and dashboards, and folds repeat detections into one issue
  • Alert triage for alerts from Datadog, Sentry, Honeycomb, Axiom, Grafana Cloud, New Relic, LangSmith, Better Stack, OpenStatus, Logfire, PostHog error tracking, and Google Cloud Monitoring, with dismissals explained, plus an investigation for every new incident.io incident with findings posted in its Slack channel
  • One agent per issue from triage to fix, with every step citing its query, log line, or deploy, and outcomes marked resolved, diagnosed, or inconclusive
  • Polylane Fleet on paid plans: a lead agent and member agents work one hard incident in parallel on a shared board, and a second agent confirms each finding before it counts
  • Autofix pull requests (merge requests on GitLab) written in a sandbox, checked for deploy risks such as locking migrations, with a short narrated video walkthrough, and routed through the built-in agent or your own Devin, Cursor, Factory, Capy, or Amp account (only Cursor or the built-in agent on GitLab)
  • Impact assessment of every pull request against the live infrastructure it deploys to, with one comment updated on each push and an optional blocking check
  • Security review on each pull request that traces a finding from input to sink, drops the ones it can rule out, and holds the merge on a confirmed critical or high finding
  • Failed or timed-out builds on main or in the merge queue become issues it investigates and fixes, with CI context from GitHub Actions, CircleCI, Depot, and Blacksmith
  • Slack agent that answers in any channel or DM, follows per-channel instructions, reports fix progress (failed CI, merge, close) back to the thread, and can open a dedicated channel for each investigation above a severity you choose
  • Instrumentation pull requests that close observability gaps it finds in your code
  • MCP server, REST API, CLI, and a plugin for Claude Code, Cursor, and Codex, plus a Polylane app in ChatGPT, so coding agents and chat assistants can query telemetry, deploys, and the context graph
  • Workspace memory kept as a git repository of markdown files that agents update as they work, with a nightly clean-up and files you can read and edit from the console, API, or MCP
  • Read-only cloud connections by default, with each write paused for approval and screened by a safety review
  • SOC 2 Type II and ISO 27001:2022 listed on Polylane's website, with a trust center for security documentation

Limitations

  • In early access, according to Coreplane Labs' own company page
  • Code must be on GitHub or GitLab (GitLab.com or self-managed, supported since October 31, 2026); Bitbucket is on the roadmap, and Devin, Factory, Capy, and Amp can write fixes only on GitHub
  • DigitalOcean, PagerDuty, Opsgenie, Jira, and Microsoft Teams are still listed on the roadmap rather than supported; Azure support maps subscriptions, records changes, and investigates Azure Monitor alerts, while Google Cloud is read and analysed like AWS
  • Agent work draws from a monthly credit pool, and agents pause when it runs out unless you are on Scale or above and turn on capped overage
  • Bring-your-own OpenAI or Anthropic key, a custom AI gateway, and custom OpenAI-compatible models are Enterprise-only; every other plan runs on Polylane's managed models
  • Running Polylane inside your own cloud account is listed only on Enterprise, and no self-hosted version is documented
  • Free is limited to 2 team members, 2 cloud accounts, 10 impact assessments a month, and 16 automatic fix runs a day (runs you start yourself do not count), and an unused Free workspace pauses background monitoring after ten days
  • Results depend on the telemetry you connect, and by Polylane's own figures most detected issues end as a report or dismissal rather than a pull request
  • Change records are kept for 30 days or the most recent 5,000 per account

Use cases

  • Letting Polylane watch a Cloudflare Worker or Lambda function and open a pull request when a latency regression traces back to a recent code change
  • Forwarding noisy Datadog or Sentry alerts so Polylane dismisses the false ones with reasons and investigates the rest
  • Asking in Slack who owns a failing service, what changed, and whether the problem is on your side
  • Requiring Polylane's production-impact check on pull requests, including ones opened by coding agents
  • Giving Claude Code or Cursor production context over MCP before it changes an API or schema
  • Having Polylane open pull requests that add missing logging and tracing to route handlers
  • Letting Polylane find the commit that broke the build on main and open the fix before the team is blocked

Our take

Polylane is aimed at teams that want incidents to end in a reviewed pull request rather than a root-cause report, and its insistence on cited evidence and read-only defaults addresses the main worry about giving an agent production access. Its coverage of Cloudflare, Vercel, Fly.io, Railway, and Supabase fits startups on modern platforms best. Google Cloud, Azure, GitLab, and incident.io support arrived in October 2026, but enterprise operations stacks built on PagerDuty, Opsgenie, Jira, or Microsoft Teams are still waiting on the roadmap. Because credit pools are stated as multiples of the Free allowance rather than in investigations, the practical way to judge cost is to connect one service on Free, compare its findings with a few recent incidents, and watch how quickly credits are used.

Who should use it

On-call engineers and platform teams at startups running on AWS, Google Cloud, Cloudflare, Vercel, Fly.io, Railway, Supabase, or Kubernetes with GitHub or GitLab, especially teams without a dedicated SRE function who want alert triage, investigations, and fix pull requests handled by an agent.

Who should skip it

Teams on Bitbucket, enterprises that need PagerDuty, Opsgenie, Jira, ServiceNow, or Microsoft Teams workflows today, and companies whose policies require self-hosting, or running inside their own cloud account without an Enterprise contract.

Strengths

  • Goes from detection to a reviewed fix pull request, not just a root-cause report
  • No alert thresholds to tune: issues are judged against each resource's own baselines
  • Every investigation step cites its evidence and can be watched or interrupted
  • Broad support for modern platforms such as Cloudflare, Vercel, Fly.io, Railway, and Supabase
  • Flat monthly plans with a free tier, and unlimited MCP and API reads on every plan
  • Read-only by default, with every production write paused for approval

Weaknesses

  • Early access product from a young company
  • No Bitbucket, PagerDuty, Opsgenie, Jira, or Microsoft Teams support yet
  • Credit pools are relative multiples of the Free allowance, which makes real capacity hard to judge before trying it
  • Bring-your-own model key and in-your-cloud deployment are Enterprise-only

Polylane pricing

Free

$0

  • 2 team members
  • Up to 2 cloud account connections
  • Unlimited repositories and integrations
  • Monthly credits included (1x allowance)
  • 10 impact assessments (pull request reviews) per month
  • Up to 16 automatic fix runs a day

Starter

$80

Billed monthly

  • $768 a year when billed annually ($64 a month)
  • Unlimited seats
  • Up to 5 cloud account connections
  • 16x the Free credit allowance
  • 500 impact assessments per month

Team

$200

Billed monthly

  • $1,920 a year when billed annually ($160 a month)
  • Unlimited seats and cloud accounts
  • 40x the Free credit allowance, shared across the team
  • Shared memories and custom instructions
  • 2,000 impact assessments per month and join by email domain

Business

$500

Billed monthly

  • $4,800 a year when billed annually ($400 a month)
  • 100x the Free credit allowance
  • 5,000 impact assessments per month

Scale

$800

Billed monthly

  • $7,680 a year when billed annually ($640 a month)
  • 160x the Free credit allowance
  • 8,000 impact assessments per month
  • Opt-in pay-as-you-go overage under a monthly cap

Enterprise

Custom

  • Everything in Ultimate, with volume pricing on credits
  • Bring your own LLM provider key and AI gateway
  • Bring your own cloud
  • Dedicated support

Free tier limits: 2 team members, 2 cloud accounts, 10 impact assessments a month, up to 16 automatic fix runs a day, and the base monthly credit allowance. A Free workspace nobody uses for ten days pauses background monitoring after a warning email, while pull request reviews, alert triage, and chat keep working.

Note: Premium ($2,000 a month or $1,600 billed annually, 400x credits, 20,000 impact assessments) and Ultimate ($5,000 a month or $4,000 billed annually, 1,000x credits, 50,000 impact assessments) sit between Scale and Enterprise. Credits are cost-weighted AI tokens in one monthly pool that resets each month. When it runs out, agents pause after warnings at 70% and 90%, unless overage is turned on (Scale and above). Annual billing is 20% off. Repositories and integrations are unlimited on every plan, and Polylane Fleet is available on paid plans. Plans and limits checked against polylane.com/pricing and Polylane's billing docs on November 12, 2026.

Technical specs

API pricing

REST API and MCP server reads are unlimited on every plan, including Free. Agentic work (investigations, autofixes, pull request reviews) draws from the plan's monthly credits

Where Polylane excels

Overnight regressions fixed before the morning stand-up

Polylane flags a sustained deviation from a resource's baseline, traces it to a recent change, and opens a pull request with the evidence trail, so the on-call engineer reviews a fix instead of starting an investigation.

Cutting alert noise

Alerts forwarded from Datadog, Sentry, or Grafana Cloud are triaged by an agent that dismisses false positives with its reasons and investigates the real ones.

Guarding against risky changes from coding agents

Every pull request, whether written by an engineer or a coding agent, is reviewed against the production resources it deploys to, and the blocking check can hold a merge that would break them.

Polylane vs. competitors

Polylane vs. AWS DevOps Agent

AWS DevOps Agent is an AWS service that investigates incidents on AWS, Azure, and on-premises workloads across observability, code, and incident tools, recommends mitigations, and is billed at $0.0083 per agent-second, with enterprise integrations such as PagerDuty, ServiceNow, Dynatrace, Splunk, GitLab, and Azure DevOps. Polylane uses flat monthly plans with credit pools, detects issues itself without alert rules, opens fix pull requests in the same run, and reviews pull requests against live infrastructure, with first-class support for Cloudflare, Vercel, Fly.io, Railway, and Supabase. AWS DevOps Agent fits AWS-centric teams with established incident tooling, and Polylane fits teams on GitHub and modern cloud platforms who want the loop to end in a pull request.

Polylane vs. Traversal

Traversal is an enterprise AI SRE that sits on top of stacks such as Dynatrace, Splunk, AppDynamics, ServiceNow, and PagerDuty, is read-only by default, and is sold through sales with credit-metered investigations and SaaS, single-tenant, or BYOC-on-AWS deployment; its fixes are opt-in draft pull requests. Polylane publishes its prices with a free tier, detects issues itself without alert rules, and opens a fix pull request in the same run when the cause is a code defect, with first-class support for platforms such as Cloudflare, Vercel, Fly.io, and Railway, but it lacks PagerDuty and Jira and offers in-your-cloud deployment only on Enterprise.

Frequently asked questions

What does Polylane do?

Polylane connects to your cloud accounts, GitHub repositories, and observability tools, builds a live graph of your production system, and detects issues by comparing telemetry with each resource's normal behavior. It investigates each issue with cited evidence and, when the cause is a code defect, opens a pull request with the fix. It also reviews pull requests against production and answers on-call questions in Slack.

How much does Polylane cost?

Free costs $0 with 2 team members, 2 cloud accounts, and 10 pull request impact assessments a month. Starter is $80 a month ($64 billed annually) with unlimited seats and 16 times Free's credits. Team is $200 a month ($160 annually) with unlimited cloud accounts and 40 times Free's credits. Business ($500), Scale ($800), Premium ($2,000), and Ultimate ($5,000) add larger credit pools, and Enterprise is custom. Agent work draws from a shared monthly credit pool, while MCP and API reads are unlimited on every plan.

Does Polylane change production on its own?

Not by default. New cloud accounts connect read-only, and a write pauses the run to show the exact call for you to approve or reject. Code fixes arrive as pull requests that your review and CI decide, and Polylane merges only where you enable it.

Is Polylane SOC 2 compliant?

Polylane's website lists SOC 2 Type II and ISO 27001:2022 and links to a trust center run on Vanta for security documentation. Its security page also describes encrypted provider credentials, workspace-scoped API keys, OAuth 2.0 with PKCE, and owner, admin, member, and read-only roles. Teams with procurement requirements should check the trust center directly.

Which clouds and observability tools does Polylane support?

Clouds and platforms include AWS, Google Cloud, Azure, Cloudflare, Vercel, Fly.io, Render, Kubernetes, PlanetScale, Railway, Supabase, Modal, Convex, ClickHouse, Turso, Neon, and Upstash. Observability sources include Datadog, New Relic, Honeycomb, Axiom, Grafana Cloud, Sentry, Better Stack, OpenStatus, Logfire, LangSmith, and Braintrust, and code can live on GitHub or GitLab. DigitalOcean and Bitbucket are on the roadmap but not yet available.

Can I use Polylane from Claude Code or Cursor?

Yes. Polylane runs an MCP server that Claude Code, Cursor, Codex, OpenCode, VS Code, Pi, and other MCP clients can connect to, giving them the context graph, telemetry queries, deploys, and code search, and a plugin installs it with Polylane's skills in Claude Code, Cursor, or Codex. Polylane is also an app in ChatGPT. Reads are allowed by default, while write tools need an explicit scope and header.

Polylane vs AWS DevOps Agent: what is the difference?

Both investigate production incidents and find likely root causes. AWS DevOps Agent is an AWS service billed per agent-second that recommends mitigations and connects to enterprise tools such as PagerDuty, ServiceNow, and Splunk. Polylane is billed as a flat monthly plan, opens fix pull requests itself, and focuses on platforms such as Cloudflare, Vercel, Fly.io, and Railway alongside AWS, but it does not yet support PagerDuty.

Integrations & fit

AWSGoogle CloudAzureCloudflareVercelFly.ioRenderKubernetesPlanetScaleRailwaySupabaseModalConvexClickHouseTursoNeonUpstashTrigger.devGitHubGitLabSlackLinearincident.ioDatadogNew RelicHoneycombAxiomGrafana CloudSentryBetter StackOpenStatusLogfireLangSmithBraintrustPostHogMixpanelAmplitudeCircleCIDepotBlacksmithDevinCursorFactoryCapyAmpClaude CodeCodexChatGPTMCPREST API
Good fit forSolo / individual, Startup / small team, Enterprise
Pricing modelFreemium· Free tier available
See pricing on Polylane →

Alternatives to consider

About Polylane

Polylane, built by Coreplane Labs in San Francisco and founded by Boris Tane (who founded Baselime, acquired by Cloudflare), treats operations as a closed loop. Connect cloud accounts, GitHub or GitLab repositories, and observability providers, and it builds a live context graph of every resource, dependency, and repository, with change records for what appeared, changed, or disappeared. It reads metrics, logs, and traces on a schedule against each resource's own baselines, so there are no alert rules to write, and it triages alerts you forward from tools such as Datadog, Sentry, Grafana Cloud, or New Relic, and opens an investigation for every new incident.io incident. Each confirmed issue is worked by a single agent run that gathers evidence, tests hypotheses, and ends as resolved, diagnosed, or inconclusive. Every step cites the query, log line, or deploy behind it, and the run is a transcript you can watch, interrupt, or share. When the cause is a code defect in a connected repository, the same run writes the fix on a branch in a sandbox, checks it for risks such as locking migrations, and opens a pull request (a merge request on GitLab) that your review and CI still gate. When code cannot fix it, Polylane escalates to an engineer with the root cause instead. It also assesses every pull request against the infrastructure it deploys to, passing by default and failing only when it can show how a line breaks production, adds a security review that holds the merge on a confirmed critical or high finding, turns failed builds on main into issues it can fix, answers on-call questions in Slack, and gives Claude Code, Cursor, Codex, ChatGPT, and other MCP clients the same production context, with unlimited reads on every plan. Polylane's own engineering blog reports that, over the month around its switch from an 18-agent pipeline to one agent, median time from detection to pull request fell from 2.2 hours to 35 minutes and the share of detected issues ending in a pull request rose from 0.6% to 4.2%, so most runs still end as a report or a dismissal. Pricing is a flat monthly plan with a shared pool of cost-weighted AI credits, from a Free tier to $80, $200, and higher plans. Google Cloud, Azure, GitLab, and incident.io support arrived in October 2026. The tradeoffs: it is still in early access, Bitbucket, DigitalOcean, PagerDuty, Opsgenie, Jira, and Microsoft Teams remain on the roadmap, handing fixes to Devin, Factory, Capy, or Amp works only on GitHub, and bring-your-own model key and running it in your own cloud are Enterprise-only, with no self-hosted version documented.

Updates from Polylane

IntegrationGitLab support

Polylane can now connect a GitLab group on GitLab.com or self-managed, link each project to what it deploys, watch pushes and pipelines, and open merge requests from investigations the same way it opens pull requests on GitHub.

IntegrationPolylane for ChatGPT and Codex

Polylane became an app in ChatGPT and Codex, answering questions about recent changes, logs, metrics, and dependencies with issue cards, charts, and context graphs in the conversation. Investigations at a chosen severity can also open their own Slack channel.

IntegrationGoogle Cloud support

Every workspace can now connect a Google Cloud project. Polylane investigates Cloud Monitoring alerts as they fire and maps and monitors load balancers, data services, and pipelines alongside the rest of the stack.

New FeaturePolylane Fleet

Any chat or investigation thread can become a fleet, where a lead agent and member agents work the same production problem in parallel on a shared board and a second agent confirms each finding. Fleets are available on paid plans. incident.io and LangSmith integrations arrived the day before.

LaunchImpact Analysis launch

Polylane launched Impact Analysis on Product Hunt: every pull request gets one comment with evidence and a verdict on whether it is safe to merge against the live infrastructure it touches, plus a separate suggestion when the change ships code that could not be debugged in production.

LaunchPolylane launches on Product Hunt

Polylane launched publicly on Product Hunt on October 1, 2026, presenting itself as AI agents that connect code, infrastructure, and observability data, investigate incidents, and open pull requests with fixes.

New FeatureOne agent from finding to pull request

Every detected finding is now worked by a single agent run that triages it, traces the cause, and opens the fix pull request when the cause is a code defect, replacing the earlier multi-agent pipeline. Grafana Cloud and Pydantic Logfire also joined the observability integrations.

IntegrationClickHouse, Convex, Turso, and Linear integrations

ClickHouse Cloud, Convex, and Turso joined the context graph, and Linear became the first issue-tracking integration, letting the agent file issues from investigations with the evidence attached after asking for confirmation.

Are you the founder? Claim this listing →