Built to Land.
Block After Block
Average landing through Beam via Astralane vs 457 ms on standard RPC
Partner providers behind one endpoint: Astralane, bloXroute, Nozomi, Falcon
Beam on the free Start plan, up to 500 on Stream and Aperture
How Beam lands a transaction
One endpoint, four provider paths
Send a signed transaction to beam.rpcfast.com. Beam routes it through the provider you name, or the one your tip account points to.
Provider docs
Provider by name or from the tip account
Live provider score feed
Live tip-size feed per provider
Two modes, chosen per transaction
fastest by default, for HFT, arbitrage and liquidations. mev_protect against frontrunning and sandwiching. Bundles land in order or revert together.
Mode docs
fastest: HFT, arbitrage, liquidations
mev_protect: frontrun and sandwich guard
Atomic bundles on paid plans
HTTP or QUIC, your call
HTTP for sendTransaction and sendBundle. QUIC on port 9900 adds sendTransactionFast: fire and forget, no response.
QUIC docs
HTTP: sendTransaction, sendBundle
QUIC: sendTransactionFast
Rust crate beam-quic-client
Landing time in numbers
Beam vs standard RPC
127 ms faster
Beam via Astralane, 20 runs each, 20 of 20 landed.
Average landing
Beam
330 ms
Standard RPC
457 ms
At p90
Beam
589 ms
Standard RPC
1,066 ms
Providers side by side
Within 3.2 ms
Separate run: Astralane, bloXroute, Falcon, 10 runs each.
Average landing, 10 of 10 landed each
Falcon
229.6 ms
Astralane
231.6 ms
bloXroute
232.8 ms
Who Beam is built for
HFT, market making, simple arbitrage, standard liquidation bots. Any of the four providers, picked by the live score, in fastest mode.
MEV searchers, multi-leg arbitrage, complex liquidations, user-facing swaps. Bundles and mev_protect through Astralane or bloXroute.
The four providers
Tips go to the provider's accounts; Beam reads the provider from them.
Astralane
bloXroute
Nozomi
Falcon
Beam is on every plan
Beam (Beta). Support times are the first answer during support chat hours; outside them requests go best effort.
What Beam does not do
Worth knowing before you wire it into a sender.
Beam and SWQoS FAQ
What is SWQoS on Solana?
Stake-Weighted Quality of Service gives validators bandwidth to the current leader in proportion to their stake. An RPC cannot stake, so it peers with a staked validator that forwards transactions for it. During congestion, stake-backed traffic gets preferential access to the leader, while unstaked traffic is rate-limited.
Why does my Solana transaction not land with a high priority fee?
A priority fee orders transactions once they are inside the leader queue. Under congestion, unstaked traffic is rate-limited, so packets can drop before they reach the leader and the fee has no chance to count. SWQoS improves that access; it does not remove fee competition, so keep paying the fee.
Which Beam provider is best for Jito bundles and MEV protection?
For bundles, multi-leg arbitrage or user-facing swaps that need mev_protect, use Astralane or bloXroute. For single-transaction speed, any of the four works: read the provider score feed and send through the one with the best real-time score. If you set no provider, Beam derives it from the tip account in your transaction.
Does Beam add the tip instruction automatically?
No. Append the provider-specific tip transfer before signing. Minimums are 0.0001 SOL for Astralane and 0.001 SOL for bloXroute, Nozomi and Falcon; the tip feed at wss://beam.rpcfast.com/tips returns recommended tip amounts per provider, and the tip accounts are listed in the docs.
Can I use SWQoS on a free Solana RPC plan?
Yes. Beam is in beta on every plan, the free Start plan included, from 60 transactions a minute on Start to 500 on Stream and Aperture. Each send costs 5 CU. Bundles need a paid plan.
Do I need ShredStream with SWQoS?
If you compete in same-slot races, you likely want one: a faster feed shortens the time to spot the opportunity, Beam raises the odds of delivery. Pair Beam with Aperture TxStream, or with ShredStream if you prefer to decode yourself; both come with the Aperture plan. For standard, low-priority flows a regular Solana RPC endpoint may be enough.
