> For the complete documentation index, see [llms.txt](https://docs.prophaze.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prophaze.com/waf-onboarding/deployment-models/on-premise.md).

# On-Premise

## **System Requirements**

* Minimum 2 node cluste&#x72;**:** one WAF node and one Management node
* Prophaze WAF tested on the following operating systems in on premise deployments

<table><thead><tr><th width="404">Type</th><th>Version</th></tr></thead><tbody><tr><td>Ubuntu </td><td>22.04, 24.04</td></tr><tr><td>RHEL</td><td>8.6</td></tr></tbody></table>

#### Management Node Hardware

1. 2 vcpu&#x20;

&#x20; 2\. 8gb memory&#x20;

#### WAF Node Hardware

&#x20;  1\.  4 vcpu&#x20;

&#x20;  2\. 16gb memory&#x20;

***NOTE**: The ports 6443 of the management and the port 80 and 443 of the WAF node should be open and available. Machines should be present on same local network.Internet and ssh access are needed.*

## **Onboarding for On-Premises Customers**

&#x20;**ON-Premise WAF installation**

&#x20;Prophaze waf will be installed in the allocated VMS. (Our team will guide)

\
&#x20; **URL for login:** [**https://dash.prophaze.com/**](https://dash.prophaze.com/login)


---

# 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.prophaze.com/waf-onboarding/deployment-models/on-premise.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.
