Vortex Overview
Geyser-compatible gRPC stream — a drop-in for your existing Yellowstone tooling
🌬 Geyser gRPC. Yellowstone wire format. Keep your decoders, your filters, and your code.
Raiden Vortex serves a Geyser-compatible account and transaction stream from Raiden’s validator-local edge. It speaks the wire format your existing tooling already speaks, so moving over is a change of endpoint rather than a rewrite.
Why It Exists
Most Solana stacks already talk to a Geyser plugin. Rewriting that integration to gain latency is a cost that rarely pays for itself, so Vortex removes the rewrite: same protobuf, same subscription shape, same client libraries.
If you are already running a Yellowstone or Dragon’s Mouth client, point it at a Vortex endpoint and it works.
Vortex vs Surge vs Pulse
| Raiden Surge | Raiden Pulse | Raiden Vortex | |
|---|---|---|---|
| Data format | Raw shred bytes | Binary decoded transactions | Geyser account & transaction updates |
| Delivery | UDP + TCP | gRPC streaming | gRPC streaming |
| Protocol | Raiden | shreder_binary proto | Geyser / Yellowstone proto |
| Client changes | Build your own pipeline | Adopt the shreder proto | None if you already use Geyser |
| Best for | Infra teams, custom pipelines | Bots, arb engines, indexers | Anyone already on Geyser tooling |
Surge and Pulse deliver shreds, pre-confirmation. Vortex delivers a Geyser feed. They are different products solving different problems, and a stack can use more than one.
Available Regions
| Region | Location | Status |
|---|---|---|
| FRA | Frankfurt, Germany | Live |
| AMS | Amsterdam, Netherlands | Live |
| NYC | New York, USA | Live |
| LND | London, United Kingdom | Live |
Each region is a separate subscription. See Getting Started for endpoints.
Subscription Methods
Vortex serves the account, transaction and slot methods:
| Method | Supported |
|---|---|
accounts | Yes |
transactions | Yes |
slots | Yes |
blocks | No |
blocks_meta | No |
entry | No |
blocks, blocks_meta and entry are not served. Vortex streams at the account and transaction level; block-level and entry-level subscriptions are not part of it.
Many Geyser clients subscribe to every method by default. Remove those three from your SubscribeRequest before connecting.
Limits
Included at the standard $650 / month / region plan:
| Limit | Value |
|---|---|
| Concurrent connections | 20 |
| Named filters | 35 per connection |
| Account filters | 5,000 per named filter |
Filtering happens server-side, so a filter that excludes traffic also saves you the bandwidth.
Need more than this? Contact us about a custom plan.
Use Cases
Existing Geyser stacks — cut latency without touching the integration you already run in production.
Real-time indexers — account and transaction updates straight into your pipeline, in a format your decoders already handle.
Trading systems — account state changes from the validator edge rather than from a shared public RPC.
Migrating off a public provider — same client, different endpoint, dedicated capacity.