For Bots, Arbitrage & Snipers
You run automated strategies on Solana — DEX arb, LP snipers, NFT mints, copy-traders, statistical arb across pools. Your edge is how fast you see the chain and how reliably your transactions land during congestion.
What you'll use
ShredStream
Receive raw Solana shreds before slot confirmation. Multi-region UDP delivery.
Direct Shreds
Dedicated shred delivery on a private link, your own IPs. Tier above ShredStream.
SWQOS
Stake-weighted priority routing for transactions during congestion.
How they fit together
A typical sniper or arbitrage stack looks like this:
ShredStream / Direct Shreds → decode shreds, watch pool state in flight
│
▼
your strategy logic
│
▼
SWQOS endpoint → tx lands at priority
You read pre-confirmation state via shreds, react in your strategy, submit through SWQOS to maximize landing rate. The shreds give you the time advantage; SWQOS gives you the inclusion advantage.
Picking the shred tier
| ShredStream | Direct Shreds | |
|---|---|---|
| Setup | Self-serve, instant | Self-serve, ~30 minutes |
| Tenancy | Shared (Starter / Pro) or dedicated lane (Ultra) | Dedicated link |
| Network path | Shared frontend | Per-customer link |
| Latency p50 (in-region) | Single-digit ms | 3 ms |
| Pricing | Tiered | $4,000/mo per IP |
Start on ShredStream. Move to Direct Shreds when your strategy outgrows the shared lane or when isolation becomes a hard requirement.
What you don't need
- Relayer/TPU — that's the pre-leader tx feed plus bundle submission for searchers identifying arb signals from pending txs. ShredStream is the post-sequencing feed (shreds being broadcast). They're complementary; if your strategy reads pool state from confirmed blocks-in-flight, ShredStream is correct.
Get started
- Sign up in the dashboard.
- Subscribe to ShredStream + SWQOS in your project.
- Read each product's quickstart: ShredStream, SWQOS.
- When you outgrow the shared lane, swap to Direct Shreds.