# Install the Spyderbat Event Forwarder

{% hint style="warning" %}
The Event Forwarder requires SIEM forwarding to be enabled on at least one saved query before it will receive events. See [SIEM Forwarding](/concepts/integrations/siem-forwarding.md) to set up the control plane first.
{% endhint %}

The Spyderbat Event Forwarder is an open-source binary ([github.com/spyderbat/event-forwarder](https://github.com/spyderbat/event-forwarder)) that polls the Spyderbat SIEM API and delivers events to your destination. It supports files, stdout, syslog, and HTTP webhooks.

## Deployment options

| Deployment            | When to use                         | Guide                                                                                     |
| --------------------- | ----------------------------------- | ----------------------------------------------------------------------------------------- |
| Helm chart            | Kubernetes environments             | [Helm Chart](/installation/spyderbat-event-forwarder/helm-chart.md)                       |
| Traditional installer | Linux systemd (VM, bare metal, EC2) | [Traditional Installer](/installation/spyderbat-event-forwarder/traditional-installer.md) |

Run only one Event Forwarder instance per organization. Multiple instances each deliver the full event stream, producing duplicates.

For architecture details, see [Spyderbat Event Forwarder](/concepts/integrations/spyderbat-event-forwarder.md).


---

# Agent Instructions: 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:

```
GET https://docs.spyderbat.com/installation/spyderbat-event-forwarder.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.