Dedicated Solana nodes.
A dedicated Solana node is private bare metal - single-tenant, co-located with stake and Jito on request - for desks that need stable p99 without noisy neighbors. Shared Trader and Desk plans stay self-serve from $249/mo when that fit is enough.
Custom, scoped per engagement - SLA-backed.
◆ OVERVIEW
Dedicated Solana nodes are private, single-tenant bare-metal Solana RPC and streaming hosts provisioned for one customer. Unlike multi-tenant shared RPC, a dedicated node removes noisy-neighbor contention so tail latency stays stable under load. rpc edge racks dedicated nodes to your specs, co-located with stake clusters and the Jito Block Engine on request, with custom stream routes and a contractual SLA.
Dedicated nodes are private bare-metal, provisioned to your specs in the region closest to your edge and co-located with Solana stake clusters and the Jito Block Engine on request. Nothing else shares the box, so no other tenant can shift your latency under load.
This is the bespoke tier - RPC, Yellowstone gRPC, preprocessed gRPC, and the transaction sender on infrastructure tuned to your workload, with custom stream routes, direct leader and Jito paths where enabled, and a contractual SLA. Onboarding is hands-on, with a direct line to the infra engineers who built the stack.
Custom - scoped per engagement, SLA-backed.
// your tail latency and jitter are yours alone
◆ CAPABILITIES
What Dedicated Nodes does.
Single-tenant bare-metal
Private nodes provisioned to your specs - no shared CPU, no noisy neighbors, deterministic tail latency.
Co-located on request
Racked beside stake clusters and the Jito Block Engine, in the region closest to your edge.
Custom streams + direct Jito
Preprocessed streams, custom routing, and direct Block Engine access where enabled - scoped to your workload.
SLA + direct support
A contractual uptime SLA and a direct line to the engineers who run the infrastructure.
# we scope a node to your workload region: closest to your edge tenancy: single-tenant bare-metal products: rpc · yellowstone-grpc · shreds · sender shred-sources: multiple (aggregated) jito: direct block-engine path sla: contractual support: direct line to infra engineers
◆ 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
- HFT desks with strict tail-latency budgets
- Funds and quant teams needing deterministic infra
- Searchers running the full first-seen-to-landing pipeline
Frequently asked questions
What are dedicated Solana nodes?
What's the difference between dedicated and shared plans?
How do I get started?
◆ GET ACCESS
Build on bare-metal that's yours alone.
Tell us your products, volume, and region - we'll scope a dedicated, co-located node tuned to your latency budget and provision it close to your edge.
Custom, scoped per engagement - SLA-backed.
CUSTOM
- Single-tenant bare-metal
- Co-located on request
- Custom streams + direct Jito
- SLA + direct support