Dedicated infrastructure for desks that can't share.
Your own node fleet, private throughput, a 99.99% SLA, and the full archive on your terms, operated by the engineers you can actually talk to. The first call is technical scoping, not a sales pitch.
- tenancy
- dedicated / co-located
- throughput
- private (provisioned, not contested)
- sla
- 99.99% · credit schedule at /sla
- history
- full archive + custom backfills
- db_access
- read-only, scoped
- access
- SSO · RBAC · audit logs
- support
- dedicated Slack · engineers on call
Everything above Pro, under one agreement.
The same streams, RPC, and archive that serve the self-serve tiers, made single-tenant, governed, and contractually backed.
Dedicated / co-located fleet
Your own Hyperliquid node (or one co-located with your stack), operated by us, used by nobody else. Pinned versions, upgrades on your change window.
Private throughput
No shared rate limits. Streams, RPC, and historical queries run at provisioned capacity that no other tenant can contest.
Custom datasets & backfills
Scoped historical builds for specific markets, wallets, or ranges, delivered to your S3/GCS bucket in Parquet, CSV, or JSONL.
Read-only DB access
Scoped, read-only access to the database behind the archive. Run your own analytics against the full tape without an export step.
SSO, RBAC & audit logs
Single sign-on, role-based access, and per-service API keys, with audit logs across every endpoint your organization touches.
Dedicated Slack
A shared channel with the engineers who run the fleet, not a ticket queue. Incidents, questions, and schema changes land there first.
White-glove onboarding
We provision endpoints, validate your subscriptions side by side with your current provider, and stay in the channel until cutover is boring.
Compliance support
Security overview, DPA, vendor forms, and SLA terms ready for review. We work your procurement process, not around it.
The fleet behind the endpoint.
Enterprise plans run on dedicated or co-located nodes inside the same architecture that serves the shared tiers, minus the sharing. Same pipeline, private throughput.
Self-operated fleet
We run our own Hyperliquid nodes, with no upstream provider between you and consensus. Versions are pinned and upgraded on a change window you can see.
Watchdog failover
Per-node health checks demote a lagging node automatically; a warm standby takes its place before your stream notices. Sequence numbers and gap replay cover the seam.
Redundant by construction
Ingest and serve layers run redundant paths across regions, so a single machine or region event never becomes your event. Incidents are published with post-mortems.
Everything your procurement team will ask for, in one folder.
Security review, legal, and vendor onboarding move in parallel with the technical evaluation, not after it. Request the pack in the contact flow below and it arrives with the first reply.
Documents are shared under NDA during scoping. Nothing here requires a signed contract first.
From scoping call to cutover in two weeks.
Onboarding is a defined process with a date on every step. You can put it in a planning doc before you've signed anything.
- Week 0
Scoping
A technical call with the engineers who run the fleet: throughput profile, markets and filters, history depth, SLA needs. The procurement pack goes out the same day so security review starts in parallel.
- Week 1
Provisioning
We stand up your dedicated or co-located node and issue private endpoints and keys. Wire-compatible with your existing QuickNode or Dwellir stubs: the endpoint changes, your code doesn't.
- Week 2
Side-by-side validation
You run our feed next to your current source and compare: sequence integrity, latency, field-level values. Cutover happens when your numbers say so, not ours.
- Ongoing
Reviews
Quarterly usage and quality reviews cover throughput headroom, cost attribution, and upcoming schema changes. The dedicated Slack channel covers everything in between.
Talk to the engineers who run the fleet.
The first call is technical scoping, not a sales pitch: your throughput profile, filters, history depth, and SLA needs. Two short steps, one business day to a reply.
Prefer email? Write to sales@hyperliquidrpc.com. The same engineers read it.