> For the complete documentation index, see [llms.txt](https://docs.thornode.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thornode.io/infrastructure/thor-shredstream/choose-your-data-source/technical-requirements-by-option.md).

# Technical Requirements by Option

### ShredStream

* Public IP with open UDP port
* Low-latency server (Frankfurt recommended)
* 50-100 Mbps bandwidth
* Custom deshredding implementation
* FEC decoding (optional, for packet loss recovery)

### Geyser gRPC

* gRPC client library
* Stable TCP connection
* Protobuf parsing
* Subscription management logic

### RPC

* HTTP client
* JSON parsing
* Basic error handling

## Cost Considerations

| Option      | Infrastructure | Development           | Operational                |
| ----------- | -------------- | --------------------- | -------------------------- |
| ShredStream | High           | High (custom parsing) | Medium                     |
| Geyser gRPC | Medium         | Medium                | Medium                     |
| RPC         | Low            | Low                   | Low (may have rate limits) |

{% hint style="info" %}
Summary:

* ShredStream is for teams who need every millisecond of advantage and have the technical capability to handle raw shreds. It's the fastest but most complex option.
* Geyser gRPC is the sweet spot for most real-time applications. You get low latency with parsed data and reliable delivery.
* RPC is the standard choice for applications where latency isn't critical. It's simple, reliable, and widely supported.

Choose based on your latency requirements and technical capabilities. When in doubt, start with gRPC or RPC and move to Shred Stream only if you need the extra edge.
{% endhint %}


---

# 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.thornode.io/infrastructure/thor-shredstream/choose-your-data-source/technical-requirements-by-option.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.