Raiden Vortex is a Solana gRPC provider: a real-time, Yellowstone-compatible streaming service that pushes Geyser account, transaction and slot updates as they happen, from Raiden-run bare metal in Frankfurt, Amsterdam, London and New York. You subscribe per region or for all four, paid in USDC. If you run a Yellowstone or Dragon’s Mouth client today, switching is a change of endpoint, not a rewrite.
FRA · AMS · LND · NYC Authorised by source IP · paid in USDC on Solana
Regional · one region
Regional Vortex
One region per subscription, from Frankfurt, Amsterdam, London or New York, with one registered IP and a flat price for the period. Bandwidth isn’t metered, and every region has a free 3-hour trial.
$650Per 30 days, per region · also $65 per day or $260 per week
Frankfurt, Amsterdam, London and New York under one subscription, with one registered IP per region and 5 TB of bandwidth shared between them. Top up from 5 TB to 105 TB when you need more.
$435Per 30 days · all four regions · 5 TB of shared bandwidth
Solana gRPC is a streaming interface to validator data. Solana validators expose a Geyser plugin interface. Yellowstone gRPC, the open-source Geyser plugin from Triton One also known as Dragon’s Mouth, serves that data over gRPC using geyser.proto. Your client opens one bidirectional Subscribe stream and sends named filters. The server then pushes every matching account, transaction or slot update as it happens. You don’t poll, you don’t parse JSON, and the filtering runs on the server. A Solana gRPC provider such as Raiden Vortex runs that stream for you, so you connect a client instead of running a validator and its plugin.
Three ways to read Solana in real time
Method
How data arrives
Encoding
Filtering
Typical use
JSON-RPC polling
You ask again on an interval
JSON over HTTP
Per request
One-off reads, low-frequency checks
WebSocket subscriptions
Server pushes, one subscription per account, program or log filter
JSON over WebSocket
One target per subscription
Wallets, notifications, light apps
Geyser gRPC (Yellowstone)
Server pushes over one long-lived stream
Protobuf over HTTP/2
Many named filters per stream, with include, exclude and required account lists
Indexers, trading systems, backends that track many accounts
Streaming over gRPC is a backend job. Browsers can’t open a raw gRPC stream, so the client runs on your server, bot or indexer.
02 / Drop-in
Drop-in for Yellowstone gRPC clients
Vortex speaks geyser.proto. That means the same Geyser service, the same bidirectional Subscribe call and the same SubscribeRequest with named filter maps. The same SubscribeUpdate comes back. The endpoint itself is one line. The checklist below covers what else changes.
−http://your-provider.example:10000
+http://fra.vortex.raiden.wtf:10001
Switching from another Yellowstone provider
Register your source IPIn the Vortex dashboard, add the public IP your client connects from, for the region you want. That address is your credential, so connect from it directly, not through a NAT or proxy that rewrites it.
Change the endpointPoint the client at http://<region>.vortex.raiden.wtf:10001, using fra, ams, lnd or nyc as the region.
Trim the SubscribeRequestRemove blocks, blocks_meta and entry. Many clients subscribe to every method by default.
Remove the token setupVortex does not use an x-token. Access comes from the registered IP.
Your account and transaction filters and your decoders stay where they are. If the stream fails with PERMISSION_DENIED: ip not whitelisted, the gateway is seeing a source IP that isn’t registered for that region.
03 / What it serves
What the Geyser stream carries: accounts, transactions, slots
Vortex streams at the account and transaction level. It does not serve block-level or entry-level subscriptions. Better to learn that here than on your first connection.
Geyser subscription types on Vortex
Subscription
Served
SubscribeRequest field
Accounts
✓Yes
accounts
Transactions
✓Yes
transactions
Slots
✓Yes
slots
Blocks
✕No
blocks, blocks_meta
Entries
✕No
entry
Transaction filter fields
Field
What it does
account_required
The transaction must touch every listed account
account_include
The transaction must touch at least one listed account
account_exclude
The transaction must not touch any listed account
vote
false drops vote transactions, true returns only votes, unset returns both
failed
false drops failed transactions, true returns only failed ones, unset returns both
Each method takes a map of named filters, and you choose the names, such as pumpfun or jupiter-swaps. Every update arrives tagged with the filter names it matched, so one stream can serve several independent jobs. Filtering runs server-side, so what you exclude never crosses the wire.
04 / Regions and access
Solana gRPC endpoints in Frankfurt, Amsterdam, London and New York
A regional subscription covers one region, and Vortex Global covers all four. Every region is served from Raiden-run dedicated bare metal next to the validators. Pick the region closest to the machine that consumes the stream.
Vortex gRPC endpoints
Region
City
Endpoint
FRA
Frankfurt
http://fra.vortex.raiden.wtf:10001
AMS
Amsterdam
http://ams.vortex.raiden.wtf:10001
LND
London
http://lnd.vortex.raiden.wtf:10001
NYC
New York
http://nyc.vortex.raiden.wtf:10001
Source IP, not a token
The IP you register in the dashboard is allowlisted on that region’s gateway. Connections from it are accepted without a per-request token.
Connect from that IP
Don’t go through a NAT or proxy that rewrites it, because the gateway would then see a different address.
One subscription, one IP
For several machines, route them through the registered address, or add another IP in the same region as its own subscription at list price. Vortex Global takes one IP in each of the four regions.
Changing the IP
You change it from the dashboard. There is a short cooldown between changes, currently 60 seconds.
Vortex serves plaintext gRPC on port 10001. Use an http:// endpoint (grpc.insecure_channel in Python), not https://: with https:// the TLS handshake fails. Full region list: Raiden regions and endpoints ↗
05 / Connect
Connect a Yellowstone client in Rust, TypeScript or Python
This is the same Subscribe call you make against any Yellowstone gRPC endpoint. Each sample streams successful, non-vote transactions that touch the pump.fun program, from Frankfurt. Any gRPC client generated from geyser.proto works the same way.
Vortex comes in two plans. Regional passes are priced per region and per period, not per gigabyte, and a one-day pass runs on the same limits as a 30-day pass. Vortex Global covers all four regions for 30 days, with bandwidth shared between them.
Regional Vortex prices, per region and per registered IP
Pass
Price
Limits
1 day
$65
Standard limits
1 week
$260
Standard limits
30 days
$650
Standard limits
20Concurrent connections
35Named filters per connection
5,000Accounts per named filter
Each price covers one region and one registered IP. A second IP in a region you already stream from is its own subscription at the same list price.
You pay in USDC on Solana from the dashboard, and each quote gets its own wallet. Payment is detected in about 30 seconds, then the subscription activates automatically. No card, no sales call.
Renewing adds the new period to your current expiry. Nothing renews on its own.
$65Per day, per region, per registered IP · $260 per week · $650 per 30 days
Vortex Global: every region, one bandwidth balance
Vortex Global puts Frankfurt, Amsterdam, London and New York under one subscription. You pay $435 for 30 days and get 5 TB of bandwidth to spend in any of the four regions, then top up when you need more. The stream is the same Vortex: same endpoints, same geyser.proto, same limits.
Global or regional
Feature
Global
Regional
Regions
All four: FRA, AMS, LND and NYC
One per subscription: FRA, AMS, LND or NYC
Price
$435 / 30 days
$65 / day, $260 / week or $650 / 30 days, per region and per IP
Bandwidth
5 TB per 30-day period, shared by the four regions
Not metered
More bandwidth
Top-ups from 5 TB to 105 TB
Not needed
Source IPs
One registered IP per region
One registered IP per subscription
Free trial
None
3 hours per region, once per account
Limits
Same
20 connections, 35 named filters, 5,000 accounts per filter
Best for
A stack that runs in several regions, or moves between them
A stack that runs in one region
Vortex Global top-ups, added to the current period
Top-up
Price
Per TB
5 TB
$175
$35
10 TB
$350
$35
15 TB
$525
$35
35 TB
$1,225
$35
55 TB
$1,925
$35
105 TB
$3,150
$30
The 5 TB are shared: what you stream in Frankfurt and in New York comes out of the same balance. 1 TB is 1,000,000,000,000 bytes.
Top-ups add bandwidth to the current period as soon as they are paid, as many times as you need. They don’t extend the period.
Nothing carries over. Unused bandwidth, top-ups included, ends with its period, and every new period starts again at 5 TB.
Renewing pays for the next 30 days, which start when the current period ends. It doesn’t refill the current balance. You can prepay up to twelve periods.
When the balance runs out, streaming pauses in all four regions until you buy a top-up or the next prepaid period starts, then resumes on its own. Usage is reported about every 60 seconds, so top up before it reaches zero.
An account holds either regional or Global Vortex, free trials included. To switch, let your regional subscriptions expire, then buy Global. Remaining regional time isn’t converted or credited.
$435Per 30 days · all four regions · 5 TB of shared bandwidth · top-ups from $175
Vortex Global is rolling out account by account. If you don’t see it in your dashboard yet, ask the team on Discord.
08 / Trial
Free Solana gRPC trial
There is no public Vortex endpoint, because access is tied to a registered IP. Instead, every region has a free 3-hour trial: once per region per account, with no payment.
Request it in the dashboardOpen the Vortex page of the dashboard, choose a region and enter the IP you will connect from.
Open a Discord ticketEvery trial request is reviewed by hand. Approvals happen from the ticket on Raiden’s Discord.
ConnectOnce the trial is approved, its 3 hours start running, on the same limits as a paid pass.
An IP that another account has already used for a trial can’t start a new one. There is no trial in a region where you already hold a live subscription. If you’d rather skip the review, a one-day pass is $65. Trials are for regional Vortex: Vortex Global has none.
09 / Fit
When Vortex fits, and when to look elsewhere
Every Yellowstone gRPC provider speaks the same protocol, so the choice comes down to what each one serves, where, and on what terms. Here is where Vortex fits, and where it doesn’t.
A good fit
Existing Geyser stacks
You run a Yellowstone or Dragon’s Mouth client and want a new endpoint without touching the integration.
Real-time indexers
Account and transaction updates go straight into a pipeline whose decoders already handle them.
Trading systems
Account state comes from the validator edge rather than from a shared public RPC.
Stacks in several regions
With Vortex Global, every region streams from one subscription and one bandwidth balance.
Leaving a public provider
You keep the same client and get a different endpoint with dedicated capacity.
Look elsewhere if
You need data before confirmation
Geyser updates arrive after processing. For pre-confirmation transactions, use decoded Solana shreds.
Your source IP keeps changing
Access is by registered IP, so serverless functions, rotating NAT and browsers don’t fit.
You rely on replay
Replaying missed slots after a reconnect (from_slot) is not documented for Vortex. Ask the team before you depend on it.
You need an uptime commitment
Our Terms of Service list Vortex among beta and early-access products, with no uptime or performance commitment.
Reading the chain is half the loop. To act on what you see, land transactions with Bolt, which runs in the same four cities plus Tokyo and has a free 5 TPS Beta tier.
10 / Raiden streams
Vortex, Pulse or Surge: Geyser gRPC or shred streaming?
Raiden sells three streams. They solve different problems, and a stack can run more than one.
Raiden Vortex, Pulse and Surge compared
Feature
Vortex
Pulse
Surge
Data
Geyser account and transaction updates
Decoded transactions from shreds
Raw shred bytes
Timing
After processing
Before block confirmation
Before block confirmation
Delivery
gRPC stream
gRPC stream
UDP
Protocol
Geyser / Yellowstone proto
raiden_binary proto
Raiden
Client changes
None if you already use Geyser
Adopt the Pulse proto
Build your own pipeline
Regions
FRA, AMS, LND, NYC
FRA, AMS, NYC
FRA, AMS, LND, NYC, TKY
From
$65 / day per region, or $435 / 30 days for all four
$70 / day per region
$49 / day per region
Best for
Anyone already on Geyser tooling
Bots, arb engines, indexers
Infra teams, custom pipelines
Shreds arrive before the block is confirmed and carry no execution result, so a transaction seen there can still fail. Geyser updates come after the node has processed the transaction. Pulse and Surge are covered on the Solana shreds page.
11 / Questions
Solana gRPC questions, answered
What is Raiden Vortex?
Raiden Vortex is a Solana gRPC provider: a paid, real-time data streaming service for Solana, run and sold by Raiden. You subscribe for a region, register the IP of the machine that will connect, and open a Yellowstone-compatible gRPC stream from that address. The stream pushes account, transaction and slot updates as the validators process them, filtered on Raiden’s side. It is a hosted service, not software you install: your side is any client generated from geyser.proto.
What is Yellowstone gRPC?
Yellowstone gRPC, also known as Dragon’s Mouth, is the open-source Solana Geyser plugin from Triton One that serves validator data over gRPC using geyser.proto. Clients open a bidirectional Subscribe stream, send named filters and receive matching updates as they happen. Raiden Vortex speaks the same protocol, so an existing Yellowstone client connects to it with a new endpoint.
Does Vortex work with my Yellowstone or Dragon’s Mouth client?
Yes. Vortex speaks the same geyser.proto, so moving over is a change of endpoint, not a rewrite. Register your source IP in the dashboard, point the client at your region’s endpoint, such as http://fra.vortex.raiden.wtf:10001, and remove blocks, blocks_meta and entry from your SubscribeRequest. Your account and transaction filters and your decoders stay as they are.
Is there a free Solana gRPC endpoint or trial?
There is no public Vortex endpoint, because access is tied to a registered IP. Every region has a free 3-hour trial instead, once per region per account and with no payment. Request it from the Vortex page of the dashboard, then open a Discord ticket: trials are reviewed by hand. If you’d rather skip the review, a one-day pass is $65. Vortex Global has no free trial.
How much does Solana gRPC cost, and is it billed by bandwidth?
Regional Vortex costs $65 per day, $260 per week or $650 per 30 days, per region and per registered IP, paid in USDC on Solana. Regional passes are flat for the period, not metered per gigabyte. Vortex Global covers all four regions for $435 per 30 days and includes 5 TB of bandwidth shared between them, with top-ups from 5 TB to 105 TB. The limits are the same on every plan: 20 concurrent connections, 35 named filters per connection and 5,000 accounts per named filter.
What is Vortex Global?
Vortex Global is one Vortex subscription for all four regions: $435 per 30 days, with 5 TB of bandwidth shared by Frankfurt, Amsterdam, London and New York and one registered IP per region. Top-ups from 5 TB to 105 TB add bandwidth to the current period. An account holds either regional or Global Vortex, not both: to switch, let your regional subscriptions expire, then buy Global.
What happens when my Vortex Global bandwidth runs out?
Streaming pauses in all four regions until you buy a top-up or your next prepaid period starts, then resumes on its own. Usage is reported about every 60 seconds, so traffic can run slightly past the allowance before the pause: watch the balance in the dashboard and top up before it reaches zero. Unused bandwidth never carries over to the next period.
What happens if my Solana gRPC stream disconnects?
Reconnect and send your SubscribeRequest again: the reconnect logic you already use with other Yellowstone providers applies. Replaying missed slots after a reconnect (from_slot) is not documented for Vortex. If your job cannot miss updates, backfill the gap from RPC, or ask the team on Discord before you rely on replay.
How is access authorised? Do I need an x-token?
No token. Vortex authorises by source IP: the address you register in the dashboard is allowlisted on that region’s gateway. Connect from that address, not through a NAT or proxy that changes it. One regional subscription covers one IP; for more machines, route them through the registered address or add another IP in the region as its own subscription at list price. Vortex Global takes one registered IP per region.
Which regions and endpoints are available?
Four regions: Frankfurt (fra.vortex.raiden.wtf), Amsterdam (ams.vortex.raiden.wtf), London (lnd.vortex.raiden.wtf) and New York (nyc.vortex.raiden.wtf), all on port 10001 with the http:// scheme. A regional subscription covers one of them, and Vortex Global covers all four. Pick the region closest to the machine that consumes the stream.
When should I use Solana gRPC instead of WebSockets?
Use gRPC when a backend tracks many accounts or programs at once: one stream carries several named filters, filtering runs on the server and updates arrive as binary Protobuf. WebSocket subscriptions suit lighter jobs, such as a wallet watching a few accounts, and JSON-RPC polling suits one-off reads. gRPC needs a server-side client, because browsers can’t open a raw gRPC stream.
Should I use Vortex or Pulse?
Use Vortex if you already run Geyser tooling and want account and transaction updates after processing, in the Yellowstone format. Use Pulse if you want transactions decoded from shreds before block confirmation and can adopt its proto. A transaction seen in shreds can still fail, and a stack can run both.
What if I need more than 20 connections?
Ask the team on Discord about a custom plan above the standard limits. Standard passes allow 20 concurrent connections, 35 named filters per connection and 5,000 accounts per named filter, and a named filter with more than 5,000 accounts is rejected.