Cloudflare Workers Unlock TCP: gRPC at the Edge

Edge Computing's New Frontier

Cloudflare's introduction of inbound TCP support for Workers, with gRPC as the initial protocol, marks a substantial expansion of its edge computing platform. The ability to accept raw TCP sockets opens the door to a much wider range of applications that were previously impossible on the Workers runtime, such as message brokers, database proxies, and custom binary protocols. The integration with Durable Objects and the potential to route to containers via getTcpPort() further enhance its flexibility, effectively turning the edge into a sophisticated termination point for arbitrary TCP traffic with programmable routing logic. This moves Workers beyond mere API gateways for HTTP to a more fundamental network function.

The gRPC focus is strategic, aligning with trends in machine-to-machine communication and the need for low-latency, persistent connections, especially in AI agent scenarios. The translation layer for gRPC-web to native gRPC is a clever way to leverage existing browser APIs and Cloudflare's infrastructure while providing a more performant edge experience. However, the limitation of Workers themselves not supporting bidirectional gRPC streaming is a notable constraint, stemming from the underlying web platform's inability to expose HTTP/2 stream-level control. This means that while Workers can serve many gRPC use cases, truly stateful, long-lived bidirectional streams will still require a different approach or a containerized backend. The private beta status and Cloudflare's candid admission of not using gRPC internally for their own core services also signal that this is an evolving feature, and developers should temper expectations regarding its maturity and stability for mission-critical, high-throughput scenarios initially.

This development is highly beneficial for developers looking to reduce latency for applications requiring persistent connections or custom protocols, especially those in the AI and IoT spaces. By bringing gRPC processing closer to the user, latency-sensitive applications can see significant performance improvements. The ability to run existing, unmodified gRPC servers within containers orchestrated by Workers is also a powerful migration path. However, the current limitations in direct bidirectional streaming from Workers and the private beta status suggest that early adopters should be prepared for potential rough edges and a phased rollout. The broader implication is that Cloudflare is solidifying its position as a comprehensive edge platform, capable of handling not just web traffic but a much wider spectrum of network-level workloads.

Key Points

• Cloudflare Workers now support inbound TCP connections, expanding beyond HTTP.
• gRPC is the first protocol built on top of this new TCP capability.
• The connect(socket) handler allows Workers to interact with raw TCP sockets.
• This enables new use cases like message brokers, database proxies, and custom binary protocols at the edge.
• Integration with Durable Objects and containers provides flexible routing options.
• Workers can serve unary and server-streaming gRPC, and call external gRPC servers without containers, but not bidirectional streaming.
• The gRPC implementation relies on translation from/to gRPC-web due to web platform constraints.
• The feature is currently in private beta, with Cloudflare acknowledging it's not yet their internal standard.

---

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