Inbound TCP and gRPC Support for Cloudflare Workers
blog.cloudflare.com- Category
- Developer Tools
- Type
- TOOL
- Added
- Aug 4, 2026
About
Cloudflare Workers can now accept inbound TCP connections via a new connect() handler and Spectrum ingress proxy, routing raw sockets to Durable Objects and Containers for full-duplex protocols like gRPC. Workers can also act as gRPC servers or clients without containers by automatically translating between gRPC and browser-compatible gRPC-web, enabling low-latency voice AI and existing gRPC backends to run on Cloudflare's edge network.
What it can do
Accept inbound TCP connections via a connect() handler
Raw TCP socket connection → Inbound connection routed to Worker
Route raw socket traffic to Durable Objects and Containers
Raw TCP socket → Routed connection to Durable Object or Container
Act as a gRPC server or client without containers
gRPC requests → gRPC responses
Translate between gRPC and browser-compatible gRPC-web
gRPC or gRPC-web traffic → Translated protocol traffic
Why it made the leaderboard
If you're building low-latency voice AI or need to run existing gRPC services without spinning up dedicated servers, this lets you terminate raw TCP and full-duplex gRPC directly at Cloudflare's edge, with automatic gRPC-web translation for browser clients.
Tags
Media
Comments (0)
No comments yet
Indexed by a proprietary survey. Corrections welcome.