The traders who win aren't smarter. They're faster.
RPC, Yellowstone gRPC, and sending for copy-trading bots and live apps. One account.
◆ End of service
rpc edge is shutting down.
New plans, checkout, and renewals are closed. Existing customers should prepare to move their workloads to another provider.
Your dashboard remains available for account details, billing history, and support. Thank you for building with us.
Interested in acquiring rpc edge?
We are open to acquisition enquiries. If you are interested in the product or technology, contact us to discuss the possibilities.
Discuss an acquisition◆ FROM QUERY TO STREAM
Polling adds work. Streaming removes it.
One persistent stream keeps your app current.
Use JSON-RPC for state and history. Use Yellowstone gRPC when your bot or app needs filtered updates as they happen.
Read the Yellowstone gRPC docs →- REGION
- FRA
- INTERFACES
- HTTP · gRPC
- ACCESS
- Self-serve
- TENANCY
- Shared · dedicated
◆ WHY rpc edge
A cleaner path from chain to app.
Use only what you need.
RPC reads, live streams, and transaction sending work through one account. Start with a copy-trading bot, DLMM strategy, or real-time app, then add capacity as the workload grows.
Subscribe instead of polling
Yellowstone gRPC pushes filtered account, slot, and transaction updates over one persistent stream, so your bot does not need to rebuild the same polling loop.
explore Yellowstone gRPC →Choose the data your workload needs
Use standard RPC for state and history, Yellowstone gRPC for live validator updates, or decoded shreds when earlier intent matters to the strategy.
what are shreds? →Start shared, move dedicated
Launch on a self-serve plan with included bandwidth. Move to private bare metal, regional placement, and an SLA when traffic or latency requirements justify it.
see the benchmarks →◆ OFFERINGS
One account. Four infrastructure products.
Read Solana state, stream live changes, access decoded shreds, and submit signed transactions without stitching together four providers.
RPC
Solana reads, writes, simulations, and subscriptions over familiar HTTP and WebSocket interfaces - with included bandwidth instead of credit math.
Learn more →Yellowstone gRPC
React to live state instead of polling. Geyser-based gRPC streams accounts, slots, and transactions the moment the validator processes them - one stream, server-side filters.
Learn more →Decoded Shreds
See transaction intent before normal processed metadata. Reconstructed from shreds and delivered over gRPC as SubscribeDeshred, without forcing every customer to rebuild shreds themselves.
Learn more →Transaction Sender
Land transactions, don't just submit them. JSON-RPC compatibility plus raw HTTP and QUIC relay paths - co-located, policy-aware, and built for route telemetry.
Learn more →◆ THE BUILDER PATH
Read state.
Stream updates. Send.
Use one account for the three jobs most Solana bots and real-time apps need: fetch current state, subscribe to live changes, and submit signed transactions.
Query state and history
Use familiar Solana JSON-RPC and WebSockets for balances, accounts, transaction history, simulation, and subscriptions.
React to live updates
Subscribe to filtered accounts, slots, and transactions over Yellowstone gRPC instead of repeatedly polling the same endpoints.
Submit signed transactions
Send through JSON-RPC-compatible, raw HTTP, or QUIC paths, then use route telemetry to understand how submissions were handled.
New to RPC, Yellowstone, and Solana data terms? Start with the glossary →
◆ MEASURED, NOT CLAIMED
Proof for what you can buy now.
Current stream and sender evidence comes first. Network-path research stays public, with its product boundary attached.
Deshred arrived first 99.92% of the time
4.64 ms median lead over processed gRPC on the same Pump AMM signatures, measured from Frankfurt.
Decision: Assess whether preprocessed data can surface matching transactions ahead of processed gRPC for this workload.
Limit: One Frankfurt Pump AMM signature set, not a guarantee for every filter, region, or transaction.
Inspect stream report →96.32% observed in the public baseline
104 ms median submit-to-first-seen in the initial one-hour QUIC sender run, with the full tail preserved.
Decision: Inspect submit-to-first-seen behavior and the full tail before testing your own transaction route.
Limit: A one-hour public baseline, not a provider comparison or service-level guarantee.
Inspect sender report →PoH: DoubleZero earlier or tied 98% of pairs
91 earlier · 106 same · 4 public earlier. DZ IBRL edge scales with leader distance; within Europe the PoH gap is negligible.
Decision: Judge where private network routing changed leader-paced placement as leader distance increased.
Limit: DoubleZero IBRL research only. DoubleZero-backed fastest shreds are not included in current self-serve plans.
Inspect paired A/B report →ProofRun by the operators who rack the bare metal. Benchmarks published raw and unedited - tail latency included.
See the published benchmark →