Home / Learn / Comparison
Comparison

Hyperliquid Direct vs perps.studio Whitelabel

Understanding the value of a whitelabel layer on top of Hyperliquid's infrastructure for teams building branded trading experiences.

This is the most common question teams ask: if perps.studio routes orders to Hyperliquid, why not just use Hyperliquid directly? It is a fair question, and the answer depends entirely on what you are trying to accomplish. If you are an individual trader, you should trade on Hyperliquid directly—there is no reason to add a layer. But if you are a team, protocol, or business that wants to offer perpetual futures trading to your users as a branded product while generating revenue, the whitelabel layer is what makes that possible. This comparison is specifically for builders and operators evaluating whether to integrate Hyperliquid directly or deploy through perps.studio.

What Hyperliquid Provides

Hyperliquid is a purpose-built L1 blockchain optimized for perpetual futures trading. It provides:

  • On-chain order book – A full CLOB with sub-second block times and transparent order matching
  • Deep liquidity – Professional market makers providing tight spreads across 100+ markets
  • Settlement – On-chain settlement with cross-margin and portfolio margin support
  • Vault system – On-chain vaults for strategy deployment and copy trading
  • HIP-3 – The builder-deployed perpetuals standard that enables third parties to build on Hyperliquid infrastructure

Hyperliquid is excellent infrastructure. It handles the hard problems: matching engines, consensus, settlement, liquidation, and liquidity. For individual traders, the Hyperliquid interface (hyperliquid.xyz) is a capable trading terminal.

What Hyperliquid does not provide is operator-level infrastructure: branded frontends, revenue sharing for operators, referral management systems, sub-account administration, or turnkey whitelabel deployment. These are the capabilities perps.studio adds.

What perps.studio Adds on Top

perps.studio is an infrastructure layer that transforms Hyperliquid's trading capabilities into operator-ready whitelabel products. Here is what the layer adds:

CapabilityHyperliquid Directperps.studio Whitelabel
BrandingHyperliquid brand onlyYour domain, logo, colors, UI theme
Revenue from user tradesNone (you are a user)Fee share from all trades on your platform
Referral systemHyperliquid's referral programCustom multi-tier referral system you control
Sub-account managementPer-user onlyOperator-level sub-account administration
Vault managementHyperliquid native vaultsBranded vault interface with custom features
One-click tradingNot availableBuilt-in
User analyticsYour own trading dataPlatform-wide user and volume analytics
Custom fee tiersStandard Hyperliquid tiersConfigurable per-deployment

The core value proposition is straightforward: perps.studio turns you from a user of Hyperliquid into an operator of a Hyperliquid-powered exchange. The underlying execution quality, liquidity, and settlement guarantees remain identical—the difference is in the business and branding layer.

Revenue Model: User vs Operator

The economic difference between using Hyperliquid directly and deploying through perps.studio is the difference between paying fees and earning fees.

Direct Hyperliquid user: You pay maker/taker fees on every trade. You can earn referral commissions through Hyperliquid's referral program by sharing your referral code, but this is a personal affiliate model with Hyperliquid-defined terms and caps.

perps.studio operator: You earn a share of trading fees generated by every user on your branded platform. This is a business model, not an affiliate program. The revenue scales with your platform's user base and volume. Key differences include:

  • Revenue ownership – You earn fees as a platform operator, not as an affiliate
  • Referral control – You define your own referral tiers, commission rates, and reward structures
  • User relationships – Users are on your platform with your branding, building your brand equity
  • Volume aggregation – All user volume on your platform contributes to your revenue, not just referred users

For protocols with existing communities, the math is straightforward. If your community generates $10M in monthly trading volume and the average fee is 3.5 basis points, that represents $35,000 in monthly fees. As a perps.studio operator, you earn a share of that revenue. As a Hyperliquid referrer, your earning potential is more limited and less controllable.

Branding and User Experience Control

For many teams, brand control is as important as revenue.

When you send users to Hyperliquid directly, you are sending them to Hyperliquid's brand. Your community members become Hyperliquid users. Any brand equity, user loyalty, and engagement accrues to Hyperliquid, not to your project. There is nothing wrong with this—Hyperliquid is an excellent platform—but it means you are building someone else's user base.

A perps.studio deployment puts your brand front and center. The reference implementation, Everex, demonstrates this: it is a fully branded trading experience that uses Hyperliquid for execution but presents itself as its own platform. Users trade on Everex, not on Hyperliquid (even though Hyperliquid handles the matching and settlement behind the scenes).

