Wake up to a fix for last night's incident.

Polylane writes the fix for the production issues it finds and opens a pull request with the cause and the proof. You review it and merge it.

Get started for free

No credit card required.

Each fix comes with the cause and the evidence.

Every fix explains what broke, why, and how it was proven, and Polylane reviews its own code before you see it.

Pull request
Open coreplanelabs/checkout-edge #1318
fix(checkout-edge): restore the Hyperdrive pool size
What broke

Checkout p99 rose 18x at 20:14. Requests were queueing for a database connection.

Why

Deploy 9f3c2a1 lowered max_connections on hd-prod from 50 to 5.

The fix

Restores the pool to 50 and adds a test that fails if it drops below peak concurrency.

Polylane review 3 rounds, nothing open
CI 18 checks passed

Polylane also fixes failed builds, missing logs and risky config.

Failed builds, missing logs, risky config: Polylane opens the pull request, so the backlog shrinks while you work on what matters.

fix(ci): pin the node version the tests were written for
From a failed build on main · 1h ago
Open
feat(orders): log the order id on every failed payment
From a gap in your logs · 3h ago
Merged
fix(queues): add a dead-letter queue to orders-queue
From an advisory · 5h ago
Merged

Let your own coding agent write the fix.

Prefer Devin, Cursor, Factory, Capy or Amp? Polylane hands them the proven cause, and they open the fix.

Investigation · Checkout p99 up 18x
Polylane 20:19

Cause proven: deploy 9f3c2a1 cut the hd-prod pool from 50 to 5. Handed the fix to Devin, as set in your coding agent settings.

Devin 20:27

Restored the pool to 50 and added a test for it.

fix(checkout-edge): restore the Hyperdrive pool size
Opened by Devin · #1318
CI passing

If CI fails on a fix, Polylane fixes that too.

If CI fails on a fix, Polylane reads the failing job and pushes a fix to the same branch. You only look once it passes.

Pull request
Open coreplanelabs/orders-api #1312
fix(orders): build the search index concurrently
polylane commented

The integration test timed out waiting for the index. I added a wait for the build to finish and pushed it to this branch.

Unit tests
Integration tests passing after the fix

Outcomes

Real numbers from Polylane customers.

Common questions.

Will Polylane merge anything on its own?

No. You review and merge every fix, unless you have explicitly set up an automation that does it.

Is there a limit on fixes?

No. Fix pull requests are unlimited on every plan.

What if CI fails on a fix?

Polylane reads the failing job and pushes a fix to the same branch. You only look once it's green.

Can I ask for changes to a fix?

Yes. Comment on the pull request or reply in the thread, and Polylane updates the fix on the same branch.

What happens to fixes nobody reviews?

Polylane reminds you after a week. After another quiet week it closes the pull request and keeps the branch.

Platform
Surfaces

Nobody should be on-call.