For Developers

Know what breaks before you push.

Every flow, connector and API you build depends on upstream sources and feeds downstream consumers you never see. Run an impact analysis in Asset Navigator and know what your change touches before you push the changes.

Asset Navigator showing a dataset with its upstream sources and downstream reports and AI agents

Why developers use it

The code is yours. The consequences are everybody's.

You inherit undocumented systems

The person who built the flow left. The map didn't.

Your change has hidden consumers

A renamed field or a retired connector can break a report three teams away.

"What does this touch?"

You used to answer from memory. Now you answer from the map.

HOW DEVELOPERS USE IT

Start from what you build. Follow the connections out.

01
Components

Start with what you build
Open the flow, connector or API you're working on. See which assets it links, and which datasets it reads and writes.
02
Datasets

Check before you change a schema
Before you rename a column or change a format, open the dataset and see every component and asset that consumes it, with its data classification and confidentiality.
03
Assets

See the bigger picture
Run upstream and downstream impact analysis on the application, AI agent or report your component belongs to. If it's flagged business critical or regulatory critical, you know before the review, not after.
04
Environments

Know where it runs
See which environments your component is deployed in, so a test change doesn't quietly hit production dependencies.
05
Projects

See who else shares your work
Find the other projects that reuse your datasets and components, and who to talk to before you change them.

Keep it current without extra work

Send documentation through our API from your own scripts or AI agents, inside your environment. You decide what is shared.

POST /api/components
    { "name": "orders-sync",
      "reads": ["customer_orders"],
      "env": "production" }

What you get

Ship with fewer surprises.

Fewer surprises after release

Know the consumers before you break them.

Faster onboarding

Understand an unfamiliar landscape in an hour, not a month.

Shorter reviews

Architects and compliance see the same map you do, so fewer meetings to explain dependencies.

Documentation that stays useful

One place, linked to real connections, not a wiki page from 2022.

Who it's for

Different roles. Same map.

Everyone sees what they need, and acts with confidence.

Project managers

See the potential impact of projects and changes, without relying on individual team members to explain the landscape.

IT Architects

See the technical landscape across business units and regions, to spot reuse, avoid duplicate builds and keep new solutions aligned with your architecture.

Business analysts

Understand where information comes from, how it moves through systems, and which reports or processes depend on it.

Risk & Compliance

See which assets and AI agents support your critical functions, with their classification, criticality and providers. Export your AI inventory report, ready for your auditor or regulator.