Turso integration: connect database groups and databases to Polylane
Connect Turso database groups and databases to Polylane with a platform token. Track usage deltas and quota burn without granting database credentials.
Get started for freeWhat 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 to set up Turso
- Create a platform API token in Turso account settings or run turso auth api-tokens mint polylane.
- Paste that token into Polylane, rather than a database auth token.
- Select the organization if more than one is reachable and connect after validation. Each connection covers one organization.
Permissions and access
Polylane uses the Platform API only. It never connects to your databases or holds database credentials. The connection form has no read-only/full-access selector; the platform token’s own privileges determine access.
Discovery, refresh and the connected view
Database groups and databases refresh every 15 minutes, with locations, placement, branching parentage and read/write status. Platform usage comes as cumulative billing-period counters rather than time series, so database pages have no metric charts. Monitoring compares deltas in reads, writes, sync traffic, storage, database count and plan quota burn with the account’s history.
Example workflow
Investigate a quota spike by checking database usage deltas and the heaviest queries per database. Compare the organization’s storage growth and replica sync traffic with its database placement and branching map. This can separate rising workload from replication overhead without handing Polylane database credentials.
Disconnect and revoke access
Disconnect Turso in Polylane and revoke the platform API token in Turso. A manual Sync requests inventory sooner than the next scheduled pass.
Provider credentials and Polylane’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
In the graph.
Every Turso resource Polylane picks up sits in the graph with its connections, config and history.
Database Group Database Common questions.
Can I connect with a Turso database token?
No. Database auth tokens and platform API tokens are different. Mint a platform token with turso auth api-tokens mint or use the account settings API Tokens page.
Does Polylane read Turso rows?
No. It reads organization and database metadata and usage from the Platform API, without a database connection or database credentials.