> For the complete documentation index, see [llms.txt](https://docs.openappsec.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openappsec.io/getting-started/start-with-linux.md).

# Start With Linux

## Overview

open-appsec can be deployed as an add-on for NGINX, Kong Gateway or APISIX Gateway to provide protection to any applications and APIs served by NGINX Reverse Proxy, NGINX Webserver, Kong API Gateway or APISIX API Gateway. 

{% tabs %}
{% tab title="NGINX" %}

<figure><img src="/files/A5PMdMLCT550SCWq5Nnc" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Kong Gateway" %}

<figure><img src="/files/wccmlFrXEVQxyeG5fMmo" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="APISIX Gateway" %}

<figure><img src="/files/2eluzKgtAgXlhgnfeOmp" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

### Proxy vs. locally-served applications

{% hint style="info" %}
The open-appsec agent attaches itself to the traffic being **proxied** by the Proxy Server or API server.
{% endhint %}

If the server serves applications locally, and does not serve as a proxy between an exposed domain and an internal one - open-appsec can still inspect the traffic if you change the port for the local applications to a higher port, and add a proxy rule between the exposed listening domain and port, to the same local machine at a higher port.

{% content-ref url="/pages/ongBhoz9sKZqGzExmUEn" %}
[Install open-appsec for Linux](/getting-started/start-with-linux/install-open-appsec-for-linux.md)
{% endcontent-ref %}