> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/wprowadzenie/architektura-platformy/moduly-wykonawcze.md).

# Execution Modules

**Execution Modules** form the core of the environment **Eximee Platform** — they are responsible for launching, executing, and supporting business processes in banking channels.\
They create a common execution layer in which defined low-code applications are processed, visualized, and made available to end users and external systems.

Each module plays a specific role in the process lifecycle — from the user interface and process engine, through case and document handling, to integrations and APIs.

## Scope

Execution modules include:

* **Eximee Core** – the core infrastructure and runtime components.
* **Eximee Forms** – the presentation layer and user forms.
* **Eximee Case Management** – task, case, and activity history handling.
* **Eximee Dashboard** – the user interface for employees and partners.
* **Eximee API** – a unified integration layer for processes and data.

## Role in the architecture

Together they create **a coherent microservices architecture**, in which:

* processes are executed by **BPMS** and exposed through **API**,
* data are stored and managed in **Core** and **Model Runtime**,
* user interactions are handled by **Forms**, **Dashboard** and **Case Management**.

Execution modules form the foundation of the entire Eximee platform - from low-code applications to banking customer service channels.


---

# 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.eximee.com/documentation/documentation-en/wprowadzenie/architektura-platformy/moduly-wykonawcze.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.