Skip to main content
Preview. This part of the console is still being built. What you see here describes the intended behavior and can change before general availability.

Suggest products and lineage with AI

You connected source control, a registry and a cloud account, and now you have a long list of resources and no idea which ones ship together. Sorting that out by hand means opening each repository and each pipeline. Suggest with AI does that first pass for you, and you make the decisions.

Dwaar AI proposes, and a person applies. Nothing changes until you approve it.

What it can suggest​

SuggestionWhat it proposesExample
Lineage linkOne resource feeds anotherThis repository builds that image
Add to productA resource belongs in an existing productThis image belongs in Lending Portal
New productA group of resources that should be a product of its ownA service, its image and its deployment become Notifications

It works with source code, artifacts, cloud resources and vendors. APIs, AI agents and build tools are not part of it yet.

Prerequisites​

Dwaar AI must be on in Settings › AI. Then what you can do depends on your permissions:

To do thisYou need
Ask for suggestionsai:use on the organization, and read access to the resources
Decide a lineage linkresources.lineage:update
Decide an Add to productresources:attach, and products:update on the product's organization
Decide a New productproducts:create, resources:attach and products:update

Rejecting takes the same permission as approving. By default, a Developer can ask for suggestions but needs an AppSec engineer, Security admin or Administrator to approve them. See Permissions.

Asking is for signed-in people only. An API key can't start a run.

Ask from where you are working​

Where you ask decides what comes back.

Start fromButtonWhat you get
A product's Overview, on the Lineage cardSuggest with AILinks and resources that belong to this product's chain
A resource's Lineage tabSuggest with AILinks and products for this one resource
ProductsSuggest productsLinks, resources to add, and new products, across what you can see
Products, on the Not tracked tabSuggest productsOnly resources no product tracks: where each belongs, or the new product it should be part of. No links

The Lineage tab of an image with nothing linked yet, offering Suggest with AI next to Map lineage.

The Not tracked tab of Products, listing resources no product tracks, with Suggest products at the top of the page.

If suggestions are already waiting, the pane opens on them and no new run starts, so a teammate can pick up where you left off. If there are none, opening the pane is the request. Suggest again asks afresh and replaces what was waiting. Decisions already made stay.

Review what comes back​

Each suggestion is a card with its confidence, one sentence of reasoning, and the evidence behind it. Read the evidence: it names what the suggestion rests on, so you can check it. Proposed links are drawn dashed on the graph at the top.

The Suggested mappings pane, with proposed links dashed on a lineage graph above cards of suggestions, each with a confidence, a reason, evidence, Approve and Reject.

Treat confidence as a reading guide, not a verdict:

ConfidenceWhat it rests on
High confidenceScan facts that directly join the two, or several signals that agree
Medium confidenceOne solid signal
Low confidencePlausible but thin. Hidden behind a Show n low confidence button

Dwaar checks every answer before you see it. A suggestion that names a record it was not sent, crosses an organization, or breaks a product's rules is left out, and the pane tells you how many were.

Approve, change or reject​

A lineage link. Correct the kind of link if it's wrong (Builds, Deploys to, Hosts, Uses, Depends on). When the link belongs to a product, Also add both to puts both ends in that product too, so clear it if you only want the link. Then select Approve.

A lineage link card: underwriter-api Deploys to uw-prod-01, with its evidence, the option to also add both to Lending Portal, Approve and Reject.

A resource for a product. Select Approve and it joins the product.

An Add to product card proposing a resource for an existing product, with its reason and evidence.

A new product. Rename it, clear any resource that doesn't belong, then select Create product. You become its owner, and the suggestion decides its organization. To put it somewhere else, reject this one and create the product by hand.

A New product card named Notifications with four resources ticked, its reason and evidence, Create product and Reject.

Approve all high confidence approves every high confidence suggestion as written, including creating any new product with all its suggested resources. Review those cards first if you want to edit one.

Once you approve, the change is real. Here is the same product before and after:

The Lineage graph of Lending Portal before: one repository and one vendor, not connected.

The same graph after approval: loan-engine leads to underwriter-api, which leads to uw-prod-01 and Experian.

Change your mind​

Reject moves a suggestion to the Rejected view. Dwaar AI won't propose it again, even on a new run, until you select Restore.

The Rejected view with one rejected lineage link and a Restore button.

To undo an approval:

You approvedUndo it with
A lineage linkThe remove control next to the resource's name on the Lineage tab
A new productDelete the product from its row menu. Its resources stay and go back to Not tracked
A resource added to a productThe API for now: DELETE /resources/:id/products/:productId. See the REST API

What it knows, and where it stops​

Dwaar AI reads the names, identities and provider details of the resources you can see, your products, and the links that already exist. Every run is checked against your access at the moment you ask. What is sent to the model has the full list.

  • Names only go so far. Suggestions get much better once scans have collected Product context, such as the images a repository's pipeline pushes. Without it, two resources named differently may not be connected at all.
  • It reads up to 200 resources per run. When you have more, the pane says how many it read. Ask from a product or a resource, or narrow your organization scope.
  • Links stay inside one organization. A product holds resources of its organization and those below it, so nothing suggested crosses that line.
  • It can be wrong. A confident suggestion is still a suggestion, which is why a person decides.

If you see "not enough resources in scope to suggest a mapping", there is nothing to connect yet: most runs need at least two resources. Connect an integration first.

Try this next​

Open Products, go to Not tracked and select Suggest products. Approve the three suggestions you are surest of, and reject one you know is wrong. Then run it again and notice that the rejected one stays gone.