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

# Add-ons

An add-on brings new classes to a workspace. It is a Docker image that the platform starts as an agent of its own; its classes then appear in the Functions explorer under the add-on's name and are wired like any others. Some add-ons are Heisenware's; one is whatever you write yourself.

{% hint style="info" %}

#### Add-ons and extensions

Add-ons add whole new classes. Extensions are something else: the modifiers, filters, recorders and error handlers that sit on an executor's output. See [Extensions, branching and errors](https://docs.heisenware.com/concepts/extensions-branching-and-errors.md).
{% endhint %}

## Installing one

The Functions explorer has a puzzle-piece button, **Install Extension**. It opens a small form:

* **Heisenware Extension**: the add-on to install. **Industrial Blockchain** and **RAG AI** are Heisenware's; **Custom Extension** asks for the **Full image name** of your own.
* **Environment Variables**: one line per setting the image expects, written `NAME: value`, for credentials and endpoints.

**Install** pulls the image and starts it. Installing the same image again replaces the running container, which is how you bring a new version in. **Remove** stops it and takes its classes out of the explorer.

<div align="left"><figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-3d3b166be9189055c3e2e81176dd71b014987503%2Finstall-extension.png?alt=media" alt="The Install Extension form: the add-on to install, its environment variables, and the Install and Remove buttons" width="328"><figcaption><p>The form behind the puzzle-piece button</p></figcaption></figure></div>

What you install stays installed: the add-on comes back when the platform restarts, and one you removed stays away. Each add-on signs in to the workspace with a login of its own, listed with the other [integrations](https://docs.heisenware.com/app-manager/app-manager/integrations.md).

{% hint style="warning" %}

#### Your own image needs your own server

On the Heisenware cloud only Heisenware's own images may be installed, because its servers are shared. **Custom Extension** is therefore offered on a dedicated server and on a self-hosted platform only; elsewhere the install is refused with "Own Docker images run on your own server only". A custom add-on can still run outside the platform, on your own machine, and connect in as an agent: see [Custom add-ons](https://docs.heisenware.com/developers/developers/custom-add-ons.md).
{% endhint %}

## Official add-ons

<table><thead><tr><th width="220">Add-on</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://docs.heisenware.com/reference/functions/add-ons/industrial-blockchain.md">Industrial Blockchain</a></td><td>Writes data to a tamper-evident ledger, for audit trails and proof of origin. Installed, it also gives the <a href="https://docs.heisenware.com/app-builder/app-builder/flowboard/recorder.md">recorder</a> its <strong>Blockchain</strong> retention policy.</td></tr><tr><td>RAG AI</td><td>Retrieval-augmented AI over your own documents. Not documented here yet.</td></tr></tbody></table>

## Custom add-ons

A custom add-on is your own code, in plain Node.js, running as an agent. You write the class, build the image and install it, and its functions are on the Flowboard like the platform's own. [Custom add-ons](https://docs.heisenware.com/developers/developers/custom-add-ons.md) shows the steps and the project scaffold to start from.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.heisenware.com/reference/functions/add-ons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
