Turso. Database groups and edge-hosted libSQL databases.
Connect your Turso organization to give agents visibility into your database groups and edge-hosted libSQL databases. Agents can track database placement across locations, monitor branching, and correlate database activity with the rest of your infrastructure.
Join the waitlistWhat Polylane does with Turso.
Groups and databases in the graph
Every database group and libSQL database with its locations, placement, and branching parentage, next to everything else you run.
Linked to the services that query them
Polylane matches database hostnames, so when a service slows down, the graph already knows the database behind it.
Change intelligence on your data layer
New databases, moved groups, and blocked reads or writes show up as changes agents can reason about mid-investigation.
Your rows stay yours
Polylane reads the Turso Platform API and nothing else: it never connects to your databases, never sees your rows, and never holds database credentials.
How it works.
Connect
Paste a platform API token, pick the organization, and syncing starts.
Link
Groups and databases join the graph, matched to the services that query them.
Agents take the watch
Every sync records what changed, and investigations trace from the service to the exact database.
In the graph.
The Turso resource types Polylane syncs, with their edges, config, and history.
Database Group Database Questions.
Is Polylane an AI SRE for Turso?
It's what most people mean by the term: agents that keep your Turso resources in one context graph, watch them, investigate issues and fix what they can, with a human approving anything that changes production. We call it self-operating software rather than an AI SRE: the point is that your software looks after itself, not that a bot joins the on-call rotation.
Can Polylane change anything in Turso?
Only if you let it. Connected read-only, agents investigate and explain, and changes only ever land as pull requests for you to review. With write access, every write pauses for your approval first, with the method, path and reason on screen. Rollbacks are off by default: you enable them per automation and can turn them off at any time.