Introduction
What rpc edge is, who it is built for, and how the product surface fits together.
rpc edge is built for Solana teams where milliseconds and bandwidth both matter: arbitrage desks, market makers, liquidation systems, HFT bots, trading apps, quant funds, and low-latency data teams.
The product starts from a narrow thesis:
- Streaming workloads should be priced and monitored around bandwidth, not opaque credits.
- Latency-sensitive customers should be as close as possible to the live validator path.
- Preprocessed transaction intent, processed account state, WebSocket PubSub, and transaction sending are different surfaces and should be documented as different surfaces.
The products
| Product | Best for | Status |
|---|---|---|
| RPC | live reads, simulations, WebSocket PubSub, transaction submission | available |
| WebSocket PubSub | standard Solana subscriptions and SDK compatibility | available |
| Yellowstone gRPC | filtered live accounts, transactions, slots, and blocks | available |
| Preprocessed gRPC | earlier transaction-intent stream before processed metadata | Desk |
| Transaction sender | fast transaction delivery through the rpc edge sender path | available |
| Dedicated nodes | private validator/RPC infrastructure and co-located compute | custom |
Why Frankfurt first
Frankfurt is the first region because it is a major Solana infrastructure hub and a practical base for European trading teams. The roadmap is multi-region, but we want region expansion to follow real customer latency needs instead of a vanity map. Tell us your preferred region in Telegram.
What we optimize for
- Low-latency streams - direct local paths to the Frankfurt validator stream source where the plan and filter shape allow it.
- Bandwidth clarity - included monthly bandwidth per plan and per-customer usage telemetry.
- Trading-first routes - processed gRPC, WebSocket PubSub, preprocessed transaction intent, and a transaction sender built around landing rate.
- Operational transparency - dashboards and benchmark pages are part of the product, not a later marketing add-on.
How these docs are organized
Each section in the sidebar maps to a product or topic. Use the per-page outline on the right to
jump around, and the previous / next links at the foot of each page to read in order. New here?
Start with the Quickstart: get a key, run npx rpcedge doctor, then make your first call.