← All updates

Updated

Neon: projects, branches and computes in the context graph

Teams on Neon can now connect an organization, so Polylane adds their Postgres projects to the context graph, watches them and queries them read-only in investigations.

What changed

Connect a Neon organization and Polylane adds your projects, branches, computes and databases to the context graph, synced every 15 minutes. A service that reaches a Neon compute, through a DATABASE_URL or a Cloudflare Hyperdrive configuration, is linked to it, so it no longer ends at an unknown external host.

Checks

Every 30 minutes, Polylane checks compute time, written data and data transfer against the account's history, the storage headroom of the fullest branch, and failed operations such as a compute that failed to start. Projects on Neon's Launch plan and above also chart compute, transfer and storage. No check queries Postgres, so monitoring never wakes a suspended compute.

Investigations

Agents can run one read-only SQL statement on a branch database, read the top statements from pg_stat_statements, and list recent operations. Postgres runs each statement in a READ ONLY transaction, and Polylane refuses API paths that return keys, passwords or connection strings. See the Neon integration.

Why it matters

Neon is often the database behind a Vercel or Cloudflare app. Linking it to the services that use it lets an investigation follow a slow or failing request to the compute and the query behind it.

How to use it

  1. In the Neon Console, open Organization settings → API keys and create an organization API key.
  2. In the Polylane console, open Settings > Clouds, connect Neon and paste the key. A personal key that reaches several organizations asks you to pick one.
  3. Polylane watches production branches by default. To watch preview, staging and development branches too, turn them on in the account settings.

Related