> For the complete documentation index, see [llms.txt](https://docs.duku.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duku.ai/core-concepts/products-and-targets.md).

# Products & Targets

Products define what you test. Targets define which version you test.

### Products

A **product** is the top-level object for an application or website in Duku. It stores the name, description, and general base URL for that app or site.

Common examples:

* A marketing site
* A web app
* A checkout flow

### Targets

A **target** is a concrete deployment of a product. In most teams, targets map to commits, branches, preview deployments, or production.

Explorations run against the target URL. The product base URL is reference data for the product itself.

In the app, you manage targets from the target menu in the top-right navbar, next to the active product.

Each target carries:

* **Version:** A commit SHA or build identifier
* **URL:** The exact deployment URL Duku should start from
* **Metadata:** Context like branch name, PR number, and commit message

### Relationship

```
Product: Web App
├── Target: main @ abc123 (https://www.example.com)
├── Target: PR #42 @ def456 (https://pr-42.preview.example.com)
└── Target: PR #43 @ ghi789 (https://pr-43.preview.example.com)
```

{% hint style="info" %}
Create one product per application. Use targets for environments and deploy variants.
{% endhint %}

When you use the GitHub Action, Duku creates and updates targets automatically. When you use the API directly, call `upsertSimulationTarget`.