Every incident teaches Polylane something it won't forget.

Polylane writes down every root cause it proves, how your services fit together and how your team likes things done, in a knowledge base you can read and edit. Every investigation starts from it.

Get started for free

No credit card required.

Every investigation leaves notes for the next one.

When Polylane learns how a service works or why it broke, it writes it down in plain markdown files. Nobody has to set them up, and you can read and edit every one.

Settings · Memory
MEMORY.md
daily
preferences
repos
services
checkout.md
orders.md
search.md
services/checkout.md Edit
checkout

checkout-edge serves every checkout request on Cloudflare Workers.

How it works
•Reads orders through the Hyperdrive pool hd-prod.
•Peaks at 41 concurrent queries around 20:00 UTC.
Known failures
•Pool too small: requests queue and time out. Seen Nov 17 after deploy 9f3c2a1, fixed in #1318.
Updated by Polylane · 2 hours ago

When a problem comes back, Polylane already knows the cause.

Every root cause Polylane proves is saved. The next time the same thing breaks, it checks the known cause first instead of starting from scratch.

Investigation · Checkout p99 up again
Polylane Nov 17
queryLogsgetCommitDiff

Cause proven: deploy 9f3c2a1 cut the hd-prod pool from 50 to 5.

Saved to the knowledge base
services/checkout.md · Known failures
Saved
Polylane Nov 24

Checkout p99 is up again. This matches a known failure in services/checkout.md, so I checked the pool size first: deploy 4c1e8b0 set it to 8. Fix is up.

Tell Polylane your team's rules once.

Deploy freezes, who owns what, how you like fixes written: put them in a file and Polylane follows them in every investigation. It never rewrites them.

preferences/deploys.md · edited by you
How we ship
•No deploys on Fridays after 4pm.
•Fixes to payments need a review from the payments team.
•Use conventional commit titles.
•Anything touching orders-db goes to #platform-oncall.

Every investigation starts briefed.

Each new investigation reads the knowledge base's index and the last three days of notes, then searches the rest for anything that matches.

investigation sandbox
❯ rg -l "hd-prod" memory/
memory/services/checkout.md
memory/repos/coreplanelabs-checkout-edge.md
memory/daily/2026-11-17.md
❯ rg "Known failures" -A 2 memory/services/checkout.md
- Pool too small: requests queue and time out.

Every night, Polylane dreams.

While your team sleeps, Polylane goes back over the day. It writes a daily note, learns from the fixes you merged as they were and the ones you changed, checks every saved fact against your infrastructure and code, and deletes what's no longer true. Each step is its own commit, so you can undo any of it.

memory · git log
❯ git log --oneline --since=yesterday
a41c9e2 dream: index
7be0d15 dream: tidy
c93f2a8 dream: corrections
removed: orders-queue backs up during imports
imports moved to their own queue in #1290
5d27b61 dream: outcomes
#1318 merged as written: keep fixes this size
e0f4c19 dream: daily note

Outcomes

Real numbers from Polylane customers.

Common questions.

Can I see and edit it?

Yes. Browse it in the console under Settings, Memory: open any file, edit it or add your own. It's a git repository, so every change is tracked.

What does Polylane save?

Findings it has confirmed with evidence, each with the resource and the date. It doesn't save guesses or anything already in the context graph.

How does Polylane use the knowledge base?

Every new investigation starts with its index and the last three days of notes, then searches the rest for anything related.

Can I add something myself?

Yes. Add your own files, or ask in any thread: “Save a note: the payments sandbox times out under parallel load.”

Platform
Surfaces

Nobody should be on-call.