Topology

Topology is the live graph of your infrastructure. Polylane builds it from the clouds and repositories you connect: every resource becomes a node, every relationship becomes an edge. Agents read this context graph to reason about your architecture. You use the topology page to navigate it.

Views

The topology page offers three views over the same resources:

• Galaxy: the default. Every resource is a dot on a rotating sphere, colored by its category. Drag to rotate, scroll to zoom, click a dot to open the resource. The sphere spins slowly on its own and pauses while you hover.
• Graph: resources and their relationships as a node-and-edge diagram.
• Table: a sortable list. Pick which columns to show and sort by any of them.

Search matches resource names and ids with both exact and fuzzy matching, so paymnt still finds payment-api. Filters narrow by provider, resource type, tier, or category. The active view, search, filters, and sort are stored in the page URL, so a filtered view can be shared as a link.

Node categories

Every resource belongs to one of thirteen categories: Compute, Storage, Databases, Networking, Messaging, Security, Observability, Repositories, People & Teams, Configuration, Environments, External Services, and Other. The galaxy view colors dots by category, and every view can filter by it.

Cross-cloud links

Polylane links resources across providers during every sync by matching hostnames, Domain Name System records, and IP addresses. A CNAME record in a Cloudflare zone that points at a Render service links the zone to that service. An A record that resolves to an IP owned by a Fly.io app or an Amazon Web Services load balancer links to that resource. The graph shows the real request path even when it crosses providers.

Repositories in the graph

Connected repositories appear as first-class nodes in the same graph. Polylane reads deployment configuration inside each repository, such as Wrangler files, Fly.io and Vercel configuration, and Render blueprints, and draws deploys_to edges from the repository to the resources it deploys. See Repositories.

Resource detail

Click any resource to open its panel. The header shows its tier, its category, and the status of its checks. The busiest resources also show their issue and change counts over the last 7 days. Below the header, the panel has tabs:

• Graph: the resource within its architecture. Traverse inbound to see dependents, outbound to see dependencies, or both, up to 10 hops deep. This is how you read the blast radius of a change.
• Wiki: the resource's living document, covered below.
• Issues: issues detected on this resource, plus its recent check evaluations.
• Metrics: charts of the resource's key metrics. Select a timeframe or drag across a chart to zoom into a window.
• Logs: log events, for resource types that produce them, such as Cloudflare Workers scripts, Amazon Web Services Lambda functions, Kubernetes pods, Vercel projects, and Fly.io apps. Search with case-sensitive or regular-expression matching, add structured field filters, and expand recurring log patterns with their rates.
• Changes: the resource's change history.
• Alternate Names: extra names the agent uses to match this resource when observability providers name it differently, for example payment-api.
• Settings: turn anomaly monitoring on or off and override the tier.
• Properties: the raw properties synced from the provider.

Per-resource wikis

Every node carries a wiki: a markdown document that Polylane writes automatically each time the resource is monitored. It records what the resource is, how it behaves, and how it connects to the rest of the architecture. You can copy the markdown or regenerate the wiki on demand from the Wiki tab.

Resource tiers

Polylane ranks every resource by how critical it is to your architecture, using its traffic, dependents, configuration, and change activity. The tier sets how often anomaly checks run and how the resource's changes are handled.

The classification is automatic, and the Settings tab shows the reasoning and the data behind it: connected resources within 2 hops, direct dependents, changes over the last 7 days, and metrics over the last 7 days. Override it there when you know better; set it back to Automatic at any time.

Advisories on nodes

When Polylane finds a configuration or observability gap on a resource, an advisory appears at the top of its panel, warnings first. Each advisory explains the problem, the remediation, and 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. Ignore an advisory to move it out of the way; restore it later from the ignored list.

Ask an agent

Agents walk the same graph you see. Use it for blast radius questions:

Use polylane to find the blast radius of my payment API: list everything that depends on it within two hops, and tell me which of those resources are tier 1 or tier 2.