Learn how Cloudflare gRPC support protects your API traffic.
The gRPC protocol was developed by Google in 2015 to build efficient APIs with smaller payloads for reduced bandwidth usage, decreased latency, and faster implementations. Cloudflare currently offers beta support for gRPC to protect your APIs on any orange-clouded gRPC endpoints.
Running gRPC traffic on Cloudflare is compatible with most Cloudflare products, including WAF, Bot Management, and Page Rules. gRPC support is available on all Cloudflare plans for no additional fees. However, charges may occur for gRPC traffic over add-on products such as Argo Smart Routing, WAF, and Bot Management. gRPC support is broadly tested and considered stable, but bugs are still possible. Report unexpected behaviors to Cloudflare Support.
- Your gRPC endpoint must listen on port 443.
- Use HTTP2 (+TLS) for gRPC requests.
- Use application/grpc or application/grpc+<message type (for example: application/grpc+proto) for the Content-Type header of gRPC requests.
The following products have limited capabilities with gRPC requests:
- Argo Smart Routing is supported for gRPC calls, client-side, and server-side streaming. Bi-directional streaming is currently not supported in combination with Argo Smart Routing.
- Argo Tunnel currently does not support gRPC.
- Trailers-Only responses without a body, typically sent when the upstream encounters an error.
Follow the instructions below to enable gRPC:
- Log in to your Cloudflare account.
- Select the appropriate domain.
- Click the Network app.
- Toggle the gRPC (beta).