01.DEDICATED NODES// private infrastructure
DEDICATED NODES

Dedicated RPC nodes.
Your hardware, your speed.

Bare-metal nodes reserved for your traffic only — no rate limits, guaranteed capacity, tuned for your workload. Infrastructure for production that cannot afford compromises.

custom quote in 24h · deployed in ~48h
// deployment topology● yours alone
your bot

private link
DEDICATED
supanode

validator peer
validator cluster
02.SHARED HAS A CEILING. DEDICATED DOESN'T.// one picture
spike.log — market moves● live
shared 09:30:01 volatility ↑ · everyone hits rpc at once
shared 09:30:02 WARN latency climbing · queued behind neighbors
shared 09:30:04 ERR 429 plan cap reached · request dropped
──────────── same moment, dedicated ────────────
dedic. 09:30:01 p99 flat · capacity is yours alone
dedic. 09:30:02 tx landed · no queue, no caps
dedic. 09:30:04 ▁▁▂▁▁▂▁▁▂▁▁▂▁▁▂▁ steady
rate limits
0

the capacity is yours — fire at hardware speed

chains
ANY

our five + Ethereum, Base, Arbitrum and more on request

region
YOURS

pick the datacenter — 10+ locations on request

tuning
CUSTOM

configured for your workload, not the average user

BARE-METAL PERFORMANCE

Physical servers, not virtual machines. No hypervisor overhead, no CPU contention, no noisy neighbors — when the market moves, your latency stays the same.

TX LANDING INCLUDED

On Solana: validator-grade gRPC, Shreds, and stake-weighted submission with a Jito path.

ENGINEERS WHO RUN IT

The people who built your node answer in the same Telegram chat.

03.BUILT FOR PRODUCTION// pick your lane

Speed without caps to compete.

MEV extraction, arbitrage, sniping. Sub-block data via gRPC and Shreds, stake-weighted submission, and zero throttling through volatility — the full stack on hardware that is yours alone.

recommended: dedicated Solana node + Shreds + Sender
edge.ts// your node, your pace
const s = await grpc.subscribe() // no neighbors
await sender.send(tx)
→ landed · every volatility spike
04.YOUR NODE, SPECCED// built per order

No standard SKU — a build sheet.

Every dedicated node starts from your workload: chain, throughput, region, interfaces. We spec the hardware, tune the configuration, and hand over endpoints with an IP allowlist. The quote covers exactly what the sheet says.

start the sheet: @supanode_tgs
[SPEC SHEET — EXAMPLE]custom quote
chainsolana mainnet
hardwarebare-metal · NVMe · sized to load
regionyour choice (10+ locations)
interfacesRPC · WS · gRPC · Shreds
rate limitsnone — capacity is yours
accessIP allowlist · private link
05.HOW IT WORKS// quote → live
01Describe your workload in Telegram — chain, throughput, region
02Get a custom quote — within 24 hours
03We build and tune the node — your hardware profile, your settings
04Go live in ~48h — endpoints + IP allowlist, same interfaces as shared
same interface, dedicated hardware// drop-in
$ curl -X POST https://your-node.supanode.xyz \
-d '{"method":"getLatestBlockhash"}'
→ 200 OK · no queue ahead of you
06.THE SWITCH// shared → dedicated
hardwareshared, plan caps publishedbare-metal, reserved for you
rate limitsper-plan capsnone
configurationstandard tuningtuned for your workload
regionFrankfurt edgeyour choice — 10+ locations
pricingflat monthly, on /pricingcustom quote in Telegram
07.DEDICATED NODES FAQ// 8 questions
What is a Supanode dedicated node?

A single-tenant node — bare-metal or VM — with dedicated compute and bandwidth, built to your spec. On Solana it is a validator-grade node with gRPC, Shreds, and TPU on infrastructure reserved entirely for your traffic, plus any custom integrations built as part of setup. RPS and TPS are unlimited.

How is a dedicated node different from a shared endpoint?

Shared plans place many customers on common infrastructure with published per-tier caps. A dedicated node reserves the entire machine for you: full compute and bandwidth, unlimited RPS and TPS, your choice of region and hardware, and custom integrations built in as part of the deployment.

Which chains run on a dedicated node?

Solana, Monad, Hyperliquid, and BNB Chain today, with more ecosystems built on request. Each is single-tenant with private endpoints in the region and on the hardware you choose. Per-chain dedicated details live on each ecosystem service page.

Are there rate limits on a dedicated node?

No. RPS and TPS are unlimited; the only ceiling is the hardware itself, which is sized to your workload at quote time. Shared-tier budgets, sliding windows, and method weights do not apply — the full capacity of the machine is yours.

Does a dedicated Solana node include transaction landing?

Yes. A dedicated Solana node is validator-grade and ships with gRPC, Shreds, and TPU on your own hardware, so the transaction path runs on a box reserved for your traffic. The stake-weighted TPU Sender also remains available as a drop-in, pay-per-use service alongside it.

How do I migrate from my current provider?

Each node speaks the standard interfaces of its chain — JSON-RPC, WebSocket, gRPC — so migration is pointing existing clients at the private endpoints. On EVM chains such as BNB and Monad, web3.js, ethers, and viem work without changes, and the engineer who built the node stays in your Telegram channel through the cutover.

Why is there no list price?

Dedicated configs change per region, and CPU, RAM, and bandwidth availability shift weekly. Pricing is per deployment, sized to your hardware, region, and SLA, with an exact quote within 24 hours and deployment in roughly 48 hours from the first Telegram message.

Is there a free trial for dedicated nodes?

Dedicated is built per order, so it runs on a quote rather than a trial. The up-to-48-hour free trial applies to shared products — Bundles, streaming, and indexers — which are a practical way to validate a workload before committing to dedicated hardware.

Ready for dedicated?

Describe the workload, get a quote within 24h. Provisioning runs over Telegram with an engineer.