> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/de-documentation/installation-fur-on-premise/system-anforderungen/web-client.md).

# Web Client

### **Systemanforderungen – aqua Web Client** <a href="#systemanforderungen_-_aqua_web_client" id="systemanforderungen_-_aqua_web_client"></a>

&#x20;Der aqua Web Client kann auf demselben Server installiert werden wie der aqua Server. Wenn Sie beabsichtigen, den aqua Client auf einer anderen Maschine zu installieren, beachten Sie bitte die folgenden minimalen Systemanforderungen:&#x20;

* Windows Server 2016, Windows Server 2019 oder Windows Server 2022
* Intel Core Prozessor 4x2,4GHz oder mehr / AMD 64bit Quad Core Prozessor 4x2,4GHz oder mehr
* 8 GB RAM oder mehr
* Mindestens 5 GB freier Festplattenspeicher
* Microsoft .NET Framework 4.7.2 oder höher

&#x20;Weiterhin kann der WebClient auch für Load Balancing auf verschiedenen Servern installiert werden. Wenn Sie beabsichtigen einen Load Balancer aufzusetzen, vergewissern Sie sich, dass Session Stickyness aktiviert ist.


---

# 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.aqua-cloud.io/documentation/de-documentation/installation-fur-on-premise/system-anforderungen/web-client.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.