Polylane

We have been using Polylane almost religiously for many months now. It's almost magical - Always almost perfect at finding issues and proactively fixing them. The polylane team has also been very active and been hearing our feedback and acting on it almost immediately, which is awesome.

We've been really impressed with the quality of proactive investigations and PRs @Polylane is landing. As soon as we had enough connectors setup (S-tier onboarding experience btw) and context was flowing it got to work. It's the first agent that feels like I had another dev on the team that cared about what I do: reliability, observability and ops. Some of the first PRs were things I had on my radar, but not the time or room to prioritize and manage my own agents to fix. Was able to remove a lot of my bespoke skills/agents.md instructions for nudging other agents to add proper observability instrumentation which never resulted in as effective outcomes as Polylane.@boristane and the team are goated in this space. They've got the secret sauce and are rapidly improving the product. Every day they're landing improvements. I can finally take a lot of the mental load off of making sure our systems remain reliable and when things do fail and the alerts roll in I am not the one having to drop everything and triage. You should have signed up yesterday!

Boris is one of my favorite creators, he never misses. (we use Polylane)

I work a day job away from my laptop, so "before you wake up" is really "before I get home" for me. Last week my bot server showed every process as online for hours while nothing actually ran, because the API credit behind it was empty. No crash, no error, just silence. That's exactly the "code can't fix it, here's the root cause" case. Does Polylane catch that kind of silent failure, or does it need an error or alert to start investigating?

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.

Congrats on the launch Boris. Down with on call

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!

We have been using it at @OpenStatus and it's been super helpful for us to catch some bugs we don't have time to fix All on the free tier 🔥

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.

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.