Topology
Topology is the live map of your infrastructure: every resource Polylane syncs is a node and every relationship is an edge. Agents read the same graph you navigate, so what you see is what they reason over.
What it does
Polylane builds the graph from every connected cloud account and repository and refreshes it on each sync. Resources link across providers by matching hostnames, DNS records and IP addresses, so a record in one provider that points at a service in another shows the real request path. Connected repositories are nodes in the same graph, joined to the resources they deploy by deploys_to edges.
Every resource belongs to one of 13 categories, from Compute and Databases to Repositories and External Services. Each view colors by category and can filter by it.
Views
| View | What you see |
|---|---|
| Galaxy | The default: every resource as a dot on a sphere, colored by category. Click a dot to open the resource. |
| Flow | Resources and their relationships as a node-and-edge diagram. |
| Table | A sortable list with the columns you pick. |
Search matches names and ids exactly and fuzzily, so paymnt still finds payment-api. Filters narrow by provider, type, tier, category and environment, and the active view, search and filters are stored in the page URL, so a filtered view can be shared as a link.
Resource detail
Select any resource to open its panel. Advisories sit at the top, followed by these tabs:
| Tab | What it shows |
|---|---|
| Cloud Graph | The resource within its architecture: what depends on it, what it depends on, or everything connected, from one hop up to 10. This is how you read the blast radius of a change. |
| Problems | The fix runs on issues detected on this resource, plus its recent check evaluations. |
| Key questions | Provider-native queries Polylane keeps answering for this resource. Shown for Critical and Standard resources on providers that support them. |
| Settings | Anomaly monitoring on or off, the tier with the reasoning behind it, and alternate names that help the agent match the resource when observability providers call it something else. |
| Properties | The raw properties synced from the provider. |
Every resource also has a fact sheet rendered from the graph: what it is and the resources it connects to within two hops, grouped by relationship. Agents read the same fact sheet when you attach a resource to a thread.
Resource tiers
Polylane ranks every resource by how much of your architecture depends on it. The tier sets how often anomaly checks run and how the resource's changes are handled.
| Tier | Label | Description | Check frequency | Changes |
|---|---|---|---|---|
| 1 | Critical | The architecture depends on it. | Every 30 minutes | Investigated |
| 2 | Standard | An important resource. | Every 90 minutes | Investigated |
| 3 | Low | Little depends on it. | Every 18 hours | Investigated |
| 4 | Minimal | Almost nothing depends on it. | Every 3 days | Recorded, not investigated |
The classification is automatic, and the Settings tab shows the model's reasoning and the data behind it: connected resources within 2 hops, direct dependents, a peer comparison, and metrics over the last 7 days. Pick a tier there when you know better, and set it back to Automatic at any time.
Advisories on resources
When Polylane finds a configuration or observability gap on a resource, an advisory appears at the top of its panel with the problem and the remediation. Each one offers a button that starts a thread: Ask Polylane to fix it when the agent can fix it in place, Ask Polylane how to fix it otherwise.
Related
- Clouds for connecting the accounts that fill the graph.
- Repositories for how code joins the graph and what
deploys_tomeans. - Advisories for the gaps Polylane flags on resources.
- Issues for what the tiered checks raise.