> For the complete documentation index, see [llms.txt](https://docs.optivalux.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optivalux.com/for-brands/pilot-program.md).

# Pilot Program

**Run the first Optivalux pilot with us.**

Optivalux is looking for a small number of design partners to put Optivalux on real products with a controlled cohort, learn together, and shape the production system.

> **Current stage:** the physical pilot is being prepared. Pilot preparation follows public-network validation and application integration. See [Current Stage](/getting-started/current-stage.md).

## Who we want to work with

* **Brands**: premium and original-product brands that want a post-sale relationship with each item.
* **Manufacturers**: makers who can place an authenticator in production and register products at source.
* **Premium-product companies**: watches, leather goods, footwear, optics, instruments and other long-lived objects.
* **Resale and platform partners**: marketplaces and authentication services that want product-level evidence before a sale.
* **Secure-hardware partners**: secure element, NFC inlay and labelling companies.

## Proposed pilot model

| Optivalux provides                       | The partner provides                     |
| ---------------------------------------- | ---------------------------------------- |
| Technical architecture                   | A suitable product category              |
| Product-identity model for your category | Sample products or a controlled cohort   |
| Certificate infrastructure               | Product metadata                         |
| Verification experience                  | Access to the relevant workflows         |
| Ownership and transfer flow              | Collaboration on authenticator placement |
| Pilot application                        | Operational feedback                     |
| Findings and a written report            | Pilot users, where appropriate           |

## Phases

1. **Scope.** Choose the product line, cohort and the questions the pilot should answer.
2. **Integrate.** Place authenticators, register products and prepare the pilot application.
3. **Operate.** Owners verify, claim and transfer real products; we observe and support.
4. **Report.** Shared findings on operations, customer response and next steps.

## Cohort, duration and success criteria

Cohort size, duration and success criteria are agreed with each partner. No standard cohort size or duration is set.

## Authenticators in pilot products

Each pilot product carries a primary authenticator and a separate **Recovery Authenticator**, so owners can restore access if the primary authenticator is lost or damaged. Authenticator placement is worked out together with the partner. See [Recovery & Protection](/product/recovery-and-protection.md).

The choice of authenticator hardware (symmetric or asymmetric) is made per category with the partner. See [Physical Authentication](/trust/physical-authentication.md).

## Expected output

A written report of findings covering operations, owner response, authenticator placement and next steps, shared with the partner.

## Commercial terms

Commercial terms for pilots are discussed individually. No pilot pricing is published.

## Start a conversation

See [Contact & Partnerships](/company/contact-and-partnerships.md), or go to [optivalux.com/contact](https://optivalux.com/contact).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.optivalux.com/for-brands/pilot-program.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.