Launching today
Polylane
AI agents that fix production before you wake up
117 followers
AI agents that fix production before you wake up
117 followers
Nobody should be on call. Polylane connects your code, infra and observability data, investigates every incident and opens a pull request with the fix. If code can't fix it, you get the root cause and a recommendation.
Hi Product Hunt, I'm Boris, founder of Polylane.
I built Baselime, an observability startup that was acquired by Cloudflare where I then led the Workers observability team. I have been advocating observability best practices for years, helping developers understand their app better. It was still not enough, I've lived and seen the pain of on-call way too much.
I'm now building Polylane, so you don't have to be on-call, a fleet of agents can do that for you.
Polylane connects your code, cloud infrastructure and observability data, and many other signals, to understand how your application actually runs. When something goes wrong, it investigates the incident and opens a pull request with a proposed fix for your team to review.
That same production context helps you:
- Catch risky code changes before they reach production.
- Get answers to production questions in Slack.
- Give your coding agents access to production context through MCP and the CLI.
Production changes require your approval, and code fixes go through your review and CI.
You can try Polylane today with the free plan. Connect your tools, and tell us where it helps or falls short.
What part of investigating an incident would you most want to hand off, and what evidence would you need to trust the result?
The team and I will be here answering questions.
Can it figure out issues that happen with CI/CD? With so much code beign pushed a lot of bad habits get introduced into CI/CD and would love to triage overtime.
@jowanza Yes! CI is one of the places it shines. @vitor_balocco mentioned it right above, Polylane picks up flaky tests and transient failures and opens PRs to harden them. It also remembers recurring patterns about your setup, so those bad habits get caught and cleaned up over time rather than one by one. Would love to see what it finds in yours Jowanza 🙌
How does it decide when an issue is safe to fix automatically?
Polylane
@ryankeller you keep control over what reaches production. Polylane investigates the incident, traces the cause through your telemetry and code, and opens a pull request when a code change can address it. That fix goes through your team’s review and CI, and production changes require your approval. If it can’t establish the cause or needs a decision from you, it brings back the evidence and the next action. Thanks for checking us out!
How it handles noisy alerts. Does the agent learn which signals are actually important for a specific application?
Polylane
@mariusholm repeated alerts for the same problem are grouped into one incident, and the agent checks the underlying telemetry and code to distinguish a real problem from expected behavior. It also saves confirmed findings and recurring patterns about your application, then uses those memories in future investigations. That gives it application-specific context over time, while recurring or worsening signals can trigger another look at an earlier dismissal. Thanks for checking us out!
Is there an audit trail showing the diagnosis and the action taken?
Polylane
@taoma17 Yup! You can open the investigation thread to see the evidence the agent gathered, its diagnosis, the tools it used, and the outcome. The incident also has an activity timeline connecting detections, findings, and the proposed fix or request for human action. If there’s a code fix, the pull request gives you the diff and validation results to review.
It fixed something like 5 mins in after we set it up. It not only helps with on-call investigations, it's also pro-active about improving issues in CI, like flaky tests, hardening against transient errors, etc. Great product!
@vitor_balocco 5 minutes, love it. Runlayer's CI setup is no joke, so watching @Polylane find its way through it and start fixing flaky tests was a real pleasure. Thanks Vitor!
Depot
We've been using Polylane at Depot for a few weeks now. I've never seen anything like it. I think we merged 10 PRs in the first hour it was running. Things will never be the same. A very awesome team to work with as well.
@kylegalbraith The day you started using Polylane was the first day @Polylane was actually on-call for us! 10 PRs in the first hour, I still think about that ! Your architecture is so complex our topology view couldn't even render all of it on day one 😅 Best stress test our systems have had. Thanks Kyle.