Direct chain reads
Block, transaction, account, and contract calls answered by your own dedicated node - no rate-limited public endpoint, no surprise quota errors mid-strategy.
Direct chain access, no middleman.
First-class blockchain RPC. Read state, broadcast transactions, and stream chain events without trusting a public endpoint to stay up. Dedicated, predictable, and wired straight into the platform's flow engine.
Anatomy of a node
Four properties, every chain.
Whatever chain you pick, the same four properties hold. The differences sit in protocol shape and historical depth - not in what the node will do for you.
WebSocket subscriptions
Subscribe to new heads, logs, pending transactions, or specific account changes. Streaming, not polling - your strategies see chain state the moment it lands.
Authoritative broadcast
Sign locally, broadcast directly. No third-party submission service, no MEV middleware unless you choose one. The node connects to its peer set on your behalf.
Archive when you need it
Full historical state on request - replay any block, audit any path, run analytics back to genesis. Comes built-in on Ethereum, opt-in on others.
What you'd do with one
Four shapes of work.
Most nodes get used for one or two of these. Pick the one closest to your strategy - it'll tell you which tier and budget to start with.
01
Strategy data feeds
Read-only state access for strategies that need on-chain prices, oracle outputs, or LP balances. Lowest call cost, highest cache hit rate.
02
DEX execution
Sign-and-broadcast transactions for swaps, LP entries, and bridge sends. Direct connectivity keeps confirmation latency predictable.
03
Indexer / scanner
Archive reads for analytics workloads, historical replay, or building a custom event index that doesn't fit a public API.
04
Mempool monitoring
Subscribe to pending transactions, watch for arbitrage opportunities, or front-run-resistant your own large orders by routing through privacy relays.
Pick a chain
One chain, or four.
Each tier is a dedicated node, not a shared rate-limited gateway. Strategy-data-only nodes are cheaper than archive ones - pick the smallest shape that answers your queries.
Ethereum Mainnet
Popular
Ethereum Mainnet
Full archive ETH node. Execution + consensus.
A dedicated Ethereum mainnet node running execution and consensus clients side-by-side, with full archive history, websocket subscriptions, and trace endpoints. The default choice when your strategy lives on Ethereum or its L2s.
Best for
ETH-native strategies · L2 watchers · DEX traders · indexers
$49
/mo
- Execution + consensus client (geth + lighthouse)
- Full archive (~14 TB) - replay any block
- WebSocket: newHeads, logs, pendingTransactions
- Trace + debug endpoints (debug_*, trace_*)
- 20 M requests / month included
- MEV-Boost ready - point at your preferred relay
Bitcoin Indexer
Bitcoin Indexer
Full Bitcoin node with electrum-style address indexing.
A Bitcoin Core full node paired with an address indexer so you can query balances, history, and UTXO sets without scanning the chain by hand. Useful for treasury operations, BTC-aware risk metrics, or Lightning peer setups.
Best for
BTC treasury · UTXO-aware strategies · Lightning operators
$39
/mo
- Bitcoin Core full node + Electrs indexer
- Address-level history, balances, and UTXO queries
- RPC + Electrum protocol both exposed
- ZMQ topic subscriptions for new block / new tx
- 10 M requests / month included
- Lightning peer + signer support on request
Multi-EVM Bundle
Multi-EVM Bundle
Arbitrum, Base, Optimism, and Polygon under one endpoint.
Four high-throughput L2 / sidechain nodes behind one routing endpoint. Same query, different chain ID. Built for cross-chain strategies, bridge ops, and any team that's tired of juggling four sets of credentials.
Best for
Cross-chain strategies · bridge operators · multi-L2 indexers
$79
/mo
- Arbitrum, Base, Optimism, Polygon - all four
- One key, one endpoint, chain selected by header or path
- Full nodes (not light clients) on each chain
- WebSocket subs across all four
- 30 M requests / month pooled across chains
- Add more EVM chains on request
Solana RPC
Solana RPC
High-throughput Solana with priority fees and Geyser plugins.
A dedicated Solana validator-grade RPC with priority-fee routing, account subscriptions, and optional Geyser plugin streaming. Built for Solana-native strategies that need consistent block-tip access without contention.
Best for
SOL-native strategies · Jito-aware traders · perp DEX operators
$59
/mo
- Dedicated full RPC node, validator-grade hardware
- Account, slot, and signature WebSocket subscriptions
- Priority-fee aware send via tip routing
- Optional Geyser plugin stream (Kafka or gRPC)
- 15 M requests / month included
- Jito relay support on request
Side by side
Every chain, same row.
| Ethereum | Bitcoin | Multi-EVM | Solana | |
|---|---|---|---|---|
| Node type | Full + archive | Full + indexer | Full × 4 | Validator-grade |
| Historical depth | Archive (full) | Full (no archive) | Recent (~10k blocks) | Recent (~432k slots) |
| WebSocket subscriptions | ✓ | ZMQ-based | ✓ | ✓ |
| Trace / debug endpoints | ✓ | - | ✓ | Limited |
| Monthly request budget | 20 M | 10 M | 30 M pooled | 15 M |
| Region | FRA · NYC | FRA | FRA · NRT | FRA · NYC |
| Private submission relay | MEV-Boost ready | - | Per-chain | Jito on request |
| Billing | Monthly | Monthly | Monthly | Monthly |
FAQ
The wire questions.
Why pay for a node when public RPCs exist?
Public endpoints rate-limit, throttle under load, and disappear without warning. A strategy that depends on the chain reading consistently can't run on shared infrastructure. The economics flip the moment your strategy's downside from a missed read exceeds the node's monthly cost.
Can I bring my own keys, or do you sign for me?
We never hold signing keys. Strategies sign transactions inside the vault using your own configuration - the node is a transport, not a signer. If you need an HSM-backed signer, that lives on the vault side.
Do you support custom or sovereign chains?
On request. EVM-compatible chains are easy - we run them as a Multi-EVM Bundle add-on. Non-EVM chains are case-by-case; talk to us about hardware and uptime requirements first.
What happens if I exceed the monthly request budget?
Soft cap. The endpoint keeps serving, you get a notification at 80 % and again at 100 %, and overflow billing kicks in at a published per-million-request rate. No throttling, no surprise outages.
Can I run multiple chains on one tier?
Multi-EVM Bundle covers four chains by default - you can add more EVM chains. For genuinely separate networks (BTC + ETH + SOL together), provision them as separate tiers and route them in your strategy code.
Spin up a node
Pick a chain. Get a key. Read.
Provisioning is fast - most chains come online inside fifteen minutes. Custom or non-EVM chains we'll quote first. Strategy templates can target a node by chain ID without any extra wiring.