Cloudflare Workers as Data Transit Proxy - How is egress/ingress data charged?

Developers Workers
1

Working on using Cloudflare Workers for a data proxy across cloud providers. For example, an AWS service hits this Cloudflare Worker to pull data through it from Azure. These workers do a quick data process and hand it through to the other side.

I understand that there are data transit costs for both AWS and Azure; Where/What are the costs for this data that is traversing across Cloudflare Worker (ingress on one side, egree on the other). Ive searched and have only found a reference that this type of use case might need to discussed with Cloudflare sales engineers as it is not “typical website use case” or something like that.

Any reference, feedback appreciated

2

Workers are billed by requests and CPU time, not data transfer.

1 Like
3

@i40west thanks. So there is no cost at all for data? Thats awfully nice, boggles my mind – but if thats what it is

As per the current pricing page 337, Egress bandwidth for unbound workers is charged at $0.045/GB.

4

“Unbound” is an older pricing model that is no longer used – but people with older Workers that were on that pricing plan could still be on it.

The current pricing is “Standard” which bills by requests and CPU time.

1 Like
5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.