---
title: "Why trading teams choose Alchemy for low-latency RPC"
description: "Trading teams choose Alchemy for low-latency reads and writes when the market moves, and a reliable record when money settles, even at peak volume."
---

# Why trading teams choose Alchemy for low-latency RPC

<ImageBlock
  src="https://media.alchemy.com/blog/why-trading-teams-choose-alchemy-low-latency-trading-hero-v2.jpg"
  alt="Low-latency trading is built on Alchemy"
  width={1024}
  height={576}
  priority
/>

An onchain trade starts with market data that has to land before the price moves. The order then has to execute, even in a volume spike, and the money has to reconcile with the chain afterward.

Prediction markets, exchanges, DEX infrastructure, trading apps, and market data providers run that work on Alchemy. They choose us for low latency under peak load, reliable infrastructure on the chains they trade, and engineers who help tune their stack.

## Why do trading teams choose Alchemy?

Trading teams choose Alchemy because we cover both parts of the job: low-latency reads and writes when the market moves, and a complete, reliable record when money settles, even at peak volume.

Think of it as a trading firm's two desks: the front office needs speed, and the back office needs certainty. Both reach the chain through an RPC node, the server that answers an app's requests to read blockchain data and submit transactions.

<EmbeddedTable
  table={{
    columns: [
      { key: "useCase", width: 200, title: "Use case", dataType: "object" },
      { key: "team", width: 140, title: "Team", dataType: "object" },
      {
        key: "why",
        width: 260,
        title: "Why they chose Alchemy",
        dataType: "object",
      },
      { key: "result", width: 300, title: "Result", dataType: "object" },
    ],
    data: [
      {
        useCase: { title: "Prediction market trading", tooltip: "", icon: "" },
        team: {
          title:
            '<a href="/case-studies/polymarket">Polymarket</a>',
          tooltip: "",
          icon: "",
        },
        why: { title: "Performance under pressure", tooltip: "", icon: "" },
        result: {
          title:
            "125K+ concurrent users; ingestion latency cut from ~250ms to ~100ms",
          tooltip: "",
          icon: "",
        },
        id: 0,
      },
      {
        useCase: {
          title: "DEX aggregation and order routing",
          tooltip: "",
          icon: "",
        },
        team: {
          title: '<a href="/case-studies/0x">0x</a>',
          tooltip: "",
          icon: "",
        },
        why: {
          title: "The only platform it tested that it could count on",
          tooltip: "",
          icon: "",
        },
        result: {
          title: "Sub-second quotes, 99.9% uptime",
          tooltip: "",
          icon: "",
        },
        id: 1,
      },
      {
        useCase: {
          title: "Trading products on Hyperliquid",
          tooltip: "",
          icon: "",
        },
        team: {
          title:
            '<a href="/case-studies/how-valantis-built-a-reliable-trading-experience-on-hyperliquid">Valantis</a>',
          tooltip: "",
          icon: "",
        },
        why: {
          title: "Standard node behavior and responsive engineering support",
          tooltip: "",
          icon: "",
        },
        result: {
          title: "100% successful RPC requests after migrating",
          tooltip: "",
          icon: "",
        },
        id: 2,
      },
      {
        useCase: {
          title: "Exchange deposit and withdrawal checks",
          tooltip: "",
          icon: "",
        },
        team: {
          title:
            '<a href="/case-studies/bitget-deposit-verification-alchemy">Bitget</a>',
          tooltip: "",
          icon: "",
        },
        why: {
          title: "Archive and trace data, chain coverage, reliability",
          tooltip: "",
          icon: "",
        },
        result: {
          title: "25M+ requests across 9 networks in 30 days, zero errors",
          tooltip: "",
          icon: "",
        },
        id: 3,
      },
      {
        useCase: {
          title: "Market data for terminals and agents",
          tooltip: "",
          icon: "",
        },
        team: {
          title:
            '<a href="/case-studies/how-struct-is-building-the-data-layer-for-onchain-finance">Struct</a>',
          tooltip: "",
          icon: "",
        },
        why: {
          title: "One provider across chains, plus hands-on support",
          tooltip: "",
          icon: "",
        },
        result: {
          title: "1.9B+ trades tracked on its platform (Struct-reported)",
          tooltip: "",
          icon: "",
        },
        id: 4,
      },
    ],
  }}
/>

## How does Alchemy keep latency low under real load?

We route every request at scale to reliably serve teams, and for teams with extreme peaks, we tune routes and capacity around their traffic. [Cortex](/cortex), the engine underneath our platform, moves traffic off a degraded path before traders notice.

