Running your own node? Do the math.
Self-hosting is the right call when you need code-level control of the node itself. For market data, it means days of setup, a localhost file format to parse, and an on-call rotation, all to reproduce streams that already exist behind an API key. We run the node fleet, with automated failover, so your engineers can work on strategy instead of plumbing.
0+
markets, perps + spot + HIP-3
~$0.0B
traded daily, captured in real time
0.00B+
order events archived
Days of ops, or one command.
A node hands you raw local output and an operations problem. The same data, structured, filtered, and attributed, is one authenticated gRPC call away.
- A node gives you raw data from the moment it syncs: no archive of anything that happened before, and no derived datasets.
- Structured streams, server-side filtering, replay, and the attribution pipeline are all things you would build and maintain yourself.
- We operate a self-operated Hyperliquid node fleet with automated failover and redundancy; the watchdog pages us, not you.
What a node gives you, and what it doesn't.
A node is the raw material, not the product. Partial marks mean the data exists but the pipeline that makes it usable is yours to build and operate.
| Feature | HyperliquidRPC | Run your own node |
|---|---|---|
| Real-time | ||
| Real-time gRPC streams | — | |
| Wallet-level attribution on every fill | ◑ | |
| Exact decimal precision, end to end | ◑ | |
| Server-side coin / wallet filtering | — | |
| Historical | ||
| Historical dataset | Full archive | — |
| Derived datasets (OHLCV, PnL, liquidations) | — | |
| Operations | ||
| HyperEVM JSON-RPC | ||
| Failover and monitoring | Operated fleet, automated failover | You build and staff it |
| Setup time | Minutes (API key) | Days + ops burden |
Real-time gRPC streams
Wallet-level attribution on every fill
Exact decimal precision, end to end
Server-side coin / wallet filtering
Historical dataset
Derived datasets (OHLCV, PnL, liquidations)
HyperEVM JSON-RPC
Failover and monitoring
Setup time
◑ = partial or provider-dependent. We keep this table honest: if a cell is out of date, tell us and we will correct it.
The pipeline, already built and operated.
Everything between raw node output and usable market data, running, monitored, and backfilled before you sign up.
Minutes instead of days
An API key replaces hardware provisioning, node sync, and pipeline development. First message on the wire in under five minutes.
No ops rotation
We run the node fleet with automated failover and redundancy. Reliability is our pager duty, not yours.
Structured streams, not file parsing
Trades, order lifecycle, L2/L4 books, raw diffs, TWAP, events, and blocks as typed gRPC streams, instead of a localhost file format you decode yourself.
An archive from day one
A fresh node starts with nothing. We hand you 1.65B+ order events and 1B+ book updates already archived, in the same schema as the live feed.
Attribution and exact decimals, done
Wallet, realized PnL, fees, and maker/taker on every fill, with byte-exact decimal encoding end to end. That is the pipeline work you would otherwise build and validate yourself.
Filtering and replay
Subscribe server-side to just the coins and wallets you need, and replay any stream from a block height to backfill: capabilities a bare node does not have.
Keep your node. Run us next to it.
If you already operate a node, the cheapest evaluation is a parallel one: a Pro key and a week of comparing data quality against what your pipeline produces, plus an honest tally of the hours the pipeline costs you.
Keep your node running
Change nothing. Your existing pipeline is the control group.
Point a client at our endpoint
A Free key covers trades, the BTC ticker, and the L2 book on up to 2 coins, enough to compare precision, attribution, and continuity against your own output.
Count both columns, then decide
Diff the data, and put a number on the other side too: sync time, storage, monitoring, and the engineer-hours your rotation spends keeping it all up.
See how fast the managed path is
The quickstart goes from key creation to live trades in five commands, a fair benchmark to weigh against your node's setup time.
The questions migrations actually raise.
Mechanics, gotchas, and tier gates, answered plainly. Anything missing lives in the migration guide.
When you need code-level control of node behavior, a data path with zero third-party dependencies, or you are building node infrastructure itself. If your goal is consuming market data, a managed feed is faster to stand up and cheaper to keep running.
Structured streams, server-side filtering, replay, wallet-attribution and exact-decimal pipelines, any historical archive predating your sync, and derived datasets like OHLCV or liquidation history. Each is a build-and-operate project on top of raw node output.
We run multiple self-operated Hyperliquid nodes with automated failover and redundancy: a watchdog promotes a healthy node when one degrades. We publish numbers rather than adjectives.
One month of Pro at most. If it does not fit your workload, cancel before the next billing cycle. Compare that against the standing cost of node ops before deciding.
Enterprise includes dedicated or co-located nodes with private throughput, direct read-only database access, and custom SLAs. You get node-level isolation without the ops rotation.
Spend the week on strategy, not node ops.
A Free key takes minutes and runs happily next to your existing node while you compare.