ToolsThe story, in brief

Cloudflare Workers Accept Inbound TCP, with gRPC the First Protocol on Top

Eight years. Cloudflare just broke Workers' HTTP-only wall with inbound TCP and native gRPC support.

Illustration of two anonymous hands arranging task cards around an amber tool on a shared desk.
People, judgement and the changing nature of work.AI illustration by KeyNews
The KeyNews take

Why it matters

Cloudflare Workers expands beyond request-response HTTP into stateful, bidirectional protocols. Practitioners building real-time or gRPC-native services now have a new edge-compute option; this widens the addressable use case for serverless at the edge.

The key facts

12 to know
  1. Cloudflare Workers now accept inbound TCP connections via new connect(socket) handler

  2. 8-year restriction to HTTP now lifted

  3. gRPC support: full-duplex for Containers, unary + server-streaming for Workers via automatic gRPC-web translation

  4. Routed through Spectrum

  5. Feature currently in private beta

  6. Multiple language support for gRPC

  7. Cloudflare Workers now accept inbound TCP via Spectrum routing

  8. Eight-year restriction to HTTP lifted

  9. Containers get full-duplex gRPC in any language

  10. Workers get unary and server-streaming via gRPC-web translation

  11. Feature is in private beta

  12. Published August 29, 2026

Go to the source

InfoQ AI/MLinfoq.com

Publisher excerpt: Cloudflare Workers can now accept inbound TCP connections through a new connect(socket) handler routed via Spectrum, ending an eight-year restriction to HTTP. Containers get full-duplex gRPC in any language, while Workers get unary and server-streaming through automatic gRPC-web translation.…
Read original report
Back to today's editionMore tools news

Keep reading

Related stories

More from Tools