> 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-partners/overview.md).

# Overview

Optivalux is infrastructure. It is useful only when the organisations around a product can take part: the people who make it, the hardware inside it, and the platforms where it is resold.

This section describes the **roles** partners can play. It does not describe existing partnerships: Optivalux has not announced any, and none should be inferred from these pages.

> **Current stage:** Optivalux is preparing its first physical pilot. Partner integrations are not yet live. See [Current Stage](/getting-started/current-stage.md).

## Partner roles

| Role                                     | Contribution                                                                                                  | Page                                                                    |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| **Manufacturers**                        | Place authenticators during production and register products at source                                        | [Manufacturers & Hardware](/for-partners/manufacturers-and-hardware.md) |
| **Secure-hardware companies**            | Secure elements, NFC inlays, tamper-evident labels and placement engineering                                  | [Manufacturers & Hardware](/for-partners/manufacturers-and-hardware.md) |
| **Resale platforms and marketplaces**    | Check product evidence and certificate standing before a sale; support owner-authorized transfer at hand-over | [Resale & Platforms](/for-partners/resale-and-platforms.md)             |
| **Authentication and service providers** | Verify products they inspect or service; take part in brand-assisted recovery where the brand designates them | [Resale & Platforms](/for-partners/resale-and-platforms.md)             |
| **Infrastructure partners**              | Components of the operated services and network infrastructure                                                | [Contact & Partnerships](/company/contact-and-partnerships.md)          |

## Principles for every partner

* **Partners do not gain ownership powers.** No partner role can transfer, reassign or take an owned product's certificate. Ownership changes only with the owner's authorization, the recipient's acceptance and fresh evidence from the product.
* **Partners do not gain brand powers by default.** Certificate standing belongs to the issuing brand. A partner acts for a brand only in roles the brand explicitly assigns, within that brand's scope.
* **Evidence is stated precisely.** Partners displaying Optivalux results state what was verified and when, using the language in [Claims & Limitations](/trust/claims-and-limitations.md).
* **Personal data stays off the record.** Partners do not receive owner identities through public verification.

## Get involved

See [Contact & Partnerships](/company/contact-and-partnerships.md).


---

# 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-partners/overview.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.