Cloudflare Workers and Containers now support inbound TCP connections and gRPC
- Source
- blog.cloudflare.com
- Author
- Cloudflare
- Date
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.
“And so as part of Agents Week, we’re extending Workers in the other direction, supporting inbound TCP connections and adding new ways to run gRPC applications on Cloudflare.”
“With this, there’s pretty much no gRPC-based application that you can’t deploy to Cloudflare, no matter what language it’s in or dependencies it relies on.”
“We translate incoming gRPC to gRPC-web, and translate outgoing gRPC-web to gRPC.”
“This lets you take advantage of Cloudflare’s network of 330+ locations and handle requests much closer to clients than is possible elsewhere.”
postCloudflare adds multimodal Clef-omni and cuts Clef-flash pricing
postCloudflare AI Search goes GA with image embeddings and PDF OCR
articleWe are introducing Clef and Clef-flash, open-source decision models hosted on…
articleToday, we’re making the Cloudflare Monetization Gateway available as part of a…
Checking sign-in…
Loading comments…