Private Solana RPC Nodes — New York, Frankfurt & Amsterdam

constant-k runs dedicated, bare-metal Solana mainnet RPC nodes in New York, Frankfurt and Amsterdam — hardware we build, own and tune ourselves, running a low-latency-tuned mainnet validator client with the full RPC API enabled. No white-labelled capacity, no shared queues: your requests hit the same machines whose live latency we publish on the benchmarks page.

View Pricing Live Benchmarks View All Plan Limits

Solana RPC is included on every plan, starting free. Compare plans on the pricing page, see the full per-method caps on plan limits, and watch live node health on RPC status. Need streaming instead of polling? See Kaldera (Yellowstone gRPC) and Turbo Kaldera (aRPC).

What You Get

The Full RPC API, on Hardware We Own

Every standard JSON-RPC method, transaction history included, served from EPYC-class bare metal. We index by program id and SPL token mint/owner, so heavy account queries like getTokenAccountsByOwner return fast instead of timing out.

Transaction Submission That Lands

sendTransaction is forwarded to the next five leaders with an aggressive retry service — the same path our own tooling uses. Transaction rate scales with your plan, from the free tier up to 200 tx/s on Nexus.

Clear Limits, No Surprise Bills

Flat monthly plans from 5 requests/s (Free) to 500 requests/s (Nexus), with every per-method cap published on our plan limits page. Limits apply per region — run New York, Frankfurt and Amsterdam together and your effective quota triples.

Pick Your Region, or Use Both

Dedicated hostnames per region (rpc-newyork / rpc-frankfurt / rpc-amsterdam) plus a geo-routed endpoint that sends you to the nearest node. Watch every region live on RPC status and benchmarks.

Coming From Another Provider?

Solana RPC is the standard JSON-RPC API over HTTPS with Solana PubSub over WebSocket, so any Solana SDK works unchanged. Helius calls the equivalent Solana RPC, with LaserStream WebSocket for subscriptions. Triton One publishes no product name for it and fronts WebSocket with Whirligig. QuickNode calls it RPC and WebSocket endpoints. Point your client at a constant-k endpoint, pass your API key, and nothing else in your code changes.

Connect in Seconds

Any Solana client works unchanged — point it at your endpoint and pass your API key:

curl "https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getSlot"}'

# Frankfurt:   https://rpc-frankfurt.constant-k.com/?api-key=YOUR_API_KEY
# Amsterdam:   https://rpc-amsterdam.constant-k.com/?api-key=YOUR_API_KEY
# geo-routed:  https://rpc.constant-k.com/?api-key=YOUR_API_KEY