> For the complete documentation index, see [llms.txt](https://docs.warpstream.com/warpstream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.warpstream.com/warpstream/kafka/advanced-agent-deployment-options.md).

# Deploy (advanced)

WarpStream BYOC Agents support a number of advanced features:

1. [Agent Roles](/warpstream/kafka/advanced-agent-deployment-options/splitting-agent-roles.md) can be used to split an Agent deployment into multiple where each split handles a subset of the functionality. This is helpful for isolating the write path, read path, and background jobs from each other.
2. [Agent Groups](/warpstream/kafka/advanced-agent-deployment-options/agent-groups.md) can be used to split a single logical WarpStream cluster at the service discovery level for isolation purposes, or so it can be flexed across multiple network boundaries (VPCs, cloud accounts, etc).
3. Agents can authenticate to the control plane with short-lived, federated OIDC tokens instead of a static Agent Key using [Workload Identity Federation](/warpstream/kafka/advanced-agent-deployment-options/workload-identity-federation.md).
4. Agents can be configured with [TLS, mTLS, and SASL authentication](https://github.com/warpstreamlabs/docs/blob/master/kafka/advanced-agent-deployment-options/broken-reference/README.md).
5. Agents can be configured to have [much lower latency](/warpstream/kafka/advanced-agent-deployment-options/low-latency-clusters.md) in exchange for higher costs.
6. Agents can be [deployed behind a standard proxy / network load balancer](/warpstream/kafka/advanced-agent-deployment-options/configure-warpstream-agent-within-a-container-or-behind-a-proxy.md) because they're completely stateless and any Agent can serve requests for any topic-partition.


---

# 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.warpstream.com/warpstream/kafka/advanced-agent-deployment-options.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.