> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thornode.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose a product

> Match a Solana workload to ThorEdge RPC, FastGate, Yellowstone, Pulse, Raw Shred Stream, Replay, or Bifrost.

Choose the product by the data your application needs and how it can receive that data. If you only need standard Solana requests or subscriptions, start with ThorEdge RPC.

## Product map

| Goal                                                 | Choose                                                             | Input                                                   | Output and transport                             |
| ---------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------- | ------------------------------------------------ |
| Call Solana JSON-RPC methods                         | [ThorEdge RPC](/products/thoredge-rpc)                             | JSON-RPC request                                        | JSON-RPC response over HTTPS                     |
| Subscribe through Solana WebSocket methods           | [ThorEdge RPC](/products/thoredge-rpc)                             | JSON-RPC subscription                                   | Events over WSS                                  |
| Run supported account-heavy queries                  | [FastGate RPC](/products/fastgate-rpc)                             | Supported account method sent to ThorEdge               | Solana account data over HTTPS JSON-RPC          |
| Receive filtered Geyser-compatible data              | [Yellowstone gRPC](/products/yellowstone-grpc)                     | Subscribe request and filters                           | Persistent gRPC stream                           |
| Receive signatures or decoded transactions over QUIC | [Pulse Decoded Shreds](/products/pulse)                            | Location target, token, feed, filters, and Pulse client | Sig-first datagrams or an ordered full-tx stream |
| Decode and process live shreds yourself              | [Raw Shred Stream](/products/raw-shred-stream)                     | Registered public IPv4 and UDP port                     | Live raw shred datagrams over UDP                |
| Re-run recently captured raw shreds                  | [Replay](/products/shredreplay)                                    | Slot range, pacing, and UDP receiver                    | Raw shred datagrams over UDP                     |
| Call a provider-specific transaction route           | [Bifrost Transaction Routes](/products/bifrost-transaction-routes) | Route-specific request                                  | Route-specific HTTP response                     |

## RPC or FastGate

**ThorEdge RPC** handles ordinary Solana JSON-RPC calls and WebSocket subscriptions. **FastGate RPC** routes supported account queries through that same HTTPS URL; it does not require a separate endpoint or credential.

Use the [RPC quickstart](/getting-started/quickstart) for either path, then verify your required method against the [FastGate method reference](/api-reference/fastgate/overview).

## Yellowstone or Pulse

**Yellowstone gRPC** provides a Geyser Subscribe-compatible stream with server-side filters. **Pulse Decoded Shreds** provides either low-overhead signature datagrams or an ordered stream of decoded transactions over QUIC; it does not send raw shred objects. Full-tx ordering begins after server enqueue and is not an end-to-end completeness guarantee.

Yellowstone sends its location token as `x-token` gRPC metadata. Pulse sends its location token in the first client control message. Copy each target and token from the same dashboard location.

## Raw Shred Stream or Replay

**Raw Shred Stream** continuously sends live raw shreds to your UDP receiver. Your application handles loss, duplication, reordering, decoding, and downstream backpressure.

**Replay** resends a slot range from the current rolling window. It covers recently captured data, not an archive or a replacement for the live stream.

Both deliver UDP datagrams to a receiver you operate. Confirm that the host has a reachable public IPv4 address and that its firewall and NAT rules permit the configured UDP port.

## Bifrost for provider-specific routes

**Bifrost Transaction Routes** lets you call a specific provider operation without opening a separate provider account or managing its API key. Bifrost aggregation is included when **Private TX** is enabled for your ThorNode access. Select the access, location, provider, and operation in the dashboard, generate a Private TX key, and copy the complete route URL.

Bifrost manages the upstream provider credentials, but your application still chooses the route and sends that route's request format. It does not imply automatic route selection, transaction landing, or confirmation. Track any returned signature according to your Solana confirmation policy.

## Find connection details

Use the **Endpoints** tab for RPC and WebSocket and its **Streaming** section for Yellowstone and Pulse. Use the separate **ShredStream**, **ShredReplay**, and **Private TX** tabs for those product flows. Select the pass or rental and location your application will use, then copy or generate the connection details shown for that selection.

Open **Limits** for the selected access before sizing throughput, filters, streams, or concurrent jobs.

## Next steps

* [Create application credentials](/dashboard/endpoints) for RPC, WebSocket, and location-based streaming access.
* [Review live usage and limits](/dashboard/usage-and-limits) before sizing concurrency.
* [Protect tokens and credential-bearing URLs](/reference/security).