Cloudflare Workers Are No Longer Just for HTTP
TL;DR: Cloudflare Workers can now accept raw TCP connections, ending an eight-year limitation to just HTTP. This major update unlocks new, non-web use cases like gRPC, IoT, and gaming servers on Cloudflare's global edge network.
Key facts
- Category
- Infrastructure
- Impact
- High
- Published
- Source
- InfoQ
Full summary
Cloudflare Workers can now accept raw TCP connections, moving beyond HTTP to support gRPC, IoT, and other non-web protocols.
Cloudflare has announced a significant expansion of its serverless platform, Cloudflare Workers, which can now accept direct inbound TCP connections for the first time. According to reporting from InfoQ, this update ends an eight-year restriction that limited Workers to handling only HTTP-based traffic. The new capability, currently in a private beta, is being rolled out with native support for gRPC, a high-performance communication framework popular for microservices and mobile backends. This move fundamentally changes the scope of applications that can be built on Cloudflare's global edge network, moving beyond web-centric tasks to support a much broader range of network protocols and services.
The new functionality is enabled through a `connect()` handler that developers can add to their Worker scripts. When a client initiates a TCP connection, Cloudflare's Spectrum service—which is designed to protect non-web applications—routes the traffic to the appropriate Worker. The Worker's code then receives a socket object, granting it direct, two-way (full-duplex) communication with the client. For gRPC, Cloudflare is offering two implementation paths. Developers using containerized Workers can leverage full-duplex gRPC in any programming language. For standard JavaScript-based Workers, Cloudflare automatically translates gRPC requests into gRPC-Web, a browser-friendly variant, which simplifies development by handling the complex protocol details for unary and server-streaming communication patterns.
This update is a game-changer for developers, CTOs, and infrastructure teams building on Cloudflare. The previous HTTP-only limitation was a major constraint, forcing engineers to implement complex workarounds or use different platforms for any service that required direct TCP communication. Now, developers can build and deploy a wider variety of applications directly at the edge, closer to their users. This unlocks use cases that were previously impractical on Workers, such as real-time backends for multiplayer games, data ingestion endpoints for IoT devices, direct database connections, and high-throughput services for mobile applications that rely on gRPC. For technology leaders, this means they can now consider consolidating more of their infrastructure onto a single platform, simplifying operations and reducing latency.
By adding raw TCP support, Cloudflare is repositioning Workers from a specialized tool for web optimization into a more general-purpose serverless compute platform. This move makes it a more direct competitor to foundational cloud services like AWS Fargate, Azure Container Apps, and Google Compute Engine for certain types of workloads. The serverless industry is rapidly maturing, and this feature is a clear signal that the battleground is shifting from simple functions to supporting complex, stateful, and network-intensive applications. The key takeaway for businesses is that the "edge" is no longer just for caching static content or running simple request-response logic; it is becoming a viable and powerful location for hosting core application backends that require persistent, low-latency connections.
As the feature is currently in a private beta, the next key milestones will be its public release, pricing structure, and performance benchmarks. It will be important to see how the developer experience evolves and what tools Cloudflare provides to help manage the security and operational complexity of exposing raw TCP sockets. The introduction of gRPC as the first officially supported protocol suggests that others, such as MQTT for IoT or native WebSockets, could follow. This strategic enhancement will likely pressure other edge computing providers like Fastly, Vercel, and Akamai to expand their own networking capabilities to remain competitive, further accelerating the industry's shift toward more powerful and versatile edge platforms.
Why it matters
This update removes a major limitation of Cloudflare Workers, allowing developers to build non-HTTP applications like IoT services, game servers, and high-performance mobile backends directly on the edge network for the first time.
Business impact
Cloudflare Workers now compete more directly with general-purpose cloud compute services like AWS EC2, moving beyond web optimization to become a viable platform for hosting core application backends and simplifying infrastructure for businesses.
Tags
Related on Notifire
Related stories
Primary source: InfoQ