[Polymarket](/case-studies/polymarket) chose us after testing several RPC providers. During the 2024 U.S. presidential debates, it served 125,000+ concurrent users, and $3.3 billion in bets moved through it across the election. We rerouted its requests based on p99 latency (the slowest 1% of requests) and added two dedicated node fleets. Cortex cut latency on its critical data ingestion from about 250ms to about 100ms.

> "Working with Alchemy has been nothing short of essential. The personal support, the quick turnaround on our feature asks, and the attention to our scale—Alchemy consistently goes above and beyond. They're not just an infra provider. They're part of our team."
>
> — Rodrigo, Head of Platform, Polymarket · [Read the Polymarket case study](/case-studies/polymarket)

[0x](/case-studies/0x) routes liquidity for decentralized exchanges and its own Matcha trading app. After testing the available platforms, it concluded we were the only one it could count on. On Alchemy, it generates quotes in under a second with 99.9% uptime.

## How does Alchemy keep trading infrastructure reliable?

We run the parts of the stack trading teams would rather not operate: [HyperEVM](/hyperevm) nodes on Hyperliquid, [Solana gRPC](/solana-grpc) streams, and the archive and trace data exchanges use for settlement.

[Valantis](/case-studies/how-valantis-built-a-reliable-trading-experience-on-hyperliquid) builds trading products on Hyperliquid. Its self-hosted HyperEVM node went down several times a week, and each failure could block traders from opening or closing dollar-cost averaging (DCA) positions. After moving to our HyperEVM Node, Valantis reports 100% successful RPC requests.

> "We need our infrastructure to just work so we can stay focused on building a great trading experience. Alchemy has given us a more reliable foundation and a team that is quick to help when we need it."
>
> — Deven Matthews, CEO, Valantis · [Read the Valantis case study](/case-studies/how-valantis-built-a-reliable-trading-experience-on-hyperliquid)

[Bitget](/case-studies/bitget-deposit-verification-alchemy), which serves 125 million+ users, credits a deposit only when independent sources agree, and we are one of those sources across 9 networks. Its own full nodes keep only about the last 128 blocks, so it relies on our archive data (full chain history) and trace methods (step-by-step transaction replays). Over 30 days, Bitget sent us 25 million+ requests with zero errors.

## How does Alchemy's team help trading teams tune their infrastructure?

Most teams in this post named support as a reason they chose us. Our engineers work on the problem directly, alongside each team's own engineers.

[Struct](/case-studies/how-struct-is-building-the-data-layer-for-onchain-finance), which streams market data to trading terminals and agents, benchmarked several providers before choosing us. It runs on our [Node API](/rpc-api) and WebSockets and leans on our support as it adds networks.

> "Partnering with Alchemy provides Struct with the stability our pipelines require. Pair that with hands on developer support allowing us to focus on serving our customers to the best of our abilities."
>
> — Elliot, CEO, Struct · [Read the Struct case study](/case-studies/how-struct-is-building-the-data-layer-for-onchain-finance)

## Start building trading use cases on Alchemy

We build for low-latency reads and writes under peak load, plus the archive, trace, and streaming data the back office depends on, across the chains you trade.

[Get started](https://dashboard.alchemy.com/signup) or [talk to our team](/contact-sales).

## Frequently asked questions

### Which RPC provider is best for Hyperliquid?

Alchemy runs a [HyperEVM Node](/hyperevm) that follows standard Ethereum node specs, so existing services can move over without a new operating model. [Valantis](/case-studies/how-valantis-built-a-reliable-trading-experience-on-hyperliquid) migrated its Hyperliquid trading backend from a self-hosted node to Alchemy one service at a time and reports 100% successful RPC requests since. Test any provider on your own methods first.

### What should a Solana trading app look for in an RPC provider?

Look for gRPC streaming alongside request-response RPC. Alchemy's [Solana gRPC](/solana-grpc) is Yellowstone-compatible, so existing clients move over with a URL change. Each subscription fans out across multiple upstream nodes, missed data backfills after a reconnect, and endpoints run in US East, US West, EU Central, and Asia-Pacific.

### Why do crypto exchanges use more than one RPC provider?

A single provider is a single point of failure for user funds. [Bitget](/case-studies/bitget-deposit-verification-alchemy) runs its own nodes and credits a deposit only when independent sources agree, with Alchemy as one of those sources. Over 30 days, Bitget sent Alchemy 25 million+ requests across 9 networks with zero errors.

### Which RPC providers support archive and trace data?

Alchemy provides archive data plus trace and debug methods such as `trace_block` and `debug_traceBlockByNumber`. The [Trace API](https://www.alchemy.com/docs/reference/trace-api-quickstart) is available on pay-as-you-go and Enterprise plans. Standard full nodes keep only recent blocks, roughly the last 128, so they cannot rebuild older transactions. Bitget uses this data to verify deposits.