Fix production issues from your terminal.

Check what's broken, follow the fix and gate your deploys without opening a browser. Your coding agents can use it too.

See what's broken in production without opening a browser.

Check what's on fire, read the investigation and follow the fix, right where you're already working.

zsh
❯ polylane issue list --active
critical Checkout p99 up 18x checkout-edge
high orders-queue backlog orders-queue
❯ polylane autofix watch
fix(checkout-edge): restore the Hyperdrive pool size
✓ Pull request opened #1318

Stop deploys while production is down.

Every command works in CI with an API key. Stop a deploy when production is already in trouble.

.github/workflows/deploy.yml
18 - name: Stop if production is on fire
19 env:
20 POLYLANE_API_KEY: ${{ secrets.POLYLANE_API_KEY }}
21 run: |
22 count=$(polylane issue list \
23 --active --severity critical \
24 --output json | jq '.items | length')
25 test "$count" -eq 0

Your coding agents can use the CLI too.

One command installs the CLI and sets up the coding agents on your machine, so they can ask Polylane about production.

zsh
❯ curl -fsSL https://polylane.com/setup | bash
✓ Installed polylane
✓ Signed in
✓ Connected Cloudflare and GitHub
✓ Set up Claude Code and Cursor

Outcomes

Real numbers from Polylane customers.

Common questions.

Can I use it in CI?

Yes. Set POLYLANE_API_KEY and every command works without signing in.

How do I install it?

Run curl -fsSL https://polylane.com/setup | bash. It installs the CLI, signs you in and connects your stack.

What can I do with it?

Start threads, read issues and follow fixes, edit the knowledge base, and call any Polylane tool.

Platform
Surfaces

Nobody should be on-call.