> 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/installation-for-on-premise/system-requirements/web-client.md).
# Web Client
Review the minimum system requirements for installing aqua Web Client on Windows Server environments, including hardware specs, software prerequisites, and load balancing guidance.
Web Client can be installed on the same server as aqua server. If you intend to install aqua Web Client on a different machine, please follow the minimum system requirements as given below:
1. Windows Server 2012 R2, Windows Server 2016 or Windows Server 2019
2. Intel Core Processor 4x2,4GHz or higher / AMD 64bit Quad Core Processor 4x24,GHz or higher
3. 8 GB RAM or higher
4. At least 5 GB of free hard disk spaceaqua
5. Microsoft .NET Framework 4.7.2 or higher
\
Furthermore, a Web Client can be installed on several servers for load-balancing purposes. If you intend to set up a load balancer, please make sure to activate session stickiness.
---
# 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/installation-for-on-premise/system-requirements/web-client.md?ask=&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.