ToolsAugust 29, 2026via InfoQ AI/ML

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

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.

Key signals

  • Cloudflare Workers now accept inbound TCP connections via new connect(socket) handler
  • 8-year restriction to HTTP now lifted
  • gRPC support: full-duplex for Containers, unary + server-streaming for Workers via automatic gRPC-web translation
  • Routed through Spectrum
  • Feature currently in private beta
  • Multiple language support for gRPC
  • Cloudflare Workers now accept inbound TCP via Spectrum routing
  • Eight-year restriction to HTTP lifted
  • Containers get full-duplex gRPC in any language
  • Workers get unary and server-streaming via gRPC-web translation
  • Feature is in private beta
  • Published August 29, 2026

The hook

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

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. Everyth

The week's key stories, every Friday.

ONE BRIEFING · EVERY FRIDAY · FREE

Free. Unsubscribe anytime.