Brand control extends to:

  • Domain – Your own domain (e.g., trade.yourprotocol.com)
  • Visual identity – Custom colors, logo, typography, and layout
  • User onboarding – Tailored onboarding flows for your specific audience
  • Communication – Notifications, emails, and announcements under your brand
  • Community integration – Embedding the trading experience within your existing community touchpoints

Technical Integration: API vs Whitelabel

Teams also have the option of building their own frontend on top of Hyperliquid's APIs. This is a middle ground worth examining.

Building on Hyperliquid's API directly gives you full control over the frontend but requires significant engineering effort:

  • Building a real-time trading interface with order book, charts, and position management
  • Implementing wallet connection and transaction signing flows
  • Building order management (placement, modification, cancellation)
  • Implementing margin calculations and liquidation displays
  • Handling WebSocket connections for real-time data streaming
  • Building referral tracking and revenue attribution from scratch
  • Ongoing maintenance as Hyperliquid's API evolves

perps.studio provides all of the above as a managed product. The trading terminal, order management, real-time data, margin displays, referral tracking, and revenue attribution are built in. Operators customize the branding and configuration rather than building the trading interface from scratch.

The build-vs-buy calculation depends on your team's engineering capacity and priorities. A team with experienced frontend engineers who need deep customization beyond what perps.studio supports might benefit from a direct API integration. Most teams will find that perps.studio's ready-made infrastructure gets them to market faster and with lower ongoing maintenance cost.

When Direct Hyperliquid Access Makes More Sense

In the interest of honest comparison, there are situations where using Hyperliquid directly is the better choice:

  • Individual trading – If you are a trader, just use Hyperliquid. The whitelabel layer is for operators, not end users.
  • Bot and algorithmic trading – Trading bots should connect to Hyperliquid's API directly for lowest latency and maximum control.
  • Protocol integrations that need raw API access – If you are building a yield vault, liquidation bot, or MEV strategy that needs direct protocol-level access, you should use the Hyperliquid API.
  • No need for branding or revenue – If you just want to point users to a perps exchange and do not need to capture revenue or build brand equity around the trading experience.

perps.studio is specifically valuable when you want to operate a branded exchange as a business or product feature. The infrastructure overhead it absorbs—frontend development, referral management, revenue splitting, user administration—only matters if those are capabilities you actually need.

Frequently Asked Questions

Do perps.studio users get the same execution quality as Hyperliquid direct users?

Yes. Orders placed through a perps.studio-powered interface are routed to and matched on Hyperliquid's order book. The execution quality—fills, slippage, order book depth—is identical because it is the same underlying matching engine and liquidity pool. The perps.studio layer handles branding and operator features, not order execution.

Is there additional latency when trading through perps.studio vs Hyperliquid directly?

The perps.studio frontend adds minimal overhead for order routing compared to using the Hyperliquid web interface. For most traders, the difference is imperceptible. Algorithmic traders or HFT strategies requiring the absolute lowest latency should connect to Hyperliquid's API directly, as any additional routing layer adds some non-zero latency.

Can my users withdraw directly from Hyperliquid if my perps.studio frontend goes down?

Yes. Since perps.studio routes to Hyperliquid, user funds are held on Hyperliquid's L1, not by perps.studio. Users can always access their funds directly through Hyperliquid's interface or via the Hyperliquid API, regardless of the status of the perps.studio-powered frontend. This is a key benefit of the non-custodial architecture.

How does perps.studio handle HIP-3 builder codes?

perps.studio leverages Hyperliquid's HIP-3 standard, which enables builder-deployed perpetuals and fee attribution. When a user trades through a perps.studio operator's platform, the builder code attributes those trades to the operator, enabling automatic fee sharing. This is a protocol-level mechanism on Hyperliquid, not a custom workaround.

Can I run both a direct Hyperliquid integration and a perps.studio deployment?

Yes. Some teams use the Hyperliquid API directly for their algorithmic or backend trading operations while using perps.studio for their user-facing branded exchange. The two are not mutually exclusive, and since both interact with the same Hyperliquid liquidity, users can see the same markets and depth on both.

Ready to launch your exchange?

perps.studio gives you the infrastructure to deploy a fully branded perpetual futures exchange in minutes.