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

# Welcome

What Heisenware is, its three parts, where to start, and the ideas behind it.

**Heisenware is an industrial application platform where AI builds the software with you.** You describe what your shop floor needs. The assistant plans the App with you, builds its logic and its pages, and shows every step as it goes. You check, change or undo anything, by asking or by hand. Underneath runs a distributed platform, so an App grows from one machine to a whole plant.

## The platform at a glance

Heisenware has three parts:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><strong>App Manager</strong></td><td>Plan Apps with the assistant, run them, and manage members, agents and integrations.</td><td><a href="https://docs.heisenware.com/app-manager/app-manager.md">App Manager tour</a></td><td><a href="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-829eca9ed1e0a19fbf849de1fa321def2c857139%2Fmanager-dashboard.png?alt=media">manager-dashboard.png</a></td></tr><tr><td><strong>App Builder</strong></td><td>Build and test an App: its logic on the Flowboard, its pages in the Page editor, with the assistant at your side.</td><td><a href="https://docs.heisenware.com/app-builder/app-builder.md">App Builder tour</a></td><td><a href="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-493b7b00a5d4b5c5cfdd89f9554fca7ed986b5de%2Fbuilder-tour.png?alt=media">builder-tour.png</a></td></tr><tr><td><strong>App Player</strong></td><td>Runs your Apps for their users, in the browser or installed on a device.</td><td><a href="https://docs.heisenware.com/app-player/app-player.md">Open and install an App</a></td><td><a href="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-9ef27f343ed06103d825f047a4870427f717eb2e%2Fwelcome-app-player.png?alt=media">welcome-app-player.png</a></td></tr></tbody></table>

## Where to start

* **New here**: [sign up and sign in](https://docs.heisenware.com/getting-started/sign-up-and-sign-in.md), then build [your first App with the assistant](https://docs.heisenware.com/getting-started/first-app-with-the-assistant.md).
* **Build it yourself**: the same App [step by step by hand](https://docs.heisenware.com/getting-started/first-app-by-hand.md), to see what the pieces are.
* **How it works**: the concepts explain one idea per page, starting with [executors and instances](https://docs.heisenware.com/concepts/executors-and-instances.md).
* **Look something up**: every [function](https://docs.heisenware.com/reference/functions.md) and [widget](https://docs.heisenware.com/reference/widgets.md) in the reference, and the words in the [glossary](https://docs.heisenware.com/reference/glossary.md).
* **Use your own AI**: [the assistant](https://docs.heisenware.com/ai-assistant/assistant.md) is built in; your own client connects through the [MCP server](https://docs.heisenware.com/ai-assistant/mcp-server.md).

## How Heisenware thinks

The pictures below come from one small App that watches a packaging line: three machines, a handful of values, one page.

### AI builds with you

The assistant knows the rules of the platform, the platform law, and builds by them: logic on the Flowboard, pages, links, variables. It works in the open. You see every step, its checkpoints let you go back at any time, and before the few things a checkpoint cannot undo — deploying, or deleting a whole App — it asks. Prefer your own AI client? The [MCP server](https://docs.heisenware.com/ai-assistant/mcp-server.md) gives it the same tools.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-f0cdbceb844f60f99cdeb70bfe6e226e5f62f3ff%2Fassistant-builds.gif?alt=media" alt="One sentence typed into the Console; the assistant reads the platform law, looks at the App, places the heading on the page, then tests the App, checks the layout and takes a screenshot of its own work"><figcaption><p>One sentence, and the App changes while you watch. The clip is sped up: the assistant went on to test what it built, look at it and correct the spacing.</p></figcaption></figure>

### See and change everything

Nothing is hidden behind the pictures. Every executor shows its inputs, its trigger and its outputs. Where clicking is not enough, you write an [expression](https://docs.heisenware.com/app-builder/app-builder/flowboard/modifier.md) in JavaScript or JSONata, and your own code joins as an [add-on](https://docs.heisenware.com/reference/functions/add-ons.md).

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-25730958514c8e416d198a9ac791bee1eafc04b0%2Fwelcome-see-and-change.png?alt=media" alt="An executor that reads the filler every two seconds, and the JavaScript expression of the modifier behind it, open on the board" width="760"><figcaption><p>The executor reads the machine; the modifier beside it picks out the four values the page needs. Both are open to you.</p></figcaption></figure>

### Widgets linked straight to your logic

Drop an executor's output onto a widget, and the widget shows its value, live. A button runs an executor, a form fills its inputs. There is no code in between. See the [widgets](https://docs.heisenware.com/reference/widgets.md).

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-78afb0cb38934f0aaa031d90698821d6b52961a7%2Fwelcome-widget-links.png?alt=media" alt="Three modifiers, each showing a live value - 70652 parts, a load of 75, the state running - with the badge of the widget it feeds underneath" width="280"><figcaption><p>One reading, three widgets: a number, a gauge and a lamp, each wired to the value it shows.</p></figcaption></figure>

### Reacts when something happens

Nothing runs in an endless loop. An executor runs when one of its triggers fires: the App starts, a value arrives, a user clicks, a timer ticks. Until then it waits, and the rest of the App keeps running. See the [Flowboard](https://docs.heisenware.com/app-builder/app-builder/flowboard.md).

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-e924e0b425f0ca72b060e4f1684f7284e6bc0be3%2Fwelcome-triggers.png?alt=media" alt="An executor carrying one trigger, every 2s when app starts, with the clock the board draws above it" width="560"><figcaption><p>This one has a clock. Take the trigger away and the executor still exists — it simply waits.</p></figcaption></figure>

### Build once, use for every machine

A class is a blueprint: the OPC UA client, the signal simulator. An instance is one living copy of it, with its own name and settings. You build the logic once and point it at the next machine by its instance name. See [executors and instances](https://docs.heisenware.com/concepts/executors-and-instances.md).

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-458fa8545c71eb299e721458a2bf056efca00e75%2Fwelcome-classes-instances.png?alt=media" alt="The same Signal Simulator class created three times, as the instances filler, capper and labeler, each with its own settings" width="700"><figcaption><p>One class, three machines. The second and the third cost a name each.</p></figcaption></figure>

### Reaches machines behind the firewall

Your machines sit in a protected network, while the platform may run in the cloud. An [agent](https://docs.heisenware.com/concepts/agents-and-where-code-runs.md) inside that network connects out to the platform, with no VPN and no open port, and runs the connectors right next to the machines.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-943726c0cb655dd483945c4768bedc727d28acdd%2Fwelcome-agent.png?alt=media" alt="Machines and a database in the plant network connect to an agent, which connects out through the firewall to Heisenware" width="760"><figcaption><p>The connection is made from the inside out. Nothing is opened towards your plant.</p></figcaption></figure>

## Where Heisenware runs

In the Heisenware cloud, hosted in Germany, or on your own servers — the same platform either way. [Cloud or on-prem](https://docs.heisenware.com/self-hosting/self-hosting.md) compares the two.


---

# 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/welcome.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.
