CUSTOM

Dedicated Solana nodes.

Private, single-tenant bare-metal nodes provisioned to your specs and co-located with stake clusters and the Jito Block Engine - the tier for HFT desks, funds, and quants.

Get started →◢ Join the community

Read the Dedicated Nodes docs →

◆ OVERVIEW

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. No noisy neighbors: your tail latency and jitter are yours alone.

This is the bespoke tier - RPC, Yellowstone gRPC, decoded shreds, and the transaction sender on infrastructure tuned to your workload, with multi-source shred aggregation, direct leader and Jito paths, and a contractual SLA. Onboarding is hands-on, with a direct line to the infra engineers who built the stack.

packet-race → current leader 0 HOPS · CO-LOCATED

// the co-located packet reaches the leader first - illustrative

◆ CAPABILITIES

What it 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.

Multi-source shreds + direct Jito

Shreds aggregated from independent sources and a direct path to the Block Engine - the full HFT stack.

SLA + direct support

A contractual uptime SLA and a direct line to the engineers who run the infrastructure.

spec
# 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.

01

Co-located by design

Our nodes are racked beside Solana stake clusters and the Jito Block Engine. Fewer hops, less distance, lower latency - physics, not promises.

02

Shreds from many sources

We aggregate shreds across multiple upstreams and serve whichever arrives first - so you never wait on a single point of delay.

03

Tuned for HFT

Every node is performance-optimized for high-frequency streaming - kernel, network stack, and RPC layer, end to end.

◆ 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

◆ RELATED

Frequently asked questions

What's the difference between dedicated and shared plans?
Shared plans run on performance-tuned multi-tenant infrastructure. Dedicated provisions private bare-metal to your specs, co-located on request, with multi-source shred aggregation and a contractual SLA - built for HFT desks, funds, and quants.
How do I get started?
Talk to the infra team. We'll scope a node to your products, volume, and region, and co-locate it close to your edge. Onboarding is hands-on.

◆ GET ACCESS

Put Dedicated Nodes on your strategy.

Start free, or talk to the infra team to scope a dedicated, co-located setup tuned to your latency and volume.

Get started →◢ Join the community

CUSTOM

  • Single-tenant bare-metal
  • Co-located on request
  • Multi-source shreds + direct Jito
  • SLA + direct support