Furge / Infrastructure

How our
infrastructure
works.

Where your market data comes from. How your orders reach the exchange. What trading costs.

How market data reaches your workspace

Market data flows through Furge. Trading paths vary by venue.

Venue
connections.

See where Furge gets market data and how trades reach each venue.

Hosted jobs use Furge runtimes. Local Marketlab CLI connections run from your own machine.

Bulk

Trading

We receive live market data from Bulk and share those connections across Furge runtimes.

Several strategies can use the same data connection. Your signed orders also pass through our servers before reaching Bulk.

Market data: Bulk → Furge → Your strategy.
Orders: Your runtime → Furge → Bulk.

Hyperliquid

Trading

We collect Hyperliquid’s public market data and index it on our servers. Your strategy receives data from our market-data infrastructure.

Hyperliquid limits connections, subscriptions, and requests from each IP address. We share connections to make better use of that capacity. Your signed orders go through our servers to Hyperliquid too.

Market data: Hyperliquid → Furge → Your strategy.
Orders: Your runtime → Furge → Hyperliquid.
Hyperliquid’s API limits

HyperLink

Trading

We receive HyperLink market data through shared Furge connections. Signed orders follow the same route back to HyperLink.

HyperLink has its own exchange connections. They are managed separately from the Bulk and Hyperliquid connections.

Market data: HyperLink → Furge → Your strategy.
Orders: Your runtime → Furge → HyperLink.

Montra

Trading

Furge indexes Montra trades on Elysium mainnet for charts and market activity.

Your runtime signs Montra swaps with your Elysium automation wallet.

Market data: Montra → Furge → Your workspace.
Swaps: Your runtime → Elysium RPC → Montra contracts.

For Bulk, Hyperliquid and HyperLink, public data connections are shared. Account-update streams stay separate for each user.

Orders from those jobs are signed by your Furge runtime. If exchange capacity is full, we show an error before a new live job starts.

Europe and Tokyo.
Both live.

A closer server can reduce latency. Moving servers does not remove exchange limits.

Europe 1

Live

Our European server is live for hosted runtimes.

Tokyo 1

Live

Tokyo is now live. Run your strategies closer to exchanges in the region.

Builder fees.
A dynamic model.

Our builder fees depend on your runtime server and whether you trade manually or use automation. Rates can change.

Automation includes scripts, bots and strategies. Exchange trading fees apply separately.

  • Bulk
  • HyperLink
Reference rates · Cloud perpetual trading
ServerManualAutomation
Europe 15 bps0.05%1 bps0.01%
Tokyo 15 bps0.05%1 bps0.01%

1 basis point (bps) = 0.01%. These rates are a reference; the current fee policy for your selected server applies.

More capacity
for Hyperliquid.

Read the exchange limits

We’re looking at third-party market-data providers and running a Hyperliquid node to increase data capacity.

This is planned work. Our feed currently comes from Hyperliquid’s public API. Trading will still follow the exchange’s rules.