It was a slow query all along. Polylane traces a regression from the service, to the branch, to the exact query.
PlanetScale runs MySQL and Postgres so you don't have to. Polylane puts your databases in the same graph as the services that query them, so investigations don't stop at the service boundary.
Join the waitlistEvery supported resource.
The PlanetScale resource types that show up in your graph.
Database Database Branch The database joins the investigation.
Your databases stop being a separate tab: agents map them and investigate through them.
Databases and branches in the graph
Polylane syncs every database and every branch with its plan, region, schema state, and history. MySQL and Postgres, next to everything else you run on other clouds.
Linked to the services that query them
Polylane matches connection hosts and usernames to work out which service talks to which branch. When checkout latency spikes, the graph already knows the database behind it.
Query Insights in the investigation
Mid-investigation, agents pull Query Insights for the branch: the slow queries, the erroring queries, and the latency windows PlanetScale itself flagged. It all lands in the investigation as evidence.
Schema changes on the timeline
Every sync records what changed: new branches, stale branches, schemas that moved. When an app breaks right after a migration, the investigation starts from the migration.
Your rows stay yours
Polylane reads the PlanetScale API and nothing else. It never connects to your databases, never sees your rows, and never holds database credentials. OAuth tokens are encrypted before they're stored and the agent never sees them.
Investigations that end in a PR
When the root cause is a bad query or a migration, the fix arrives as a pull request on the repo behind the service, with the evidence attached: the missing index, the reverted migration.
Questions.
How does Polylane connect to my PlanetScale organization?
With OAuth. Click connect, approve in PlanetScale, and syncing starts. Polylane asks for read scopes only, and there are no API keys to create or paste.
What PlanetScale resources does Polylane sync?
Databases and their branches, MySQL and Postgres, each with plan, region, schema state, and history. Polylane also matches connection hosts and usernames so each branch is linked to the services that query it.
Can Polylane change my databases?
No. Polylane reads the PlanetScale API only: it never connects to your databases, never sees your rows, and never holds database credentials. When the fix is a bad query or a migration, it arrives as a pull request, and your review and CI gate the merge.
How do database issues show up?
Through the graph. When an app regresses, the blast radius includes the branch behind it, and agents pull Query Insights for that branch: slow queries, erroring queries, and PlanetScale's own latency anomaly windows.
Does it work with my observability provider?
Yes. Datadog, Sentry, Honeycomb, and Axiom join the graph as first-class sources, and their alerts get triaged by an agent the moment they fire.
What does it cost?
Pricing is public and self-serve: a free plan, paid plans from $80 a month, and prepaid autofix bundles that never expire. Every plan and limit is published at polylane.com/pricing.