Solana RPC, tuned for trading.
Performance-tuned Solana RPC over HTTP and WebSocket - co-located with the cluster, single-tenant on dedicated, and scoped for live trading reads rather than archive workloads.
50% OFFLaunch offer on Trader, from $249/mo. Paid onboarding support on request.
◆ OVERVIEW
Solana RPC is the JSON-RPC API that applications use to read on-chain state and submit transactions to the network. Over HTTP you make one-shot calls like getAccountInfo and sendTransaction; over WebSocket you subscribe to account, log, and signature updates.
rpc edge runs Solana JSON-RPC over HTTP and WebSocket on infrastructure racked beside Solana stake clusters and the Jito Block Engine. It is the live read-and-write workhorse of your trading stack: account lookups, simulations, subscriptions, and transaction submission.
Where public and shared endpoints add hops, rate limits, and unpredictable latency, our nodes are tuned end to end - kernel, network stack, and RPC layer - so your reads return fast and your writes reach the leader.
Available on Trader from $249/mo.
◆ CAPABILITIES
What Solana RPC does.
One endpoint, live reads and subscriptions
HTTP JSON-RPC for live reads and simulations, plus WebSocket subscriptions for accounts, logs, slots, blocks, and signatures.
No credit counting
Plans are scoped to throughput and bandwidth, not opaque per-method credits. Heavy account and history methods are explicitly limited on shared plans.
Co-located, low-hop
Racked beside stake clusters and the Jito Block Engine, so the distance between you and the cluster stays at the floor the network allows.
Single-tenant option
On dedicated, your RPC runs on private bare-metal - your tail latency and jitter are yours alone.
// read and write over the same co-located endpoint
const account = await rpcedge.getAccountInfo(PUBKEY, {
commitment: "processed",
});
const sig = await rpcedge.sendTransaction(tx, {
skipPreflight: true,
maxRetries: 0, // you own the retry loop
});◆ WHY rpc edge
Latency is a location problem.
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.
Choose the data your workload needs
Use standard RPC for state and history, Yellowstone gRPC for live validator updates, or preprocessed transactions when earlier intent matters to the strategy.
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.
◆ USE CASES
- Trading bots that need fast, reliable reads and writes
- Trading apps that need live reads without archive-RPC assumptions
- Apps moving off public endpoints to predictable infra
Frequently asked questions
What is Solana RPC?
How is this different from a public or shared RPC?
Do you charge per method or per credit?
◆ GET ACCESS
Move your reads and writes onto tuned infra.
Pick a plan and point your client at a scoped endpoint, or talk to the infra team to scope a dedicated, co-located node tuned to your latency and volume.
50% OFFLaunch offer on Trader, from $249/mo. Paid onboarding support on request.
HTTP · WS
- One endpoint, live reads and subscriptions
- No credit counting
- Co-located, low-hop
- Single-tenant option