The resource map

A new Map page, under Respond in the sidebar, shows what your connected providers run and how each piece depends on the others. Every connection to a provider that runs or holds infrastructure puts what it reaches on the map, each resource linked to its page on the provider. See The map.

Three views. Map draws each account as a box, arranged in the direction things depend, with anything that has an open incident outlined in red. Focus shows one resource and everything up to three links away, following what it needs, what needs it, or both. Table ranks every resource by how many others depend on it, and can show only the ones with no links yet.

Every link says how it was found. A link is either reported by the provider, matched from a setting such as DATABASE_URL that names the database's exact address, added by a person, or suggested by Firefight from clues like matching names. Suggestions, such as which service uses which database, are drawn dashed and wait under To review until someone confirms or dismisses them. A setting's value is read in memory only and never stored.

Linked to the catalog. Link a resource to the catalog service it runs, and an incident that names that service lights the resource up on the map and counts toward its history.

Search everything at once. Press Ctrl K, or ⌘K on a Mac, on any dashboard page to search the map and the catalog together, by name, tag, owning team or what a service does.

Who sees it. Reading the map is its own permission. Every member sees the whole map by default, and an admin can limit someone to some environments. Agents read it once granted, with MCP tools such as get_resource_map, search_map, find_resources, blast_radius and suggest_resource_link.