Cloudflare is adding a programmable layer to its Gateway security service, letting customers run their own code during policy decisions or route web traffic through a Worker. The practical change is more control over how security rules handle requests, without requiring customers to run a separate proxy for those tasks.
Cloudflare Watch analysis
What happened
Cloudflare announced two ways to connect its Workers compute platform to Gateway. The Forward action, available in public beta, sends matching HTTP traffic to a Worker, which can inspect and modify requests and responses, or take another action while traffic continues to its destination.
Custom Functions will follow before the end of the year. They let a Worker calculate a typed value, such as a user’s role, that Gateway can use as a selector in HTTP or network policy rules. The company says both capabilities are available to all Zero Trust plans. Cloudflare’s announcement includes examples such as adding headers based on identity information and prompting users to justify access to sensitive destinations.
Why it matters
Teams can write policy logic for their own environments rather than stitching together a Gateway rule, a separate proxy and the accompanying maintenance. Cloudflare says Workers and Gateway run on the same infrastructure, so a Worker call is a local function call rather than traffic sent on a round trip across the network.
That may simplify some awkward security workflows, but the two features have different jobs. Custom Functions return a value for a policy to evaluate; Forward is the more flexible option for modifying live HTTP traffic, and Cloudflare says it should be designed carefully to avoid harming the user experience.
Our read
This is a substantial extension point, not just another row in a dashboard. The appealing part is that an organisation can bring its own logic into the policy path without maintaining a separate proxy fleet. The catch is that the flexibility also means customers own the behaviour they build. “Programmable” is useful; it is not the same thing as “someone else has tested your custom rule”.
What to watch
- How quickly Custom Functions reach general availability, and whether their supported context matches real policy needs.
- What customers build with Forward, and whether those Workers introduce latency or operational headaches in practice.
- How teams test and govern custom logic before it starts handling live traffic.
Discussion spark: Would you rather keep security policy within a vendor’s built-in rules, or run your own code in the decision path and take responsibility for what it does?
Sources and evidence
- A fully programmable secure web gateway (15 October 2026, 17:11 UTC)
not affiliated with or endorsed by Cloudflare