Clouds
Connecting a cloud account gives agents visibility into your infrastructure. Polylane syncs the account's resources into the topology, records every change, and runs detection against what it finds.
Supported providers
Cloud providers
Connect your infrastructure
Connect an account
Pick a provider
Open the console, go to Clouds, and choose Connect a cloud account. Each provider has a guided flow: AWS deploys a CloudFormation stack that creates a role in your account, and the page waits until the stack reports back. Most other providers take an API token. You can also connect from the terminal:
polylane cloud connect --provider aws
Each provider page at /integrations/<type> documents the exact credentials it needs, for example /integrations/cloudflare.
Resources sync in
Polylane discovers the resources your credentials can see and adds them to the topology as nodes, with edges for how they relate. The account header shows sync progress and a "Last synced" timestamp. Accounts re-sync automatically; force a sync any time with the Sync with Cloud action in the account header.
Run a scan
After connecting, you land on a page that offers Run scan. A scan analyses the account in the background for about a minute and writes a report covering the few risks that stand out, plus advisories, metrics, logs, and traces. Polylane keeps the 50 most recent reports per connection.
Read-only by default
New accounts are read-only. Agents can call the provider's read endpoints, but any write call is refused and the agent is told why. A workspace admin can turn read-only off in the account's Settings tab. Even with writes enabled, every write call passes a safety review, and in chat threads it is held until you explicitly confirm it.
The account page
The page opens on the account's slice of the topology: its resources as nodes, filterable by type. Select any node to open its resource page. The other tabs:
- Changes: the account's change history. Every sync is diffed against the previous snapshot. Substantive differences become change records, each with its own detail page. Noise is filtered out: deployment cleanups, certificate renewals, and changes to volatile fields never produce a record. Automations can react to new records with the
polylane.change_record.createdtrigger. See Change intelligence. - Issues: issues scoped to this account.
- Alerts: automatic triage for the account's alerts. When triage is on, alerts that fire become issues, are triaged automatically, and get an investigation when confirmed as an incident. AWS and Cloudflare accounts also list each discovered alert rule with its own toggle. Shown for AWS, Cloudflare, Vercel, and Render.
- Repositories: the source code behind the account's resources, matched from your connected repositories or added by you. Polylane reads these to understand the account. Discovery requires a connected GitHub.
- Settings: the read-only toggle, check frequency, credential rotation and testing, resource tier re-classification, preview environment monitoring for Vercel, and account deletion.
- Properties: the raw account record as JSON.
Try it from your coding agent:
Integrations
Connect Polylane to your cloud providers, code host, observability stack, communication tools, coding agents, and any Model Context Protocol server.
Topology
The live graph of every resource across your connected clouds and repositories, with a galaxy view, per-resource wikis, tiers, and advisories.