Roadmap. What we're building, in public.
We're a small team with big ambitions: we ship to production nearly every day and we publish the plan. No swimlanes, no dates, just what's done, what's in progress, and what's next.
The cloud graph
One graph, every cloud
Connect AWS, Cloudflare, Vercel, Fly, and Render, and every resource you run lands in a single living graph with its edges, config, and history.
AWS 
Cloudflare 
Vercel 
Fly.io 
Render Kubernetes
Clusters, workloads, and their churn alongside everything else. Hand us a kubeconfig and EKS wires itself up.
Kubernetes Wikis that write themselves
Every cloud resource gets living documentation that rewrites itself as your system drifts, and your repositories are indexed for agents to grep.
Workers 
Lambda 
DynamoDB 
D1 
S3 …and every resource we sync Change intelligence
Every sync writes down exactly what appeared, changed, or disappeared. When production breaks, the culprit is usually in here.
Blast radius
Every anomaly maps the slice of the graph it touches, and the investigation starts from that map: agents walk the affected edges to the offending resource instead of guessing.
Resource tiers
An agent ranks every resource by how load-bearing it is. Tier one gets watched closest and investigated first, and you can overrule the ranking anytime.
Applications
Resources grouped into the applications they serve, so agents know what's load-bearing before they touch anything.
More clouds
GCP, Azure, Supabase, Railway, and DigitalOcean. Same graph, same treatment.
Google Cloud 
Azure 
Supabase 
Railway 
DigitalOcean Detection without thresholds
Proactive observability
Agents comb your metrics, logs, traces, and access logs on a cadence and flag what's actually wrong, before your customers do. No thresholds to tune, no alert rules to babysit.
Observability providers as sources
Datadog, Sentry, Honeycomb, and Axiom join the graph as first-class citizens, and an agent triages every alert they fire the moment it lands.
Datadog 
Sentry 
Honeycomb 
Axiom Your charts become checks
That dashboard your team curated? Every query and chart saved in a provider gets picked up on the next sync and watched from then on.
Déjà vu detection
Repeat detections fold into one anomaly instead of re-paging you. An 18x P99 regression is one anomaly, not forty pages.
Scan reports
Ask for a sweep of a whole account and an agent walks the graph, queries the telemetry, and hands you a written report of what it found.
Telemetry attribution
Logs, metrics, and datasets from your observability providers matched to the exact resources that emit them. No tagging homework, an agent works out the mapping.
Vercel runtime telemetry
Function logs and runtime metrics from Vercel joining the graph, next to the deployments and domains we already sync.
Vercel Cloud doctor
Like react-doctor, for your cloud. One command grades the whole account: misconfigurations, missing observability, security posture, and the five things to fix first.
Cost intelligence
Billing joined to the graph, and agents that point at exactly which resources are burning money for nothing.
More providers
Grafana, Splunk, Better Stack, SigNoz, and Logfire, with the same first-class treatment.
Grafana 
Better Stack 
SigNoz 
Logfire Closing the loop with product
PostHog, Mixpanel, and Amplitude in the graph, so an incident's blast radius includes what your users actually felt.
PostHog 
Mixpanel 
Amplitude From signal to reviewed fix
Incident threads
Every investigation is a transcript with cited tool calls. Watch it think, interrupt it, hand it to a teammate, or make it public.
Marathon investigations
The agent loop is moving onto durable workflows: investigations that grind for hours, survive restarts, and pick up exactly where they left off.
Autofix
Investigations that end at a line of code end as a pull request, with a regression test and the evidence trail. You review, you merge.
Bring your own executor
Route autofix through Cursor or Devin with your own key, or let the built-in agent open the PR.
Cursor 
Devin The next autofix engine
The built-in executor is moving to the open-source pi coding agent, running in the same sandbox with the same review gates.
More executors
Claude Code, Codex, and Factory: delegate the fix to whichever agent your team already trusts.
Claude Code 
Codex 
Factory Memory
Agents remember what they confirm; so can you. Each day the workspace also writes its own notes from your threads, durable facts plus a daily log, so every investigation starts already knowing your system.
Skills
The way your team debugs, packaged into procedures agents reach for on the next incident. Write them once, benefit every time.
Dynamic skills
Agents notice what keeps working and write their own skills, sharpening them with every incident.
Automations
Cron, webhooks, GitHub events, and alerts trigger agent runs; results land in email, Slack, or your webhook.
Advisories
Every resource carries its misconfigurations and risks, each one marked fixable in place or with guidance.
Agents on your pull requests
A comment when a change looks like tomorrow's incident, an answer when you ask whether it'll break production.
Change intelligence for pull requests
Every PR annotated with what it will actually change in your cloud, before you merge instead of after the deploy.
Issue trackers
Findings filed as issues in Linear or Jira, where your team already plans work.
Linear 
Jira Every surface
A CLI built for coding agents
Structured output, non-interactive flags everywhere, and a skill that teaches Claude Code or Cursor when to reach for it.
MCP server
The whole platform as tools for any agent that speaks MCP.
Bring your own MCP
Connect your own MCP servers and their tools show up in the agent's hands mid-investigation.
Public API
Everything the console does, scriptable.
Slack
Notifications where your team lives, and investigations you can spin off from any message.
Slack Browser extension
Cmd+. puts the agent on whatever tab you're reading; the page becomes the thread's context.
Your incident platforms
An incident fires in PagerDuty or incident.io and an agent is already investigating before anyone picks up the page. Resolved with evidence, not just acknowledged.
PagerDuty 
incident.io Wanna add to the roadmap? Tell us what to build.
We want Polylane to be everything you expect from software that looks after itself in production.
Feedback or requests? Find us on X or email us. What already landed is in the build log.
Or skip the suggestion box and come build it with us. We're hiring.