Skip to main content
AlchemyLaunch

What is the Alchemy Edge Proxy?

What happened

Alchemy launches custom edge proxy.

Source

alchemy.comMay 13, 2026

What is the Alchemy Edge Proxy?

Article excerpt

What is the Alchemy Edge Proxy? Think of the Edge Proxy as the front door to Alchemy's RPC infrastructure. Every API request, whether it is reading Ethereum state, querying Solana accounts, or submitting a transaction on Base, passes through this ingress layer before reaching the serving infrastructure behind it. For years at Alchemy Alchemy used a major CDN as that front door. CDNs are a popular industry choice for good reason: they ship out of the box with DDoS protection, geographic routing, WAF rules, and SSL termination. For most web applications, that bundle is good enough. CDNs have spent two decades being the default ingress layer for everything from e-commerce to streaming, and they earn that position. Onchain finance has different demands. RPC traffic is bursty, latency-sensitive, geographically global, and security-critical in ways that ordinary web traffic is not. A trading bot reading state across three chains in parallel does not care that a CDN can cache a marketing page in 50 cities. It cares about the time between issuing eth_call and getting a response. A wallet syncing balances does not need a WAF rule for SQL injection. It needs the closest possible edge node and a TLS handshake that completes in single-digit milliseconds. A protocol settling positions on a derivatives exchange cannot tolerate a third-party CDN's incident timeline as a ceiling on its...

Keep reading with a free account

The rest of this article, and every signal for Alchemy, is in your free account.

Extracted from this sentence

To meet those demands, Alchemy built a custom edge proxy on bare metal: a purpose-built ingress layer designed from the ground up for high-throughput, low-latency blockchain RPC traffic.

Extracted by Autobound

From the Signal API record
Event
Launch

What this signalsA launch often needs new go-to-market and support spend.

Product
custom edge proxy

The full record

From the Signal API record

Extraction

Confidence
50%
Detected
May 13, 2026
signal_type
news
signal_subtype
launches

Use this data

Get every launch signal for Alchemy and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Alchemy this week?”

  2. Send it to your own tools

    The Signal API returns launch signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full news record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/f2a721b6-eb50-403c-8b1c-c4c864e7137f returns this record as JSON. POST /v1/companies/enrich returns every signal for alchemy.com.

{
  "signal_id": "f2a721b6-eb50-403c-8b1c-c4c864e7137f",
  "signal_type": "news",
  "signal_subtype": "launches",
  "detected_at": "2026-05-13T00:00:00+00:00",
  "company": {
    "name": "Alchemy",
    "domain": "alchemy.com"
  },
  "data": {
    "url": "https://www.alchemy.com/blog/alchemy-edge-proxy",
    "title": "What is the Alchemy Edge Proxy?",
    "excerpt": "What is the Alchemy Edge Proxy?\n\nThink of the Edge Proxy as the front door to Alchemy's RPC infrastructure. Every API request, whether it is reading Ethereum state, querying Solana accounts, or submitting a transaction on Base, passes through this ingress layer before reaching the serving infrastructure behind it.\n\nFor years at Alchemy Alchemy used a major CDN as that front door. CDNs are a popular industry choice for good reason: they ship out of the box with DDoS protection, geographic routing, WAF rules, and SSL termination. For most web applications, that bundle is good enough. CDNs have spent two decades being the default ingress layer for everything from e-commerce to streaming, and they earn that position.\n\nOnchain finance has different demands. RPC traffic is bursty, latency-sensitive, geographically global, and security-critical in ways that ordinary web traffic is not. A trading bot reading state across three chains in parallel does not care that a CDN can cache a marketing page in 50 cities. It cares about the time between issuing eth_call and getting a response. A wallet syncing balances does not need a WAF rule for SQL injection. It needs the closest possible edge node and a TLS handshake that completes in single-digit milliseconds. A protocol settling positions on a derivatives exchange cannot tolerate a third-party CDN's incident timeline as a ceiling on its own...",
    "product": "custom edge proxy",
    "summary": "Alchemy launches custom edge proxy.",
    "planning": false,
    "image_url": "https://media.alchemy.com/blog/edge-proxy-hero-2026-05.png",
    "confidence": 0.5036,
    "product_data": {
      "full_text": "custom edge proxy",
      "fuzzy_match": true
    },
    "published_at": "2026-05-13T00:00:00Z",
    "article_sentence": "To meet those demands, Alchemy built a custom edge proxy on bare metal: a purpose-built ingress layer designed from the ground up for high-throughput, low-latency blockchain RPC traffic."
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.