> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.6.2/getting-started/installation-guide/helmut4-server.md).

# Helmut4 Server

The purpose of this guide is to provide instructions for a successful deployment of the latest version of Helmut4.

There are two hosting options for Helmut4:

* Single (standalone) server installation
* Cluster installation

### Single server

A single server is the default deployment method for Helmut4. All necessary components run on a single system which makes the setup very easy and straight forward

### Cluster installation

Customers who are facing a higher amount of users a cluster installation is an alternative solution towards load balancing and redundancy. A cluster system requires at least three individual machines which will be combined to a swarm cluster.

{% hint style="info" %}
Cluster systems does have a different SLA/support agreement compared to the default single server installation
{% endhint %}


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/v4.6.2/getting-started/installation-guide/helmut4-server.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.