> 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/app-builder/build-backend/functions/extensions.md). # Docker Extensions Docker Extensions expand platform capabilities using Docker container technology. A Docker Extension is a standard Docker image that the platform loads, executes, and exposes as functions inside the App Builder. {% hint style="info" %} #### Docker Extensions versus extension nodes Docker Extensions add completely new function classes to the platform. Do not confuse them with [extension nodes](/app-builder/build-backend/extension-nodes.md) (modifiers, filters, recorders, and error handlers), which are the small nodes that attach directly to a function output on the canvas. {% endhint %} The platform supports two categories of Docker Extensions: 1. **Official extensions**: Pre-built, managed modules maintained by Heisenware. 2. **Custom Extensions**: User-created Docker images containing custom algorithms, drivers, or proprietary logic. ## Official extensions Pre-built modules add advanced capabilities to the platform without manual coding:

Extension	Description
Industrial blockchain	Provides immutable data logging and audit trails.
RAG AI	Enables Retrieval-Augmented Generation for context-aware AI assistants.
Process simulations	Simulates utilities consumption, CNC machine telemetry, and silo fill levels.
OGC SensorThings API	Manages IoT sensor data via the standardized OGC SensorThings specification.

Once installed, these extensions run alongside standard platform services, appearing as selectable blocks in the Function Explorer.

## Custom Extensions Build a custom Docker Extension by wrapping code inside a Code Adapter and loading the image into the platform or running it on your infrastructure. See the [Custom Extensions](/app-builder/build-backend/functions/extensions/custom-extensions.md) guide for deployment steps. --- # 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/app-builder/build-backend/functions/extensions.md?ask=&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.