Cloudflare Privacy Gateway
Managed Oblivious HTTP relay that hides client IPs from the backend and payloads from the relay.
- Provider
- cloudflare
- Kind
- API gateway
- Category
- Edge
- Official docs
- https://developers.cloudflare.com/privacy-gateway/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| auth | enum | none | api-key | jwt | oauth2 | mtls | no | none | inherited |
| clientIpVisibleToBackend | boolean | — | no | false | inherited |
| closedBeta | boolean | — | no | true | inherited |
| concurrencyLimit | boolean | — | no | false | inherited |
| idempotencyKeys | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| keyTtlHours | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| obliviousHttp | boolean | — | no | true | inherited |
| protocol | enum | http | grpc | websocket | fix | ouch | no | http | ▸ http |
| rateLimiting | boolean | — | no | false | inherited |
| tls | boolean | — | no | true | ▸ true |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
sync-chain-too-deep
Every consecutive synchronous hop from this entry point spends part of the stated p95 latency budget, and the chain's failures multiply. More than three hops is a budget nobody is tracking.
- — all of these hold:
- — the design requirement `latency.p95Ms` has a value
- — the longest chain of synchronous calls starting at the node is more than 3 hops long
nodes:
- { id: "privacy-gateway", component: "cloudflare-privacy-gateway" }API Gatewayalibaba-api-gatewayAmazon API Gatewayaws-api-gatewayAWS AppSync GraphQL APIaws-appsyncAzure API Managementazure-api-managementAI Gatewaycloudflare-ai-gatewayCloudflare API Shieldcloudflare-api-shieldMCP Server Portalcloudflare-mcp-portalGeneric API gatewayapi-gatewayApache APISIXapisixApollo GraphOSapollo-graphosEasegresseasegressEmissary-ingressemissaryEnvoy Gatewayenvoy-gatewayGloo GatewayglooHasurahasuraHelicone AI Gatewayhelicone-gatewayHigresshigressKong GatewaykongKong AI Gatewaykong-ai-gatewayKong Konnectkong-konnectKrakenDkrakendLiteLLM ProxylitellmMartian GatewaymartianNot Diamondnot-diamondPortkey AI GatewayportkeyRequestyrequestySpring Cloud Gatewayspring-cloud-gatewayTyk GatewaytykUnifyunify-aiVercel AI Gatewayvercel-ai-gatewayWSO2 API Managerwso2-api-managerZuulzuulApigeeapigeeAgent Gatewaygoogle-agent-gatewayAPI Gatewaygoogle-api-gatewayApigee hybridgoogle-apigee-hybridCloud Endpointsgoogle-cloud-endpointsFirebase Data Connectgoogle-firebase-data-connectIBM API Connectibm-api-connectOCI API Gatewayoci-api-gateway
# yaml-language-server: $schema=../../schema/component.schema.json # Privacy Gateway: a managed Oblivious HTTP relay on Cloudflare's network. The relay forwards # encrypted requests without learning the application data, and the backend never sees the client # IP. It is in closed beta for privacy-oriented companies and partners ("Privacy Gateway overview"). schemaVersion: "1" type: "component" id: "cloudflare-privacy-gateway" kind: "api-gateway" provider: "cloudflare" docs: "https://developers.cloudflare.com/privacy-gateway/" defaults: managed: true tls: true protocol: "http" properties: obliviousHttp: type: "boolean" default: true clientIpVisibleToBackend: type: "boolean" default: false closedBeta: type: "boolean" default: true