> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog.md).

# Bolt-ons catalog

**Bolt-ons** are **optional add-ons** to the standard Reach platform.

Use this page to:

* **Find the right bolt-on**
* Understand **how to request one**
* Understand common **commercial** and **timeline expectations**

### Bolt-ons (available)

Start here for the most common bolt-ons:

1. [Product Bundle Integration](/customizations-and-bolt-ons/product-bundle-integration.md)
2. SSO
   1. [SSO — Agents](/customizations-and-bolt-ons/sso-agents.md)
   2. [SSO — End Customers](/customizations-and-bolt-ons/sso-end-customers.md)
3. [Custom App Hosting](/customizations-and-bolt-ons/custom-app-hosting.md)
4. [Custom SFTP Setup](/customizations-and-bolt-ons/custom-sftp-setup.md)

{% hint style="info" %}
Some bolt-ons are only available to some **brands**, **networks**, or **launch stages**.
{% endhint %}

### How to request a bolt-on

1. Share your goal, target date, and impacted customer journeys.
2. Provide the required brand inputs listed on the bolt-on’s page.
3. Reach confirms feasibility, scope, and any constraints.
4. Reach implements the change and shares it in a test environment.
5. After brand sign-off, Reach enables it in production.

### Commercial & timeline notes

* Bolt-ons must be included in the **commercial agreement**
* Some bolt-ons extend onboarding due to **discovery**, **build**, and **testing**
* Post-launch enablement typically requires a **formal change request**

<figure><img src="/files/HwsKW3lf63l10HomLG48" alt=""><figcaption></figcaption></figure>

### Questions or support

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at <account-desk@reachplatform.com> for help and support.
{% endhint %}


---

# 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.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog.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.