> 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/concepts/suites-of-apps.md).

# Suites of Apps

When one App is not enough: how several Apps of a workspace share data and call each other.

A bigger setup is rarely one App. It is a **suite**: an overview for the office, one App per machine at the line, a settings App for the people who maintain it. Each is used by different people on different devices, and they work on the same data.

Three things tie a suite together.

## Named instances are the data bus

An instance belongs to its agent, not to an App. A `DataStore` named `productionOrders`, or a database connection named `internal-postgres`, is **the same object** for every App of the workspace that names it.

So Apps share state by naming the same instance, never by each keeping its own copy. The overview App reads the orders the line App writes, because both talk to `productionOrders`.

## Endpoints carry actions

When one App must make another App *do* something, the target App publishes an [endpoint](https://docs.heisenware.com/concepts/variables-and-endpoints.md#endpoints) and the caller calls it by name. Do not reach into another App's logic.

The endpoint is the contract: its name stays while the logic behind it is rebuilt. In production, a call is routed to the released version of that App.

## One rule, one place

Where several Apps write the same data under a rule, such as "an order may only be started when no other order is running on that line", put the rule in the database as a function and let every App call it. The database then enforces it in one transaction, and refuses with the rule's own message. A rule copied into three Apps is a rule that will differ in three Apps.

## Working on a suite

* **Look before you add.** Read what the workspace already has: its Apps, their pages and the tables they use. Extend a table before inventing a second one for the same thing.
* **Write the architecture down.** Which App does what, which instances carry what, which endpoints exist: that belongs in the workspace's project notes, where every member and the assistant can read it. Notes keep App ids, not links: a link names one host.
* **Checkpoint every App you touch** before a change that spans the suite, so a single rollback is possible everywhere.

## Planning a suite

A suite is worth planning before it is built. That is what the Manager's [planning](https://docs.heisenware.com/app-manager/app-manager/planning.md) seat is for: the documents and requirements go in, and what comes out is each App's identity, its devices, its language and its look, plus the notes that carry the decisions. Building then happens in each App's Builder.

What a plan cannot invent, and what you will be asked for: each App's name and its one-sentence role, the devices it runs on (they become its [screens](https://docs.heisenware.com/concepts/screens-and-layouts.md)), its language, its navigation, and the corporate design.


---

# 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/concepts/suites-of-apps.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.
