Relationships

Map the connections between every service, API, team, and resource in your organization. Understand ownership, dependencies, and impact without reading a stale architecture diagram.

Join the waitlistRequest a demo
RoadieSearch⌘+KRelationsData SourcesObject GraphWorkflowsIntegrations›RelationsPrometheus Targets> discoveredLabelsobject+11 moreProd0 K8s Services> specobject> metadataobject+2 moreProd0 K8s Namespaces> metadataobject+3 moreLaunchDarkly Usersmfastringrolestringemailstring+15 moreTenantsTenantstringadminEmailstring+10 moreGitHub Users> _additionalDataobject+19 moreReposnamestring> security_and_analy…object+82 morePPagerDuty Usersnamestringrolestringemailstring+17 more

Trusted by the world's leading companies

Snyk
Contentful
Relativity
Royal Mail
Baillie Gifford
Celonis
AstraZeneca
Yotpo
ENTITY GRAPH

How entities connect

A sample of what the relationship graph looks like in practice with teams owning components, services depending on each other, APIs being provided and consumed.

ownsownshasParthasPartdependsOnprovidesApiconsumesApiTeamPlatform TeamSystemPayment SystemComponentcheckout-svcComponentauth-serviceAPICheckout APIComponentmobile-app
Component
API
Team
System
RELATIONSHIP FEATURES

A connected graph

Isolated data points are not useful.

Dependency mapping

Track which services depend on which APIs, libraries, and infrastructure. Surface the full dependency chain of any component so engineers always know what they're building on top of.

Ownership graphs

Connect teams to the components, systems, and APIs they own. Clear ownership means faster incident response and no more guessing who to ping.

System hierarchy

Organize entities into components, systems, and domains. The hierarchy gives engineers a mental model of your architecture without reading a diagram that's three sprints out of date.

API relationships

Know who provides and who consumes every API. When an API changes, immediately see which downstream services are affected before you ship.

Impact analysis

Before making a change, traverse the relationship graph to understand blast radius. See every downstream consumer, dependent system, and affected team at a glance.

Queryable by agents

Relationships aren't just for humans. AI agents can traverse the graph to answer questions, assess risk, and assemble context for complex tasks (without hallucinating the connections).
HOW IT WORKS

From YAML to graph

Relationships live alongside your code and stay in sync automatically. No separate graph database to maintain.

01

Define in YAML

Relationships are declared in catalog-info.yaml alongside your code. Standard relation types like dependsOn, ownedBy, partOf, consumesApi are built in. Custom types are supported too.

02

Roadie ingests and links

When Roadie processes your catalog entities, it resolves all declared relationships and builds a graph. Bidirectional links are created automatically.

03

Graph is queryable

Engineers can explore relationships in the portal UI. Agents can traverse the graph via MCP. Tech Insights can query relationships for scorecards. Everything connects.

04

Stays current

As teams ship new services, deprecate APIs, and reorganize, the graph updates automatically on the next catalog sync. No dedicated graph-maintenance work required.

“Roadie has been fantastic to work with and allowed us to adopt Backstage without the overhead.”